SQL - best practices [closed] - sql

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am about to develop a small cms\forum. Multiple customers are going to have there own access where the customers can communicate white them.
What is best practices- to make separate SQL db to each customer's cms data or one big to contain all the customers data?

As I cannot comment, so I can only type here.
It is strange that you would like to have separate database for each customer and it seems impossible to manage multiple db for just one purpose or function. For example, how could you identify which db belong to which customer? Also, do you expect to have many resource to allocate to each customer? a db simply waste if the customer is not active.
So, I suggest you to use one db to manage all the customers data which is normal solution.

Related

SQL Server Integration Services: how to manage multiple sources? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I merged two databases for analyses purposes. One of these databases is out of production, so the data is not changing. The other db is live and continuously growing.
What's the best practice in terms of data management/storage? Do I have to delete all rows and reload + union data from both databases or is there a better way to manage this?
Thanks in advance
Sam
If you know the SSIS then make a package which will check keys and based on that it will inserted only unique rows.
You can easily apply lookup via ssis in source and destination.
Let me know if you need any help

ERD for Payroll [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I am attempting to build a database for a company's payroll system. I have worked on an ERD and my main concerns revolve around the loops, reimbursement table and possible weak entities.
I haven't done much of these and could use your help.
Thanks.
Link to ERD: ERD for Payroll
I would probably change the user to user_login. and remove loan_payment and reimbursement and just simply have a payment table. This could hold similar values but also include a payment type that would include its values like 'reimbursement' or 'work payment' because like you said reimbursement doesn't need to be its own table.

How to make choice between NoSQL and SQL? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
My question is that I want to learn nodejs/express, and make a super simple web project. It would be a database with tables : users, video_games, categories.
The web site will just show list of games (just an example).
In this typical case, what would be more efficient : Mysql or MongoDB (SQL or NoSql) ?
In this particular case were you want to show only list ( you don't want to actual store videos, doc, texy, etc..) SQL database will be a good choice.
Another reason to use SQL database is that your data is relational ( I am assuming that the data i.e video_games, category...etc are linked to users) were SQL database suits more.
You should go to nosql database only when there is to relationship between your data ( well this is not the only case, but for beginners were your aim is to simply pick the right database this suffice)

sql database convention [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Apologies in advance if this is a stupid question. I've more or less just started learning how to use SQL.
I'm making a website, the website stores main accounts, each having many sub-accounts associated with them. Each sub-account has a few thousand records in various tables associated with it.
My question is to do with the conventional usage of databases. Is it better to use a database per main account with everything associated with it stored in the same place, store everything in one database, or an amalgamation of both?
Some insight would be much appreciated.
Will you need to access more than one of these databases at the same time? If so put them all in one. You will not like the amount of effort and cost 'joining' them back together to do a query. On top of that, every database you have needs to be managed, and should you need to transfer data between them that can get painful as well.
Segregating data by database is a last resort.

sql database design - select & check boxes [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am designing a database for a form which contains many select boxes and check boxes lists.
I am unsure whether to populate these lists from a table in the database or from the select html text.
as part of db design best practice which is the preferred method.
If you expect the form elements (checkboxes, lists) are likely to change often, or are conditional (based on configurable permissions/roles), then they should come from a database.
However, if they are mostly static (rarely change, not dependent on configurable permissions), then you should hard-code them. The big benefit of hard-coding them is less traffic on your DB. This will yield the best performance.