SQL Server - Maximum Capacity Specifications Comparison Table
SQL Server - Maximum Capacity Specifications Comparison Table
Object SQL Server 7.0 SQL Server 2000 SQL Server 2005 (32-bit)
Batch size 65,536 * Network Packet Size1 65,536 * Network Packet Size1 65,536 * Network Packet Size1
Bytes in source text of a stored procedure Lesser of batch size or 250 MB Lesser of batch size or 250 MB Lesser of batch size or 250 MB
Limited only by number of bytes Limited only by number of bytes Limited only by number of bytes
Columns in GROUP BY, ORDER BY
per GROUP BY, ORDER BY per GROUP BY, ORDER BY per GROUP BY, ORDER BY
Length of a string containing SQL Statements (batch size) 65,536 * Network packet size 1 65,536 * Network packet size 1 65,536 * Network packet size 1
Locks per connection Maximum locks per server Maximum locks per server Maximum locks per server
Nested subqueries 32 32 32
Rows per table Limited by available storage Limited by available storage Limited by available storage
1
Network Packet Size is the size of the tabular data stream (TDS) packets used to communicate between applications and the relational database engine. The default packet
size is 4 kilobytes (KB), and is controlled by the network packet size configuration option.
2
The maximum number of bytes in any index key cannot exceed 900 in SQL Server 2000 and SQL Server 2005. You can define a key using variable-length columns whose
maximum sizes add up to more than 900, provided no row is ever inserted with more than 900 bytes of data in those columns. In SQL Server 2005, you can include nonkey
columns in a nonclustered index to avoid the maximum index key size of 900 bytes.
3
Database objects include objects such as tables, views, stored procedures, extended stored procedures, user-defined functions, triggers, rules, defaults, and constraints. The
sum of the number of all objects in a database cannot exceed 2,147,483,647.
4
Although a table can contain an unlimited number of FOREIGN KEY constraints, the recommended maximum is 253. Depending on the hardware configuration hosting SQL
Server, specifying additional foreign key constraints may be expensive for the query optimizer to process.
5
This value is for static lock allocation. Dynamic locks are limited only by memory.
6
If a stored procedure accesses more than 8 databases, or more than 2 databases in interleaving, you will receive an error.
7
If the table contains one or more XML indexes, the clustering key of the user table is limited to 15 columns because the XML column is added to the clustering key of the
primary XML index. In SQL Server 2005, you can include nonkey columns in a nonclustered index to avoid the limitation of a maximum of 16 key columns.
8
SQL Server 2005 supports row-overflow storage which enables variable length columns to be pushed off-row. Only a 24-byte root is stored in the main record for variable
length columns pushed out of row; because of this, the effective row limit is higher than in previous releases of SQL Server.