3136) 9/27/2007 Q195761 INF: Frequently Asked Questions - Failover (Q195761)
This article is meant to address frequently asked questions regarding SQL Server 7.0 failover support. 3137) 9/30/2007 Q296438 FIX: Error Message 1205 Is Not Returned with the Localized Message Text (Q296438)
If a deadlock occurs, SQL Server chooses one of the deadlocking system process IDs (SPIDs) as the deadlock victim, terminates the SPID, and then notifies the client application by returning error number 1205. 3138) 1/11/2007 Q308401 FIX: SQLExecute on a Prepared Statement with SQL_NOSCAN_ON Causes Client-Side AV (Q308401)
When you execute a statement that was prepared with the SQL_ATTR_NOSCAN attribute, you may receive an access violation (AV) as follows: 3139) 9/14/2006 Q301953 SQLOLEDB: Unenlisting From Active Transaction Against SQL Server 7.0 Causes Hang and Drain Abort Entry (Q301953)
When using the SQL Server native provider (SQLOLEDB) against a SQL Server 7.0 database, and when running in a transactional context such as MTS or COM+, directly or indirectly releasing an OLE DB session object that is enlisted in a distrib 3140) 12/18/2006 Q302248 FIX: SQLOLEDB Does Not Work with DBACCESSOR_OPTIMIZED Flag and SSPROP_ENABLEFASTLOAD (Q302248)
Using the Microsoft OLEDB Provider for SQL Server (SQLOLEDB) that comes with Microsoft Data Access Components (MDAC) version 2.6 or 2.6 SP1, when you set the value of the SSPROP_ENABLEFASTLOAD property to true in the SQLSERVERDATASOURCE pro 3141) 11/13/2006 Q303446 FIX: SQLOLEDB Returns No Data When Using AutoFetch Option with Fast Forward Cursors (Q303446)
The SQL Server native provider (SQLOLEDB) may return no data for a VARCHAR field that is larger than 255 characters under the following conditions: 3142) 7/11/2007 Q300420 FIX: Connection to SQL Server Database Using IP Address Is Unusually Slow (Q300420)
When Microsoft Data Access Components (MDAC) version 2.6 is installed, each attempt to connect to a SQL Server 7.0 or SQL Server 2000 database using an IP address (rather than the server name) may take longer than anticipated. In certain re 3143) 9/29/2007 Q297035 FIX: Correlation Error Using Parameters.Refresh with SQLOLEDB (Q297035)
When executing a parameterized UNION query with the SQLOLEDB OLEDB Provider, the following error may be reported: 3144) 1/13/2007 Q299717 FIX: Query Method Used to Access Data May Allow Rights that the Login Might Not Normally Have (Q299717)
Logins that use the SQL Server Authentication (Standard) security mode with a particular query method used to access data from an OLE-DB data source may allow rights that the login might not normally have. 3145) 9/2/2007 Q159976 HOW TO: Connect to the Microsoft SQL Server Through the Use of Named Pipes (Q159976)
When you connect to Microsoft SQL Server from the Active Server Pages (ASP) using ActiveX Data Objects via named pipes, the client computer must be validated by SQL Server to use the named pipe. If SQL Server is on a different physical comp 3146) 9/20/2007 Q311348 BETA-PRB: Error in SQL Server 7.0 When You Call Command.Prepare Before You Add Parameters Using Visual C# .NET (Q311348)
When you create a parameterized command against Microsoft SQL Server 7.0, if you call the 3147) 5/12/2007 Q310368 BETA-PRB: Error in SQL Server 7.0 When You Call Command.Prepare Before You Add Parameters Using Visual Basic .NET (Q310368)
When you create a parameterized command against Microsoft SQL Server 7.0, if you call the
1
2
.... .... 202
203
204
205
206
207
208
209
[ 210 ]
Previous Page
Page 210 of 210
|