1111) 2/6/2012 911310 Error message when you run a Transact-SQL query that involves one or more SQL Server CLR Integration (SQLCLR) objects in SQL Server 2005: "Msg 6535"
1112) 2/4/2012 912397 The SQL Server service cannot start when you change a protocol parameter for a clustered instance of SQL Server 2000 or of SQL Server 2005 to a value that is not valid
1113) 1/31/2012 912417 The module information is represented incorrectly when you profile managed code that is running in SQL Server 2005 by using performance tools in Visual Studio Team Edition for Software Developers
1114) 2/8/2012 912428 Error message when you try to replicate a table from SQL Server 2005 to SQL Server 2005 Mobile Edition: "HRESULT 0x80004005 (0)"
1115) 2/4/2012 911839 How to change the SQL Server 2005 service accounts by using the Windows Management Instrumentation (WMI) Provider for Configuration Management
1116) 2/3/2012 912389 BUG: The query does not use the indexed view in SQL Server 2005 Enterprise Edition
1117) 2/7/2012 908018 How to create a package template in SQL Server Business Intelligence Development Studio
1118) 2/6/2012 912399 Event ID: 1023 occurs, and counter data is not logged when you use Performance Monitor to collect data from SQL Server 2005 Analysis Services performance counters
1119) 2/7/2012 911936 The installation may fail and you may receive an error message when you try to install the DTS redistributable package for SQL Server 2005 on a Windows 2000 Advanced Server SP4-based computer
1120) 2/5/2012 910512 Custom events information from a child package is not logged under the log provider context of the parent package in SQL Server 2005 Integration Services
1121) 2/8/2012 912426 How to detect the status of the SQL Server Express service or start the SQL Server Express service by using Visual Basic or Visual C#
1122) 2/6/2012 910416 FIX: Error message when you run certain queries or certain stored procedures in SQL Server 2005: "A severe error occurred on the current command"
1123) 1/25/2012 911847 The user access option of a SQL Server 2005 database may unexpectedly be set to SINGLE_USER when you restore the database by using a backup file
1124) 2/1/2012 910419 FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services
1125) 2/6/2012 912412 Error message when you use Service Broker or database mirroring to connect to an instance of SQL Server 2005: "Connection handshake failed"
1
2
.... .... 71
72
73
74
[ 75 ]
76
77
78
79
.... 86
Previous Page
Page 75 of 86
Next Page
|