SQL database design
i have slary system using vb.net and sql server there is 27 user the compute up to 700 employ salary every monthe i collecte (700 *27) number of row and adding them programaticaly to a table called salary
the table salary have 40 column with one primery key is there any proplem with this algorthim when the number of rows be more than million in salary tabe ?
Software/Hardware used:
sqlserver
the table salary have 40 column with one primery key is there any proplem with this algorthim when the number of rows be more than million in salary tabe ?
Software/Hardware used:
sqlserver
ASKED:
July 28, 2011 6:09 AM
UPDATED:
March 31, 2012 7:46 PM
Answer Wiki:
one table with 40 columns sounds like you have not normalized the data.
I suggest you investigate data normalization as it applies to RDBMS theory.
Will what you have work? Probably. Will it work well? Not as well as it could.
To see all answers submitted to the Answer Wiki: View Answer History.
I agree with Meandyou. There is probably a normalization issue.
However, if no normalization issues exist, make sure that the appropriate indexes exist and the database server is correctly configured (memory and storage) to offer acceptable perfomance with that amount of data and its expected growth.
thanx carlosd and meandyou
im in the programe designing step but i make a test by vb.net loop adding more than 1000000 rows to the salary tabe it worke but sloo
there is no normalization available
carlosd…………… plz
what you mean by:-
configured (memory and storage
I’m not sure you understand what normalization is.
As for your last question, database management systems usually have settings to properly configure the use of memory and storage according to the amount of data and the expected type and frequency of transactions, among other things. This is the DBA’s job.
P.s. I’m not a DBA
THANXXX CARLOSD