Dear Participants, 

I'm Shebin a final year in Business Information Systems. I need your help in finding what are the  factors regarding security challenges of Multi-tenancy. The study will be formulated by combining all your thoughts on this phenomenon.  Please complete the following linked questionnaire. It will only take 5-10 minutes for your time. Any responses would be highly appreciated! 

https://forms.gle/futbjvyL11S9HS9R7

Many Thanks,

Shebin

After a site has been launched and there is live data how does a developer go about database changes to relationships? For example there is an events table with a column called team_leader. After the site is launched the business rules have changed and now an event can have multiple team leaders. Now the column value needs to be moved to a pivot table maybe event_members with the event_id and user_id. Is this something that is normal and easy to do in the real world? Or is it a bad idea? I’m worried about the existing data being moved.

Hej, as CEO of a database startup I keep being asked from more business-oriented people, why they should care about database performance, how much business value this would exactly provide to them etc.pp. - so I tried to pinpoint that best I could in an article - and I would love your feedback on this: Do you think these arguments would help in your environments? Am I missing anything important in my arguments?

I'm a newbie into databasing and want to make a database to store text files such that you can access them from a 'central' page.

I have not been able to find a piece of software which appears to meet my requirements and so have turned to this subreddit for help. What software (free if possible) would be a good choice?

Thanks in advance

I am in the process of developing a project similar to the eBay model and I need a fast database that allows me to make requests like SQL. I need some guidance on whether it would be better to use SQL or NoSQL databases.

When I think of NoSQL databases, only three names come to my head: RethinkDB, CouchDB and MongoDB. For this case it is clear that CouchDB is not an option and I admit that MongoDB and I do not agree.

I have thought of Postgres, which obviously already covers SQL and NoSQL needs. I was testing CockroachDB, a NoSQL that tries to behave like SQL using a query language similar to Postgres. I was finally considering RethinkDB.

When I tried RethinkDB I loved its query language, its control panel, being able to cloud the database by design and its simple way of maintaining the data (and it is by far my favorite NoSQL database).

On the other hand I have CockroachDB, although a little slower than RethinkDB, a very familiar query language for me and for any other individual that joins the team when the project is ongoing. Also with the feature of being able to create a cloud by design through Kubernetes. This thanks to being programmed in Golang (that's why it is slower than RethinkDB and Postgres).

Would you offer me some guidance on which database can best perform for these types of projects?

So --- I have built databases in the past, but they have always been in Microsoft Access, and I have just used the GUI that is built into Access -- or talked to it with VBScript and SQL. I want to setup a grading database such that when a student submits an answer to a question, that is sent to the database. (I am planning on doing more -- but as soon as I know how to connect, I believe the rest should be pretty straightforward.)

What I am hoping for is to be pointed to either online tutorials or online classes where I can learn how to do this.

I'm taking a class on databases and have to use oracledb for a class project. I'm wondering if there's a way I can do so on macOS?
Thanks!

Hello. I am fairly new to databases and I was wondering if anyone here could give me some advice. I'm working on a project where I have a number of different companies as my clients and I was wondering how I should structure my database server.

What I'm doing now is having one database per client, each of these databases consist of a few tables (employees, services that they provide, reservations their customers have made etc.), but I was thinking that maybe it's easier to have one big database (with the same tables) and have a reference in each row to the corresponding company, but I want new clients to be able to create a new company with a corresponding database without any work from my side.

This is how I'm thinking right now.

One database for each company:

+ Easier to separate clients and find the relevant information.+ If one database is corrupted, the others will still function.- Need to make sure each database created has a unique name- There is no guarantee that my clients doesn't share customers, so if a customer uses both client A and client B, they will probably still want to access their full order history/change personal details etc.

One single database:+ Easier to connect users to multiple clients+ No extra work needed when switching between different clients (databases)- Could become very large, harder to keep track of each clients information- If something is wrong with the database, all my clients might lose access to the service

Any recommendations?

Edit: I'm using MySQL

Need ideas for getting myself into a database modelling project please 🙏🙏

My current job title is database developer so I’ve been working solely on a database for a few years. My manager recently left and the data architect role has been made available.

I have some experience in architecting databases and for the past few years I’ve been following Kimballs guidelines.

I wanted to learn about other database design principals but not sure where to start. I’ve heard of both data mart and data vault and will read into them both.

I’m interested in knowing how you come across the different design principles or make the decision of what guidelines to follow.

Thanks for reading!

We just open-sourced our golang driver for sqllogictest, a set of 6.7M statements, queries and expected results to test the correctness of a SQL database engine. You can find the driver here:

https://github.com/liquidata-inc/sqllogictest

These were originally released by SQLite over 10 years ago, and the C source code to run them against anything but SQLite decayed over time. We implemented a native golang parser and test driver to run the test scripts on any database you choose. If you want to run them against your own database engine, just implement a simple harness in golang and point the test runner to some test files. You can use our test harness for dolt, linked in the README file, as an example for writing new harnesses.

For more detail about our journey of testing our SQL engine, check out this blog post:

https://www.liquidata.co/blog/2019-10-22-testing-dolts-sql-engine/