Voici 7 façons de déterminer la version de SQL Server installé.
1ère méthode : via une requête
select @@VERSION
2ème méthode : via une requête
SELECT
SERVERPROPERTY (‘productversion’) AS ProductVersion,
SERVERPROPERTY (‘ResourceVersion’) AS ResourceVersion ,
SERVERPROPERTY (‘productlevel’) AS ProductLevel,
SERVERPROPERTY (‘edition’) AS Edition,
SERVERPROPERTY (‘ResourceLastUpdateDateTime’) AS LastUpdate
3ème méthode : via VB.Net
Dim oCon As SqlClient.SqlConnection = New SqlClient.SqlConnection
oCon.ConnectionString = « server=op00spprq1ppr;Integrated Security=SSPI »
oCon.Open()
Debug.WriteLine(oCon.ServerVersion)
oCon.Close()4ème méthode : via PowerShell
5ème méthode : via les rapports standards Reporting Services embarqués dans SQL Server 2005
6ème méthode : via le menu propriétés
7ème méthode : via l’onglet « object Explorer Details »
Une fois la version connue, vous pouvez vous reporter au tableau ci-dessous, qui liste l’ensemble des versions de SQL Serveur 2005 (commence par 9.) et donne leur caractéristique.
Build | KB Ref. | Desc. |
9.00.3257 | 951217 | Cumulative update package 8 for SQL Server 2005 Service Pack 2 as of June 16, 2008 |
9.00.3239 | 949095 | Cumulative update package 7 for SQL Server 2005 Service Pack 2 available as of April 28, 2008 |
9.00.3232 | 949959 | Merge Replication Hotfix |
9.00.3231 | 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 | 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 | 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 | 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 | Cumulative update package 3 for SQL Server 2005 Service Pack 2 |
9.00.3182 | N/A | On-demand build with hotfixes: 50001298, 50001324, and 50001440 |
9.00.3180 | 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 | On-demand build with hotfixes: 50001482 and 50001194 |
9.00.3178 | N/A | On-demand build with hotfixes: 50001193 and 50001352 |
9.00.3177 | N/A | On-demand build with hotfixes: 50001391, 50001367, 50001379, 50001408, and 50001397 |
9.00.3175 | 936305 | Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available |
9.00.3171 | 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 | 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 | 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.3161 | 935356 | Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available |
9.00.3159 | 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 | 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 | FIX: You may receive an access violation when you perform a bulk copy operation in SQL Server 2005 |
9.00.3154 | 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 | FIX: The Distribution Agent does not deliver commands to the Subscriber even if the Distribution Agent is running in SQL Server 2005 |
9.00.3154 | 934106 | FIX: SQL Server 2005 database engine generates failed assertion errors when you use the Replication Monitor to monitor the distribution database |
9.00.3153 | 933564 | FIX: A gradual increase in memory consumption for the USERSTORE_TOKENPERM cache store occurs in SQL Server 2005 |
9.00.3152 | 9333097 | Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available |
9.00.3152 | 9333097 | Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available |
9.00.3054 | 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 | Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at different intervals than intended |
9.00.3043 | Service Pack 2 Refresh | |
9.00.3042 | Service Pack 2 Original | |
9.00.3026 | 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 | FIX: You may receive error 3456 when you try to restore a transaction log for a SQL Server 2005 database |
9.00.2227 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | FIX: You receive error 1456 when you try to add a witness to a DBM session in SQL Server 2005 |
9.00.2211 | 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 | FIX: SQL Server 2005 may not perform histogram amendments when you use trace flags 2389 and 2390 |
9.00.2208 | 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 | FIX: A memory leak may occur every time that you synchronize a SQL Server Mobile subscriber in SQL Server 2005 |
9.00.2207 | 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 | FIX: The changes are not reflected in the publication database after you reinitialize the subscriptions in SQL Server 2005 |
9.00.2207 | 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 | 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 | 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 | FIX: Updates to the SQL Server Mobile subscriber may not be reflected in the SQL Server 2005 merge publication |
9.00.2198 | 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 | 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 | 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 | FIX: The restore operation may take a long time to finish when you restore a database in SQL Server 2005 |
9.00.2198 | 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 | 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 | 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 | FIX: SQL Server 2005 may stop responding when you use the SqlBulkCopy class to import data from another data source |
9.00.2183 | 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 | 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 | FIX: Error message when you use SQL Server 2005: « High priority system task thread Operating system error Exception 0xAE encountered » |
9.00.2175 | 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 | 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.2175 | 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.2167 | 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 | 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 | 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.2164 | 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.2153 | 918222 | Cumulative hotfix package (build 2153) for SQL Server 2005 is available |
9.00.2153 | 919224 | 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.2050 | 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.2050 | Update for SQL Server 2005 Service Pack 1 – .NET Vulnerability | |
9.00.2047 | Service Pack 1 | |
9.00.1561 | 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 | 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 | 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 | FIX: A forward-only cursor may be implicitly converted to a keyset cursor in SQL Server 2005 |
9.00.1532 | 916046 | http://support.microsoft.com/?kbid=916046 |
9.00.1528 | 915307 | FIX: You experience a slow uploading process if conflicts occur when many merge agents upload changes |
9.00.1528 | 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 | FIX: When you start a merge agent, synchronization between the subscriber and the publisher takes a long time to be completed in SQL Server 2005 |
9.00.1528 | 915308 | FIX: The CPU usage of the server reaches 100% when many DML activities occur in SQL Server 2005 |
9.00.1519 | 913494 | FIX: The merge agent does not use a specified custom user update to handle conflicting UPDATE statements in SQL Server 2005 |
9.00.1406 | 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 | RTM |
[Update] : Sur le blog de Christian Robert, vous pouvez trouvez un tableau identique incluant les versions précédente de SQL Server tableau
Pas de commentaire reçu(s)
Laisser une réponse