Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Recently we started to get some performance issues on our SQL Server.
On analysis I found the DBA has got 800 millions rows in ONE TABLE (300 GB in size)
No partitioning, no proper indexes – lead to performance going down.
ADVICE:
How many number of rows would one recommended for a table in SQL Server 2005
Oracle user here (never used MS SQL server with such large number of rows)
I can say that in all the systems I’ve worked with, all the tables having hundreds of millions of rows just had to be partitioned.
According to this document you should also have such big table partitioned in MS SQL as well. http://msdn.microsoft.com/en-us/library/ms345146(v=sql.90).aspx