tsql - designing table for high insert rate -


i sugestion on how design table gets 10 50 million inserts day , needs respond selects... should use indexes? or overhead cost great?

edit:im not worried transaction volume... assigment... , need figure out design table "must respond selects not based on primary key, knowing table receive enourmous amount of inserts day-in-day-out"

definitely. @ least primary key, foreign keys, , whatever need reporting, don't overdo it. 10k-50k inserts day not problem. if like, don't know, million inserts start thinking of having separate tables, data dictionaries , not, needs wouldn't worry.


Comments

Popular posts from this blog

c# - SVN Error : "svnadmin: E205000: Too many arguments" -

c++ - Using OpenSSL in a multi-threaded application -

All overlapping substrings matching a java regex -