Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-04-27 : 09:21:35
|
| James writes "My OLEDB link to an Oracle database from SQL Server performs far slower than a linked table to the same data source from an Access97 database.Does anyone have an explanation for this? Surely they are using the same data provider?I've tried both Microsoft OLE DB Provider for ODBC and Microsoft OLE DB Provider for Oracle." |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-04-27 : 09:26:52
|
| It depends on where your Access database file is stored. If it's on the SQL Server's hard drive, then it can be accessed without any network overhead. I assume the Oracle server is on a completely different machine from SQL Server, so they need to communicate through network traffic. I'm also assuming that the Oracle server is being used by far more people than the Access database is, so it's carrying a higher burden.You should try to use the native OLE DB provider for a data source instead of the ODBC provider; as long as it works properly, the SLOWEST it can go is about as fast as ODBC can run. This is true for Oracle as well as Access, or any other data source, because the ODBC provider has extra overhead that the OLE DB providers do not. |
 |
|
|
|
|
|
OLE DB Linked Servers