It’s close to a week-end, and hence, I have a very short post for today.
Very often I find teams and SQL Server enthusiasts coming up to me and asking me some of the following questions:
- How many databases can I host on a SQL Server instance?
- How large can these databases be?
- Is there a limit to the number of records in a table?
I often point them to Books On Line/MSDN where they can find the official specification which would be able to answer all of their questions. Today, I thought of putting an end to this almost endless cycle of same question-answer sessions and provide the direct links to the Books on Line/MSDN maximum capacity specification for SQL Server. So, here goes:
Maximum Capacity Specifications for SQL Server
- SQL 2012: http://msdn.microsoft.com/en-us/library/ms143432.aspx
- SQL 2008 R2: http://msdn.microsoft.com/en-us/library/ms143432(v=sql.105).aspx
- SQL 2008: http://msdn.microsoft.com/en-us/library/ms143432(v=sql.100).aspx
- SQL 2005: http://msdn.microsoft.com/en-us/library/ms143432(v=sql.90).aspx
How do you calibrate your systems?
Whenever someone asks a minimum/maximum capacity specification related question, I always wonder how they would calibrate their systems and more importantly, certify their product against these numbers. So, here’s what I would like to learn from you, my kind readers:
How do you derive minimum/maximum capacity specifications for your systems?
Ideally, the situation would be that a production system would have the same limitations as the underlying platform. But, that would not happen in practice due to the choice of the architecture and/or technical design decisions.
Do leave a note as you go. It’s a very interesting question, with no fixed answer – every system and every team would have their own methods, which is why I am sure it would be a great discussion.
Until we meet next time,