Getting that going can be a hassle, depending on your infrastructure. This is usually a problem with delegation and security. You may also find that accessing files on the network is harder than accessing the same file on a local disk. You will want to be sure that the provider representing your drivers (look under the Linked servers folder for the Providers folder) is set to "Allow in process" and. There should be plenty of examples of how to create linked servers using ACE drivers (both with TSQL and the SSMS GUI) on the internet. You can just create the linked server and go. With the new drivers, you don't need to create a system DSN like with the old ODBC drivers. The redistributable ACE drivers are available for download on Microsoft's site. The release for Office 2010 that comes in 32 bit and 64 bit versions. They are OLEDB based, but you wouldn't necessarily notice. These drivers replace the old "JET" drivers and were introduced with Office 2007. On recent versions of SQL Server, 2005+, I've had the best success with the "ACE" drivers. I have had the old ODBC drivers from Microsoft bring down server instances, so i avoid them. 64 bit SQL Servers can't use 32 bit ODBC (or OLEDB or anything else) drivers. The first thing to do is to make sure that you are using 32 bit drivers if you have a 32 bit SQL Server and 64 bit drivers if you are using a 64 bit SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |