When you use the Jet OLEDB Provider (OLE DB Provider for Jet [Text IISAM]) to access a text file from a SQL Server linked server, the query may take a very long time. The slow query performance only occurs when there are a large number of columns in the text file.
The Jet OLEDB Provider is querying the Jet Property Manager
on a property-by-property basis for each column. Starting with Jet 4.0 Service Pack 5 (SP5) the query is performed in a bulk mode, which speeds up the query considerably.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
INF: How to Obtain the Latest SQL Server 2000 Service Pack
This problem has been fixed in the latest edition of the Jet Service Pack.
For additional information about how to obtain the latest version of the Jet 4.0 database engine, click the following article number to view the article in the Microsoft Knowledge Base:
How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0 Database Engine
To work around the problem, use a different provider to query the text file from SQL Server.
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
The computer stops responding (hangs) when SQL Server calls IDBSchemaRowset::GetRowset(DBSCHEMA_COLUMNS).
Steps to Reproduce Behavior
To reproduce the behavior, run the code sample that follows.
: This sample assumes that the C:\MyDir\TextFile.txt file has 255 columns.
@server = 'My Documents',
@provider = 'Microsoft.Jet.OLEDB.4.0',
@srvproduct = 'OLE DB Provider for Jet (Text IISAM)',
@datasrc = 'c:\MyDir\',
@provstr = 'Text'
exec sp_addlinkedsrvlogin 'My Documents', false, NULL, 'admin'
SELECT * FROM [My Documents]...[TextFile#txt]
exec sp_droplinkedsrvlogin 'My Documents', null
exec sp_dropserver 'My Documents'