SQL Server Build List - SQL 2008 R2

Main Builds

Build	KB Article	Title	Description
10.5.1600.1	RTM	Release of Manufacturing of SQL Server 2008 R2	The first public, supported version of SQL Server 2008 R2

Build	Kb Article	URL	Description
10.50.1753.0	Cumulative Update package 5 for SQL Server 2008 R2	http://support.microsoft.com/kb/2438347	CU 5 for SQL Server 2008 R2 RTM includes fixes for Reporting Services, replication with XML columns, and a number of engine fixes for various items
10.50.1746.0	Cumulative Update package 4 for SQL Server 2008 R2	http://support.microsoft.com/kb/2345451	CU 4 for SQL Server 2008 R2 RTM includes fixes for TDE and full-text search with compression enabled.
10.50.1734.0	Cumulative Update package 3 for SQL Server 2008 R2	http://support.microsoft.com/kb/2261464/	CU 3 for SQL Server 2008 R2 RTM
10.50.1720.0	Cumulative Update package 2 for SQL Server 2008 R2	http://support.microsoft.com/kb/2072493	CU 2 for SQL Server 2008 R2 RTM
10.50.1702.0	Cumulative Update package 1 for SQL Server 2008 R2	http://support.microsoft.com/kb/981355/en-us	CU 1 for SQL Server 2008 R2 RTM
10.50.1600.1		N/A	RTM
10.50.1450.3		N/A	RC 0

SQL Server Build List - SQL 2008

Main Builds

Version	Build	KB Article
Service Pack 2 for SQL Server 2008	10.0.4000.00	968369
Service Pack 1 for SQL Server 2008	10.0.2531.00	968369
RTM	10.0.1600.22	N/A

Build	KB Article	Title	Description
10.0.4272.00	2467239	SQL Server 2008 SP2 CU 2	CU#2 for SQL Server 2008 Service Pack 2. Fixes include recovering LOB pages from failed inserts, custom resolver issues in replication, and issues with online index rebuilds among others.
10.0.4266.00	2289254	SQL Server 2008 SP2 CU 1	The first CU after SQL Server 2008 Service Pack 2.
10.0.4000.00	2285068	SQL Server 2008 SP2	The second service pack for SQL Server 2008.
10.0.2808.00	2467236	Cumulative Update 12 for SQL Server 2008 SP1	The 12th rollup of patches for Service Pack 1. Fixes include clustering IPv6 problems, join performance fixes, and SSAS crashes.
10.0.2804.00	2413738	Cumulative Update 11 for SQL Server 2008 SP1	The 11th rollup of patches for Service Pack 1. Fixed include fixes for too many VLFs during recovery, MDX issues in BIDS, and a few analysis services fixes.
10.0.2799.00	2279604	Cumulative Update 10 for SQL Server 2008 SP1	The tenth rollup of patches for Service Pack 1.
10.0.2789.00	2083921	Cumulative Update 9 for SQL Server 2008 SP1	The ninth rollup of patches for Service Pack 1.
10.0.2775.00	981702	Cumulative Update 8 for SQL Server 2008 SP1	The eighth rollup of patches for Service Pack 1.
10.0.2766.00	979065	Cumulative Update 7 for SQL Server 2008 SP1	The sixth rollup of patches for Service Pack 1.
10.0.2757.00	977443	Cumulative Update 6 for SQL Server 2008 SP1	The sixth rollup of patches for Service Pack 1.
10.0.2746.00	975977	Cumulative Update 5 for SQL Server 2008 SP1	The fifth rollup of patches for Service Pack 1.
10.0.2734.00	973602	Cumulative Update 4 for SQL Server 2008 SP1	The fourth rollup of patches for Service Pack 1.
10.0.2723.00	971491	Cumulative Update 3 for SQL Server 2008 SP1	The third rollup of patches for Service Pack 1.
10.0.2714.00	970315	Cumulative Update 2 for SQL Server 2008 SP1	The second roll-up of patches for Service Pack 1.
10.0.2710.00	969099	Cumulative Update 1 for SQL Server 2008 SP1	The first roll-up of patches for Service Pack 1. Includes CU4 patches for RTM that didn't make it in SP1.
10.0.2531.00	968369	Service Pack 1 for SQL Server 2008	SP1
10.0.1835.00	979064	Cumulative Update 10 for SQL Server 2008 SP1	The tenth rollup of patches for SQL Server 2008 RTM.
10.0.1828.00	977444	Cumulative Update 9 for SQL Server 2008	The 9th roll-up of patches for SQL Server 2008 RTM.
10.0.1823.00	975976	Cumulative Update 8 for SQL Server 2008	The 8th roll-up of patches for SQL Server 2008 RTM.
10.0.1818.00	973601	Cumulative Update 7 for SQL Server 2008	The 7th roll-up of patches for SQL Server 2008 RTM.
10.0.1812.00	971490	Cumulative Update 6 for SQL Server 2008	The 6th roll-up of patches for SQL Server 2008 RTM.
10.0.1806.00	969531	Cumulative Update 5 for SQL Server 2008	The 5th roll-up of patches for SQL Server 2008 RTM.
10.0.1798.00	963036	Cumulative Update 4 for SQL Server 2008	The fourth roll-up of patches since the RTM version.
10.0.1787.00	960484	Cumulative update package 3 for SQL Server 2008	The third roll-up of patches since the RTM version.
10.0.1779.00	958186	Cumulative update package 2 for SQL Server 2008	The second roll-up of patches since the RTM version.
10.0.1763.00	956717	Cumulative update package 1 for SQL Server 2008	The first roll-up of patches since the RTM version.
10.0.1755.00	957387	FIX: No records may be returned when you call the SQLExecute function to execute a prepared statement and you use the SQL Native Client ODBC Driver in SQL Server 2008
10.0.1600.22	RTM		The first public, supported version of SQL Server 2008

SQL Server Build List - SQL 2005

Main Builds

RTM	9.00.1399.06
SP1	9.00.2047
SP2	9.00.3042
SP3	9.00.4035
SP4	9.00.5000

Build	Kb Article	URL	Description
9.00.5054	2463332	http://support.microsoft.com/kb/2464079	Cumulative Update 1 for SQL Server 2005 Service Pack 4
9.00.5000	2463332	http://support.microsoft.com/kb/2463332	SQL Server 2005 Service Pack 4
9.00.4311	2345449	http://support.microsoft.com/kb/2345449	Cumulative update package 12 for SQL Server 2005 Service Pack 3
9.00.4309	2258854	http://support.microsoft.com/kb/2258854	Cumulative update package 11 for SQL Server 2005 Service Pack 3
9.00.4305	983329	http://support.microsoft.com/kb/983329/	Cumulative update package 10 for SQL Server 2005 Service Pack 3
9.00.4294	980176	http://support.microsoft.com/kb/980176/	Cumulative update package 9 for SQL Server 2005 Service Pack 3
9.00.4290	960598	http://support.microsoft.com/kb/960598	Post SP3 Hot fix, documented on the "All Builds" page at Microsoft for this SP. You receive error 8623 and non-yielding scheduler error intermittently when you try to clean up old expired notifications in SQL Server 2008
9.00.4285	978915	http://support.microsoft.com/default.aspx?scid=kb;en-us;978915	Cumulative update package 8 for SQL Server 2005 Service Pack 3
9.00.4273	960598	http://support.microsoft.com/kb/960598	Cumulative update package 7 for SQL Server 2005 Service Pack 3
9.00.4266	974648	http://support.microsoft.com/kb/974648/	Cumulative update package 6 for SQL Server 2005 Service Pack 3
9.00.4262	970894	http://support.microsoft.com/kb/970894/	MS09-062: Description of the security update for SQL Server 2005 Service Pack 3 QFE: October 13, 2009
9.00.4230	972511	http://support.microsoft.com/kb/972511/	Cumulative update package 5 for SQL Server 2005 Service Pack 3
9.00.4226	970279	http://support.microsoft.com/kb/970279/	Service Pack 3 Cumulative Update 4
9.00.4220	967909	http://support.microsoft.com/kb/967909/	Service Pack 3 Cumulative Update 3
9.00.4211	961930	http://support.microsoft.com/kb/961930	Service Pack 3 Cumulative Update 2
9.00.4207	959195	http://support.microsoft.com/kb/961930	Service Pack 3 Cumulative Update 1
9.00.4053	MS09-062	http://www.microsoft.com/technet/security/bulletin/MS09-062.mspx	Vulnerabilities in GDI+ Could Allow Remote Code Execution
9.00.4035	955706	http://support.microsoft.com/kb/955706	Service Pack 3
9.00.3356	976952	http://support.microsoft.com/kb/976952/	Cumulative update package 17 for SQL Server 2005 Service Pack 2
9.00.3355	974647	http://support.microsoft.com/kb/974647/en-us	Cumulative update package 16 for SQL Server 2005 Service Pack 2
9.00.3330	972510	http://support.microsoft.com/kb/972510/en-us	Cumulative update package 15 for SQL Server 2005 Service Pack 2
9.00.3328	970278	http://support.microsoft.com/kb/970278/en-us	Cumulative update package 14 for SQL Server 2005 Service Pack 2
9.00.3325	967908	http://support.microsoft.com/kb/967908	Cumulative update package 13 for SQL Server 2005 Service Pack 2
9.00.3315	962970	http://support.microsoft.com/kb/962970	Cumulative update package 12 for SQL Server 2005 Service Pack 2
9.00.3310	960090	http://support.microsoft.com/kb/960090	MS09-004: Description of the security update for SQL Server 2005 QFE: February 10, 2009
9.00.3301	958735	http://support.microsoft.com/kb/958735	Cumulative Update 11 for Service Pack 2
9.00.3295	959132	http://support.microsoft.com/kb/959132/	FIX: Error message when you install Cumulative Update 10 or Cumulative Update 9 for SQL Server 2005 Service Pack 2 on a drive that uses the FAT32 file system
9.00.3294	956854	http://support.microsoft.com/kb/956854/	Cumulative update package 10 for SQL Server 2005 Service Pack 2 as of Octboer 21, 2008
9.00.3289	xx	http://support.microsoft.com/kb/937137	Hotfix now rolled into CU 10. Listed in the Post-SP2 builds
9.00.3282	953752	http://support.microsoft.com/kb/953752/	Cumulative update package 9 for SQL Server 2005 Service Pack 2 as of August 19, 2008
9.00.3260	954950	http://support.microsoft.com/kb/954950/	FIX: Error message when you run a distributed query in SQL Server 2005: "OLE DB provider 'SQLNCLI' for linked server '' returned message 'No transaction is active'"
9.00.3259	954669	http://support.microsoft.com/kb/954669/	FIX: An ongoing MS DTC transaction is orphaned in SQL Server 2005
9.00.3257	951217	http://support.microsoft.com/kb/951217/	Cumulative update package 8 for SQL Server 2005 Service Pack 2 as of June 16, 2008
9.00.3239	949095	http://support.microsoft.com/kb/949095/	Cumulative update package 7 for SQL Server 2005 Service Pack 2 available as of April 28, 2008
9.00.3232	949959	http://support.microsoft.com/kb/949959/	Merge Replication Hotfix
9.00.3231	949687	http://support.microsoft.com/kb/949687/	FIX: Error message when you run a transaction from a remote server by using a linked server in SQL Server 2005: "This operation conflicts with another pending operation on this transaction"
9.00.3228	946608	http://support.microsoft.com/kb/946608/	Cumulative Update 6 contains hotfixes for SQL Server 2005 issues that have been fixed since the release of Service Pack 2.
9.00.3215	943656	http://support.microsoft.com/kb/943656/	Cumulative Update 5 contains hotfixes for SQL Server 2005 issues that have been fixed since the release of Service Pack 2.
9.00.3200	941450	http://support.microsoft.com/default.aspx?scid=kb;en-us;941450	Cumulative Update 4 contains hotfixes for SQL Server 2005 issues that have been fixed since the release of Service Pack 2.
9.00.3186	939537	http://support.microsoft.com/kb/939537	Cumulative update package 3 for SQL Server 2005 Service Pack 2
9.00.3182	N/A	N/A	On-demand build with hotfixes: 50001298, 50001324, and 50001440
9.00.3180	939942	http://support.microsoft.com/kb/939942/	FIX: You receive an error message when you try to access a report after you configure SQL Server 2005 Reporting Services to run under the SharePoint integrated mode
9.00.3179	N/A	N/A	On-demand build with hotfixes: 50001482 and 50001194
9.00.3178	N/A	N/A	On-demand build with hotfixes: 50001193 and 50001352
9.00.3177	N/A	N/A	On-demand build with hotfixes: 50001391, 50001367, 50001379, 50001408, and 50001397
9.00.3175	936305	http://support.microsoft.com/kb/936305	Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
9.00.3171	937745	http://support.microsoft.com/kb/937745	FIX: You may receive error messages when you try to log in to an instance of SQL Server 2005 and SQL Server handles many concurrent connections
9.00.3169	937041	http://support.microsoft.com/kb/93704	FIX: Changes in the publisher database are not replicated to the subscribers in a transactional replication if the publisher database runs exposed
9.00.3166	936185	http://support.microsoft.com/kb/936185	FIX: Blocking and performance problems may occur when you enable trace flag 1118 in SQL Server 2005 if the temporary table creation workload is high
9.00.3162	935360	http://support.microsoft.com/kb/935360/	(http://support.microsoft.com/kb/935360/) FIX: Error message when you run an MDX query that retrieves data from an Analysis Services database: "An error occurred while the dimension...
9.00.3162	935922	http://support.microsoft.com/kb/935922/	FIX: Error message when you install Microsoft Dynamics CRM 3.0: "Setup failed to validate specified Reporting Services Report Server"
9.00.3162	932610	http://support.microsoft.com/kb/932610/	FIX: Error message when you run an MDX query in SQL Server 2005 Analysis Services: "An unexpected error occurred...
9.00.3162	935829	http://support.microsoft.com/kb/935829/	http://support.microsoft.com/kb/935829/
9.00.3162	935830	http://support.microsoft.com/kb/935830/	FIX: A server may start slowly if you have SQL Server 2005 Analysis Services installed and if many objects are stored on the server
9.00.3162	935832	http://support.microsoft.com/kb/935832/	FIX: You cannot cancel an MDX query that runs for a long time in SQL Server 2005 Analysis Services
9.00.3161	935356	http://support.microsoft.com/kb/935356	Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available
9.00.3159	934459	http://support.microsoft.com/kb/934459	FIX: The Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context
9.00.3156	934226	http://support.microsoft.com/kb/934226	FIX: Error message when you try to use Database Mail to send an e-mail message in SQL Server 2005: "profile name is not valid (Microsoft SQL Server Error 14607)"
9.00.3155	933549	http://support.microsoft.com/kb/933549	FIX: You may receive an access violation when you perform a bulk copy operation in SQL Server 2005
9.00.3154	934106	http://support.microsoft.com/kb/934106	FIX: SQL Server 2005 database engine generates failed assertion errors when you use the Replication Monitor to monitor the distribution database
9.00.3154	934109	http://support.microsoft.com/kb/934109	FIX: The Distribution Agent generates an access violation when you configure a transaction publication to run an additional script after the snapshot is applied
9.00.3154	934188	http://support.microsoft.com/kb/934188	FIX: The Distribution Agent does not deliver commands to the Subscriber even if the Distribution Agent is running in SQL Server 2005
9.00.3153	933564	http://support.microsoft.com/kb/933564	FIX: A gradual increase in memory consumption for the USERSTORE_TOKENPERM cache store occurs in SQL Server 2005
9.00.3152	9333097	http://support.microsoft.com/kb/933097	Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available
9.00.3152	9333097	http://support.microsoft.com/kb/933097	Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available
9.00.3080	970895	http://support.microsoft.com/kb/970895/	MS09-062: Description of the security update for GDI+ for SQL Server 2005 Service Pack 2 GDR: October 13, 2009
9.00.3077	960089	http://support.microsoft.com/default.aspx/kb/960089	MS09-004: Description of the security update for SQL Server 2005 GDR: February 10, 2009
9.00.3073	954606	http://support.microsoft.com/kb/954606	MS08-052: Description of the security update for GDI+ for SQL Server 2005 Service Pack 2 GDR: September 9, 2008
9.00.3068	948109	http://support.microsoft.com/kb/948109	Description of the security update for SQL Server 2005 GDR: July 8, 2008
9.00.3054	934458	http://support.microsoft.com/kb/934458	FIX: The Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context in certain circumstances in SQL Server 2005 builds 3042 through 3053
9.00.3050	933508	http://support.microsoft.com/kb/933508	Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at different intervals than intended
9.00.3043		http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/servicepacks/sp2.mspx	Service Pack 2 Refresh
9.00.3042		N/A	Service Pack 2 Original
9.00.3026	929376	http://support.microsoft.com/kb/929376	FIX: A "17187" error message may be logged in the Errorlog file when an instance of SQL Server 2005 is under a heavy load
9.00.2233	937544	http://support.microsoft.com/kb/937544	FIX: You may receive error 3456 when you try to restore a transaction log for a SQL Server 2005 database
9.00.2227	934066	http://support.microsoft.com/kb/934066	FIX: The row of data on the publisher and the row of data on the subscriber may be inconsistent in a merge publication after synchronization has occurred in SQL Server 2005
9.00.2224	932990	http://support.microsoft.com/kb/932990	FIX: You cannot obtain statements in the current batch in SQL Server 2005 by using the DBCC INPUTBUFFER statement, trace flag 1204, deadlock graph event class, or Activity Monitor
9.00.2221	931593	http://support.microsoft.com/kb/932555	FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 2047
9.00.2219	931329	http://support.microsoft.com/kb/931329	FIX: Error message when you run a query in Microsoft SQL Server 2005: "Msg 8624, Level 16, State 116 Internal Query Processor Error
9.00.2218	931843	http://support.microsoft.com/kb/931843	FIX: SQL Server 2005 does not reclaim the disk space that is allocated to the temporary table if the stored procedure is stopped
9.00.2215	931666	http://support.microsoft.com/kb/931666	FIX: An assertion violation may be logged after you install SQL Server 2005 or after you add more processors to a server that is running SQL Server 2005
9.00.2214	930505	http://support.microsoft.com/kb/930505	FIX: Error message when you run DML statements against a table that is published for merge replication in SQL Server 2005: "Could not find stored procedure"
9.00.2214	929240	http://support.microsoft.com/kb/929240	FIX: I/O requests that are generated by the checkpoint process may cause I/O bottlenecks if the I/O subsystem is not fast enough to sustain the IO requests in SQL Server 2005
9.00.2214	930775	http://support.microsoft.com/kb/930775	FIX: Error message when you try to retrieve rows from a cursor that uses the OPTION (RECOMPILE) query hint in SQL Server 2005
9.00.2211	930284	http://support.microsoft.com/kb/930284	FIX: You receive error 1456 when you try to add a witness to a DBM session in SQL Server 2005
9.00.2211	930283	http://support.microsoft.com/kb/930283	FIX: You receive error 1456 when you add a witness to a database mirroring session and the database name is the same as an existing database mirroring session in SQL Server 2005
9.00.2209	929278	http://support.microsoft.com/kb/929278	FIX: SQL Server 2005 may not perform histogram amendments when you use trace flags 2389 and 2390
9.00.2208	929404	http://support.microsoft.com/kb/929404	FIX: Error message when you perform a transaction log backup operation and another data backup operation in parallel in SQL Server 2005: "Error 3633"
9.00.2208	929179	http://support.microsoft.com/kb/929179	FIX: A memory leak may occur every time that you synchronize a SQL Server Mobile subscriber in SQL Server 2005
9.00.2207	928789	http://support.microsoft.com/kb/928789	FIX: Error message in the database mail log when you try to use the sp_send_dbmail stored procedure to send an e-mail in SQL Server 2005: "Invalid XML message format received on the ExternalMailQueue"
9.00.2207	928394	http://support.microsoft.com/kb/928394	FIX: The changes are not reflected in the publication database after you reinitialize the subscriptions in SQL Server 2005
9.00.2207	928372	http://support.microsoft.com/kb/928372	FIX: Error message when you use a synonym for a stored procedure in SQL Server 2005: "A severe error occurred on the current command"
9.00.2206	928083	http://support.microsoft.com/kb/928083	FIX: You may receive an error message when you run a CLR stored procedure or CLR function that uses a context connection in SQL Server 2005
9.00.2202	927643	http://support.microsoft.com/kb/927643	FIX: Some search results are missing when you perform a full-text search operation on a Windows SharePoint Services 2.0 site after you upgrade to SQL Server 2005
9.00.2201	927289	http://support.microsoft.com/kb/927289	FIX: Updates to the SQL Server Mobile subscriber may not be reflected in the SQL Server 2005 merge publication
9.00.2198	926612	http://support.microsoft.com/kb/926612	FIX: SQL Server Agent does not send an alert quickly or does not send an alert when you use an alert of the SQL Server event alert type in SQL Server 2005
9.00.2198	926106	http://support.microsoft.com/kb/926106	FIX: You receive an error message when you use the Print Preview option on a large report in SQL Server 2005 Reporting Services
9.00.2198	925277	http://support.microsoft.com/kb/925277	FIX: You may experience very large growth increments of a principal database after you manually fail over a database mirroring session in SQL Server 2005
9.00.2198	924807	http://support.microsoft.com/kb/924807	FIX: The restore operation may take a long time to finish when you restore a database in SQL Server 2005
9.00.2198	924686	http://support.microsoft.com/kb/924686	FIX: The database mirroring session may remain in the synchronizing state and may stop responding when a database failover occurs in SQL Server 2005
9.00.2198	926613	http://support.microsoft.com/kb/926613	FIX: You may receive inconsistent results when you query a table that is published in a transactional replication in SQL Server 2005
9.00.2196	926024	http://support.microsoft.com/kb/926024	FIX: The query performance is very slow when you use a fast forward-only cursor to run a query in SQL Server 2005
9.00.2195	926240	http://support.microsoft.com/kb/926240	FIX: SQL Server 2005 may stop responding when you use the SqlBulkCopy class to import data from another data source
9.00.2183	924291	http://support.microsoft.com/kb/924291	FIX: Error message when you execute a user-defined function in SQL Server 2005: "Invalid length parameter passed to the SUBSTRING function"
9.00.2181	923605	http://support.microsoft.com/kb/923605	FIX: A deadlock occurs and a query never finishes when you run the query on a computer that is running SQL Server 2005 and has multiple processors
9.00.2176	922594	http://support.microsoft.com/kb/922594	FIX: Error message when you use SQL Server 2005: "High priority system task thread Operating system error Exception 0xAE encountered"
9.00.2175	922579	http://support.microsoft.com/kb/922579	FIX: The operation may take longer than you expect when you run a warm query to obtain information from the Microsoft Search service in SQL Server 2005
9.00.2175	921536	http://support.microsoft.com/kb/921536	FIX: A handled access violation may occur in the CValSwitch::GetDataX function when you run a complex query in SQL Server 2005
9.00.2175	920794	http://support.microsoft.com/kb/920794	FIX: The size of the e-mail message is very large when you use Database Mail in SQL Server 2005 to send query results to users
9.00.2167	921295	http://support.microsoft.com/kb/921295	FIX: You may receive an incorrect result when you try to run a Multidimensional Expressions (MDX) query by using SQL Server 2005
9.00.2167	921293	http://support.microsoft.com/kb/921293	FIX: The description for the Dimension field is not set in the local cube file when you use the CREATE LOCAL CUBE statement in SQL Server 2005
9.00.2164	919243	http://support.microsoft.com/kb/919243	FIX: Some rows in the Text Data column are always displayed for a trace that you create by using SQL Server Profiler in SQL Server 2005
9.00.2164	918832	http://support.microsoft.com/kb/918832	FIX: An inefficient or incorrect SQL query is generated when you try to use SQL Server 2005 to browse a ROLAP dimension
9.00.2153	919224	http://support.microsoft.com/kb/919224/en-us	Error message when you connect to an instance of SQL Server 2005 Integration Services by using SQL Server Management Studio on a computer that has a 64-bit processor
9.00.2153	918222	http://support.microsoft.com/kb/918222/en-us	Cumulative hotfix package (build 2153) for SQL Server 2005 is available
9.00.2050		http://support.microsoft.com/kb/932555	FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 2047
9.00.2047		N/A	Service Pack 1
9.00.1561	932556	http://support.microsoft.com/kb/932556	FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1500 and later builds
9.00.1558	926493	http://support.microsoft.com/kb/926493
	FIX: Error message when you restore a transaction-log backup that is generated in SQL Server 2000 SP4 to an instance of SQL Server 2005
9.00.1551	922527	http://support.microsoft.com/kb/922527	FIX: Error message when you schedule some SQL Server 2005 Integration Services packages to run as jobs: "Package has been cancelled"
9.00.1545	919193	http://support.microsoft.com/kb/919193	FIX: A forward-only cursor may be implicitly converted to a keyset cursor in SQL Server 2005
9.00.1532	916046	N/A	KB916046 : FIX: Indexes may grow very large when you insert a row into a table and then update the same row in SQL Server 2005>KB916046 : FIX: Indexes may grow very large when you insert a row into a table and then update the same row in SQL Server 2005		http://support.microsoft.com/kb/916046
9.00.1528	915307	http://support.microsoft.com/kb/915307	FIX: You experience a slow uploading process if conflicts occur when many merge agents upload changes
9.00.1528	915306	http://support.microsoft.com/kb/915306	FIX: The merge agent fails and a "permission denied" error message is logged when you synchronize a SQL Server 2005-based merge publication
9.00.1528	915309	http://support.microsoft.com/kb/915309	FIX: When you start a merge agent, synchronization between the subscriber and the publisher takes a long time to be completed in SQL
9.00.1528	915308	http://support.microsoft.com/kb/915308	FIX: The CPU usage of the server reaches 100% when many DML activities occur in SQL Server 2005
9.00.1519	913494	http://support.microsoft.com/kb/932557	FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1399
9.00.1406	932557	http://support.microsoft.com/kb/932557	FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1399
9.00.1399		N/A	RTM

Script to Get PK and FK

set nocount on
create table #PK(constraint_schema sysname not null, constraint_name sysname not null, sql varchar(4000) not null, constraint PK_#PK1 primary key clustered(constraint_schema, constraint_name))

create table #cols(constraint_schema sysname not null, constraint_name sysname not null, column_name sysname not null, ordinal_position int not null, constraint PK_#PKcol primary key clustered(constraint_schema, constraint_name, ordinal_position))

create table #FK(constraint_schema sysname not null, constraint_name sysname not null,
unique_constraint_schema sysname not null, unique_constraint_name sysname not null,
sql varchar(4000) not null, constraint PK_#FK primary key clustered(constraint_schema, constraint_name))

insert into #PK
select constraint_schema, constraint_name, 'ALTER TABLE ' + quotename(table_schema) + '.' + quotename(TABLE_NAME) +
' ADD CONSTRAINT ' + quotename(CONSTRAINT_NAME) +
' PRIMARY KEY ' + CASE WHEN si.indid<>1 THEN 'NON' ELSE '' END +
'CLUSTERED (>cols<) WITH FILLFACTOR=' + cast(si.OrigFillFactor as varchar) + ' ON ' + quotename(fg.groupname) AS SQL from INFORMATION_SCHEMA.TABLE_CONSTRAINTS TC INNER JOIN sysindexes si on TC.CONSTRAINT_NAME=si.name inner join sysfilegroups fg on si.groupid=fg.groupid WHERE CONSTRAINT_TYPE IN('PRIMARY KEY','UNIQUE') and TC.CONSTRAINT_NAME not in(Select CONSTRAINT_NAME from kds.INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE where CONSTRAINT_NAME like 'p%') insert into #fk select c.constraint_schema, c.constraint_name, c.unique_constraint_schema, c.unique_constraint_name, 'ALTER TABLE ' + quotename(F.table_schema) + '.' + quotename(F.table_name) + ' ADD CONSTRAINT ' + quotename(F.constraint_name) + ' FOREIGN KEY(>cols<) REFERENCES ' + quotename(r.table_schema) + '.' + quotename(r.table_name) + '(>rcols<)' AS sql FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS F INNER JOIN INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS C ON F.constraint_schema=C.constraint_schema AND f.constraint_name=c.constraint_name AND F.constraint_type='FOREIGN KEY' INNER JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS R ON R.constraint_schema=C.unique_constraint_schema AND r.constraint_name=c.unique_constraint_name AND r.constraint_type in ('PRIMARY KEY','UNIQUE') ORDER BY F.table_name, r.table_name insert into #cols select constraint_schema, constraint_name, COLUMN_NAME, ORDINAL_POSITION from INFORMATION_SCHEMA.KEY_COLUMN_USAGE declare @ctr int, @max int, @delim varchar(1) select @ctr=1, @max=max(ordinal_position), @delim='' from #cols set nocount on while @ctr<=@max BEGIN update P SET SQL=Replace(SQL, '>cols<', @delim + quotename(c.column_name) + '>cols<') FROM #PK P INNER JOIN #cols C ON P.constraint_schema=C.constraint_schema AND P.constraint_name=C.constraint_name WHERE C.ORDINAL_POSITION=@ctr UPDATE F SET SQL=Replace(Replace(SQL, '>cols<', @delim + quotename(c.column_name) + '>cols<'), '>rcols<', @delim + quotename(r.column_name) + '>rcols<') FROM #FK F INNER JOIN #cols C ON F.constraint_schema=C.constraint_schema AND F.constraint_name=C.constraint_name AND C.ordinal_position=@ctr INNER JOIN #cols R ON F.unique_constraint_schema=R.constraint_schema AND F.unique_constraint_name=R.constraint_name AND C.ordinal_position=R.ordinal_position select @ctr=@ctr+1, @delim=',' END set nocount on update #PK SET SQL=Replace(SQL, '>cols<', '') update #FK SET SQL=Replace(Replace(SQL, '>cols<', ''), '>rcols<', '')

select sql from #PK
select sql from #FK

--drop table #pk
--drop table #fk
--drop table #cols

Ports Used By SQL Server

Ports Used By the Database Engine

The following table lists the ports that are frequently used by the Database Engine.

Scenario	Port	Comments
SQL Server default instance running over TCP	TCP port 1433	This is the most common port allowed through the firewall. It applies to routine connections to the default installation of the Database Engine, or a named instance that is the only instance running on the computer. (Named instances have special considerations. See Dynamic Ports later in this topic.)
SQL Server named instances in the default configuration	The TCP port is a dynamic port determined at the time the Database Engine starts.Â	See the discussion below in the section Dynamic Ports. UDP port 1434 might be required for the SQL Server Browser Service when you are using named instances.
SQL Server named instances when they are configured to use a fixed port	The port number configured by the administrator.	See the discussion below in the section Dynamic Ports.
Dedicated Admin Connection	TCP port 1434 for the default instance. Other ports are used for named instances. Check the error log for the port number.	By default, remote connections to the Dedicated Administrator Connection (DAC) are not enabled. To enable remote DAC, use the Surface Area Configuration facet. For more information, see Understanding Surface Area Configuration.
SQL Server Browser service	UDP port 1434	The SQL Server Browser service listens for incoming connections to a named instance and provides the client the TCP port number that corresponds to that named instance. Normally the SQL Server Browser service is started whenever named instances of the Database Engine are used. The SQL Server Browser service does not have to be started if the client is configured to connect to the specific port of the named instance.
SQL Server instance running over an HTTP endpoint.	Can be specified when an HTTP endpoint is created. The default is TCP port 80 for CLEAR_PORT traffic and 443 for SSL_PORT traffic.	Used for an HTTP connection through a URL.
SQL Server default instance running over an HTTPS endpoint.	TCP port 443	Used for an HTTPS connection through a URL. HTTPS is an HTTP connection that uses secure sockets layer (SSL).
Service Broker	TCP port 4022. To verify the port used, execute the following query: SELECT name, protocol_desc, port, state_desc FROM sys.tcp_endpoints WHERE type_desc = 'SERVICE_BROKER'	There is no default port for SQL Server Service Broker, but this is the conventional configuration used in Books Online examples.
Database Mirroring	Administrator chosen port. To determine the port, execute the following query: SELECT name, protocol_desc, port, state_desc FROM sys.tcp_endpoints WHERE type_desc = 'DATABASE_MIRRORING'	There is no default port for Database mirroring however Books online examples use TCP port 7022. It is very important to avoid interrupting an in-use mirroring endpoint, especially in high-safety mode with automatic failover. Your firewall configuration must avoid breaking quorum. For more information, see Specifying a Server Network Address (Database Mirroring).
Replication	Replication connections to SQL Server use the typical regular Database Engine ports (TCP port 1433 for the default instance, etc.) Web synchronization and FTP/UNC access for replication snapshot require additional ports to be opened on the firewall. To transfer initial data and schema from one location to another, replication can use FTP (TCP port 21), or sync over HTTP (TCP port 80) or File and Print Sharing (TCP port 137,138, or 139).	For sync over HTTP, replication uses the IIS endpoint (ports for which are configurable but is port 80 by default), but the IIS process connects to the backend SQL Server through the standard ports (1433 for the default instance. During Web synchronization using FTP, the FTP transfer is between IIS and the SQL Server publisher, not between subscriber and IIS. For more information, see Configuring Microsoft Internet Security and Acceleration Server for Microsoft SQL Server 2000 Replication over the Internet.
Transact-SQL debugger	TCP port 135 See Special Considerations for Port 135 The IPsec exception might also be required.	If using Visual Studio, on the Visual Studio host computer, you must also add Devenv.exe to the Exceptions list and open TCP port 135. If using Management Studio, on the Management Studio host computer, you must also add ssms.exe to the Exceptions list and open TCP port 135. For more information, see Configuring the Transact-SQL Debugger.

For step by step instructions to configure the Windows Firewall for the Database Engine, see How to: Configure a Windows Firewall for Database Engine Access.

Dynamic Ports

By default, named instances (including SQL Server Express) use dynamic ports. That means that every time that the Database Engine starts, it identifies an available port and uses that port number. If the named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433. If other instances of the Database Engine are installed, it will probably use a different TCP port. Because the port selected might change every time that the Database Engine is started, it is difficult to configure the firewall to enable access to the correct port number. Therefore, if a firewall is used, we recommend reconfiguring the Database Engine to use the same port number every time. This is called a fixed port or a static port. For more information, see Configuring a Fixed Port.

An alternative to configuring a named instance to listen on a fixed port is to create an exception in the firewall for a SQL Server program such as sqlservr.exe (for the Database Engine). This can be convenient, but the port number will not appear in the Local Port column of the Inbound Rules page when you are using the Windows Firewall with Advanced Security MMC snap-in. This can make it more difficult to audit which ports are open. Another consideration is that a service pack or cumulative update can change the path to the SQL Server executable which will invalidate the firewall rule.

Undocumented DBCC commands

Undocumented DBCC commands

Here you can find some useful undocumented DBCC commands.

1. DBCC BUFFER

This command can be used to display buffer headers and pages from the buffer cache.

Syntax:

dbcc buffer ([dbid|dbname] [,objid|objname] [,nbufs], [printopt])

where dbid|dbname - database id|database name objid|objname - object id|object name nbufs - number of buffers to examine printopt - print option 0 - print out only the buffer header and page header (default) 1 - print out each row separately and the offset table 2 - print out each row as a whole and the offset table

This is the example:

DBCC TRACEON (3604) dbcc buffer(master,'sysobjects')

2. DBCC BYTES

This command can be used to dump out bytes from a specific address.

Syntax:

dbcc bytes ( startaddress, length )

where startaddress - starting address to dump length - number of bytes to dump

This is the example:

DBCC TRACEON (3604) dbcc bytes (10000000, 100)

3. DBCC DBINFO

Displays DBINFO structure for the specified database.

Syntax:

DBCC DBINFO [( dbname )]

where dbname - is the database name.

This is the example:

DBCC TRACEON (3604) DBCC DBINFO (master)

4. DBCC DBTABLE

This command displays the contents of the DBTABLE structure.

Syntax:

DBCC DBTABLE ({dbid|dbname})

where dbid|dbname - database name or database ID

This is the example:

DBCC TRACEON (3604) DBCC DBTABLE (master)

The DBTABLE structure has an output parameter called dbt_open. This parameter keeps track of how many users are in the database.

Look at here for more details:
FIX: Database Usage Count Does Not Return to Zero

5. DBCC DES

Prints the contents of the specified DES (descriptor).

Syntax:

dbcc des [( [dbid|dbname] [,objid|objname] )]

where dbid|dbname - database id|database name. objid|objname - object id|object name

This is the example:

DBCC TRACEON (3604) DBCC DES

6. DBCC HELP

DBCC HELP returns syntax information for the specified DBCC statement. In comparison with DBCC HELP command in version 6.5, it returns syntax information only for the documented DBCC commands.

Syntax:

DBCC HELP ('dbcc_statement' | @dbcc_statement_var | '?')

This is the example:

DBCC TRACEON (3604) DECLARE @dbcc_stmt sysname SELECT @dbcc_stmt = 'CHECKTABLE' DBCC HELP (@dbcc_stmt)

7. DBCC IND

Shows all pages in use by indexes of the specified table.

Syntax:

dbcc ind( dbid|dbname, objid|objname, printopt = {-2|-1|0|1|2|3} )

where dbid|dbname - database id|database name. objid|objname - object id|object name printopt - print option

There is change in this command in how it is used in SQL Server 7.0, in that the printopt parameter is now no longer optional.

This is the example:

DBCC TRACEON (3604) DBCC IND (master, sysobjects, 0)

8. DBCC log

This command is used to view the transaction log for the specified database.

Syntax:

DBCC log ( {dbid|dbname}, [, type={-1|0|1|2|3|4}] )

PARAMETERS: Dbid or dbname - Enter either the dbid or the name of the database in question. type - is the type of output: 0 - minimum information (operation, context, transaction id) 1 - more information (plus flags, tags, row length, description) 2 - very detailed information (plus object name, index name, page id, slot id) 3 - full information about each operation 4 - full information about each operation plus hexadecimal dump of the current transaction log's row. -1 - full information about each operation plus hexadecimal dump of the current transaction log's row, plus Checkpoint Begin, DB Version, Max XDESID by default type = 0

To view the transaction log for the master database, run the following command:

DBCC log (master)

9. DBCC PAGE

You can use this command to view the data page structure.

Syntax:

DBCC PAGE ({dbid|dbname}, pagenum [,print option] [,cache] [,logical])

PARAMETERS: Dbid or dbname - Enter either the dbid or the name of the database in question. Pagenum - Enter the page number of the SQL Server page that is to be examined. Print option - (Optional) Print option can be either 0, 1, or 2. 0 - (Default) This option causes DBCC PAGE to print out only the page header information. 1 - This option causes DBCC PAGE to print out the page header information, each row of information from the page, and the page's offset table. Each of the rows printed out will be separated from each other. 2 - This option is the same as option 1, except it prints the page rows as a single block of information rather than separating the individual rows. The offset and header will also be displayed. Cache - (Optional) This parameter allows either a 1 or a 0 to be entered. 0 - This option causes DBCC PAGE to retrieve the page number from disk rather than checking to see if it is in cache. 1 - (Default) This option takes the page from cache if it is in cache rather than getting it from disk only. Logical - (Optional) This parameter is for use if the page number that is to be retrieved is a virtual page rather then a logical page. It can be either 0 or 1. 0 - If the page is to be a virtual page number. 1 - (Default) If the page is the logical page number.

This is the example:

DBCC TRACEON (3604) DBCC PAGE (master, 1, 1)

Look at here for more details:
Data page structure in MS SQL 6.5

10. DBCC procbuf

This command displays procedure buffer headers and stored procedure headers from the procedure cache.

Syntax:

DBCC procbuf( [dbid|dbname], [objid|objname], [nbufs], [printopt = {0|1}] )

where dbid|dbname - database id|database name. objid|objname - object id|object name nbufs - number of buffers to print printopt - print option (0 print out only the proc buff and proc header (default) 1 print out proc buff, proc header and contents of buffer)

This is the example:

DBCC TRACEON (3604) DBCC procbuf(master,'sp_help',1,0)

11. DBCC prtipage

This command prints the page number pointed to by each row on the specified index page.

Syntax:

DBCC prtipage( dbid, objid, indexid, indexpage )

where dbid - database ID objid - object ID indexid - index ID indexpage - the logical page number of the index page to dump

This is the example:

DBCC TRACEON (3604) DECLARE @dbid int, @objectid int SELECT @dbid = DB_ID('master') SELECT @objectid = object_id('sysobjects') DBCC prtipage(@dbid,@objectid,1,0)

12. DBCC pss

This command shows info about processes currently connected to the server.

Syntax:

DBCC pss( suid, spid, printopt = { 1 | 0 } )

where suid - server user ID spid - server process ID printopt - print option (0 standard output, 1 all open DES's and current sequence tree)

This is the example:

DBCC TRACEON (3604) dbcc pss

13. DBCC resource

This command shows the server's level RESOURCE, PERFMON and DS_CONFIG information. RESOURCE shows addresses of various data structures used by the server. PERFMON structure contains master..spt_monitor field info. DS_CONFIG structure contains master..syscurconfigs field information.

Syntax:

DBCC resource

This is the example:

DBCC TRACEON (3604) DBCC resource

14. DBCC TAB

You can use the following undocumented command to view the data pages structure (in comparison with DBCC PAGE, this command will return information about all data pages for viewed table, not only for particular number).

Syntax:

DBCC tab (dbid, objid)

where dbid - is the database id objid - is the table id

This is the example:

DBCC TRACEON (3604) DECLARE @dbid int, @objectid int SELECT @dbid = DB_ID('master') SELECT @objectid = object_id('sysdatabases') DBCC TAB (@dbid,@objectid)

Maximum Capacity Specifications for SQL Server

The following table specifies the maximum sizes and numbers of various objects defined in SQL Server databases or referenced in Transact-SQL statements.

SQL Server Database Engine object	Maximum sizes/numbers SQL Server (32-bit)	Maximum sizes/numbers SQL Server (64-bit)
Batch size1	65,536 * Network Packet Size	65,536 * Network Packet Size
Bytes per short string column	8,000	8,000
Bytes per GROUP BY, ORDER BY	8,060	8,060
Bytes per index key2	900	900
Bytes per foreign key	900	900
Bytes per primary key	900	900
Bytes per row8	8,060	8,060
Bytes in source text of a stored procedure	Lesser of batch size or 250 MB	Lesser of batch size or 250 MB
Bytes per varchar(max), varbinary(max), xml, text, or image column	2^31-1	2^31-1
Characters per ntext or nvarchar(max) column	2^30-1	2^30-1
Clustered indexes per table	1	1
Columns in GROUP BY, ORDER BY	Limited only by number of bytes	Limited only by number of bytes
Columns or expressions in a GROUP BY WITH CUBE or WITH ROLLUP statement	10	10
Columns per index key7	16	16
Columns per foreign key	16	16
Columns per primary key	16	16
Columns per nonwide table	1,024	1,024
Columns per wide table	30,000	30,000
Columns per SELECT statement	4,096	4,096
Columns per INSERT statement	4096	4096
Connections per client	Maximum value of configured connections	Maximum value of configured connections
Database size	524,272 terabytes	524,272 terabytes
Databases per instance of SQL Server	32,767	32,767
Filegroups per database	32,767	32,767
Files per database	32,767	32,767
File size (data)	16 terabytes	16 terabytes
File size (log)	2 terabytes	2 terabytes
Foreign key table references per table4	253	253
Identifier length (in characters)	128	128
Instances per computer	50 instances on a stand-alone server for all SQL Server editions. SQL Server supports 25 instances on a failover cluster.	50 instances on a stand-alone server. 25 instances on a failover cluster.
Length of a string containing SQL statements (batch size)1	65,536 * Network packet size	65,536 * Network packet size
Locks per connection	Maximum locks per server	Maximum locks per server
Locks per instance of SQL Server5	Up to 2,147,483,647	Limited only by memory
Nested stored procedure levels6	32	32
Nested subqueries	32	32
Nested trigger levels	32	32
Nonclustered indexes per table	999	999
Number of distinct expressions in the GROUP BY clause when any of the following are present: CUBE, ROLLUP, GROUPING SETS, WITH CUBE, WITH ROLLUP	32	32
Number of grouping sets generated by operators in the GROUP BY clause	4,096	4,096
Parameters per stored procedure	2,100	2,100
Parameters per user-defined function	2,100	2,100
REFERENCES per table	253	253
Rows per table	Limited by available storage	Limited by available storage
Tables per database3	Limited by number of objects in a database	Limited by number of objects in a database
Partitions per partitioned table or index	1,000	1,000
Statistics on non-indexed columns	30,000	30,000
Tables per SELECT statement	Limited only by available resources	Limited only by available resources
Triggers per table3	Limited by number of objects in a database	Limited by number of objects in a database
Columns per UPDATE statement (Wide Tables)	4096	4096
User connections	32,767	32,767
XML indexes	249	249

1Network 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 KB, and is controlled by the network packet size configuration option.

2The maximum number of bytes in any index key cannot exceed 900 in SQL Server. 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, you can include nonkey columns in a nonclustered index to avoid the maximum index key size of 900 bytes.

3Database objects include objects such as tables, views, 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.

4Although 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.

5This value is for static lock allocation. Dynamic locks are limited only by memory.

6If a stored procedure accesses more than 8 databases, or more than 2 databases in interleaving, you will receive an error.

7If 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, you can include nonkey columns in a nonclustered index to avoid the limitation of a maximum of 16 key columns. For more information, see Index with Included Columns.

8SQL Server 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. For more information, see the "Row-Overflow Data Exceeding 8 KB" topic in SQL Server Books Online.

SQL Server Utility Objects

---

The following table specifies the maximum sizes and numbers of various objects that were tested in the SQL Server Utility.

SQL Server Utility object	Maximum sizes/numbers SQL Server (32-bit)	Maximum sizes/numbers SQL Server (64-bit)
Computers (physical computers or virtual machines) per SQL Server Utility	100	100
Instances of SQL Server per computer	5	5
Total number of instances of SQL Server per SQL Server Utility	2001	2001
User databases per instance of SQL Server, including data-tier applications	50	50
Total number of user databases per SQL Server Utility	1,000	1,000
File groups per database	1	1
Data files per file group	1	1
Log files per database	1	1
Volumes per computer	3	3

1 SQL Server 2008 R2 Datacenter supports a SQL Server Utility with a maximum of 200 managed instances of SQL Server. SQL Server 2008 R2 Enterprise supports a SQL Server Utility with a maximum of 25 managed instances of SQL Server. For getting started information, see Overview of SQL Server Utility.

SQL Server Data-tier Application Objects

---

The following table specifies the maximum sizes and numbers of various objects that were tested in the SQL Server data-tier applications (DAC).

SQL Server DAC object	Maximum sizes/numbers SQL Server (32-bit)	Maximum sizes/numbers SQL Server (64-bit)
Databases per DAC	1	1
Objects per DAC1	Limited by the number of objects in a database, or available memory.	Limited by the number of objects in a database, or available memory.

1The types of objects included in the limit are users, tables, views, stored procedures, user-defined functions, user-defined data type, database roles, schemas, and user-defined table types.

Replication Objects

---

The following table specifies the maximum sizes and numbers of various objects defined in SQL Server Replication.

SQL Server Replication object	Maximum sizes/numbers SQL Server (32-bit)	Maximum sizes/numbers SQL Server (64-bit)
Articles (merge publication)	256	256
Articles (snapshot or transactional publication)	32,767	32,767
Columns in a table1 (merge publication)	246	246
Columns in a table2 (SQL Server snapshot or transactional publication)	1,000	1,000
Columns in a table2 (Oracle snapshot or transactional publication)	995	995
Bytes for a column used in a row filter (merge publication)	1,024	1,024
Bytes for a column used in a row filter (snapshot or transactional publication)	8,000	8,000

1If row tracking is used for conflict detection (the default), the base table can include a maximum of 1,024 columns, but columns must be filtered from the article so that a maximum of 246 columns is published. If column tracking is used, the base table can include a maximum of 246 columns. For more information on the tracking level, see the "Tracking Level" section of How Merge Replication Detects and Resolves Conflicts.

2The base table can include the maximum number of columns allowable in the publication database (1,024 for SQL Server), but columns must be filtered from the article if they exceed the maximum specified for the publication type.