Hi all
I'm attempting to setup a linked server to a cache database within
Enterprise Manager. I setup an ODBC driver on the server and the
connection worked when tested.
Selected Micorsoft OLE DB Provider for ODBC Driver from the drop down
list.
Entered the data source name in the Data Source field and I keep
getting "error 7399: OLE DB provider 'MSDASQL' reported an error. OLE
DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize
returned 0x800004005;]"
Does the ODBC driver need to be installed on the same drive as SQL?
The driver is a system DNS stored on C: while SQL is installed on
another drive.
Or am I missing some parameters in the setup?
Thanks
mike
Got it to work.
Had to set everything up on the server and not on my machine.
Showing posts with label cache. Show all posts
Showing posts with label cache. Show all posts
Friday, March 23, 2012
ODBC Connection Problem
ODBC Connection Problem
Hi all
I'm attempting to setup a linked server to a cache database within
Enterprise Manager. I setup an ODBC driver on the server and the
connection worked when tested.
Selected Micorsoft OLE DB Provider for ODBC Driver from the drop down
list.
Entered the data source name in the Data Source field and I keep
getting "error 7399: OLE DB provider 'MSDASQL' reported an error. OLE
DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize
returned 0x800004005;]"
Does the ODBC driver need to be installed on the same drive as SQL?
The driver is a system DNS stored on C: while SQL is installed on
another drive.
Or am I missing some parameters in the setup?
Thanks
mikeGot it to work.
Had to set everything up on the server and not on my machine.
I'm attempting to setup a linked server to a cache database within
Enterprise Manager. I setup an ODBC driver on the server and the
connection worked when tested.
Selected Micorsoft OLE DB Provider for ODBC Driver from the drop down
list.
Entered the data source name in the Data Source field and I keep
getting "error 7399: OLE DB provider 'MSDASQL' reported an error. OLE
DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize
returned 0x800004005;]"
Does the ODBC driver need to be installed on the same drive as SQL?
The driver is a system DNS stored on C: while SQL is installed on
another drive.
Or am I missing some parameters in the setup?
Thanks
mikeGot it to work.
Had to set everything up on the server and not on my machine.
Monday, February 20, 2012
Objects in Procedure or Data Cache
I am having some performance issues on my server and wish to track down the particular objects responsible.
Is there any way of determining which objects are in memory?
Many thanks.
Dontable "syscacheobjects" in master database, for cache usage.
setting up a trace in SQL Profiler is also useful
des|||Thanks Des,
It provides some of what I am looking for. I don't seem to find objects of type 'user table' being generated. My SQL Server reports to be using something like 1.4 GB memory from Sysmon. I was hoping that syscacheobjects will shed like on the objects in memory. However, I will continue with the profiler.
Many thanks once more.
Don
Originally posted by DesmondX
table "syscacheobjects" in master database, for cache usage.
setting up a trace in SQL Profiler is also useful
des|||an easy way to keep unnecessary stuff out of memory is to run a scheduled "checkpoint" command on each database every few hours, to flush the memory to disk...
good luck sorting it out...
des
Is there any way of determining which objects are in memory?
Many thanks.
Dontable "syscacheobjects" in master database, for cache usage.
setting up a trace in SQL Profiler is also useful
des|||Thanks Des,
It provides some of what I am looking for. I don't seem to find objects of type 'user table' being generated. My SQL Server reports to be using something like 1.4 GB memory from Sysmon. I was hoping that syscacheobjects will shed like on the objects in memory. However, I will continue with the profiler.
Many thanks once more.
Don
Originally posted by DesmondX
table "syscacheobjects" in master database, for cache usage.
setting up a trace in SQL Profiler is also useful
des|||an easy way to keep unnecessary stuff out of memory is to run a scheduled "checkpoint" command on each database every few hours, to flush the memory to disk...
good luck sorting it out...
des
Labels:
cache,
database,
determining,
microsoft,
mysql,
objects,
oracle,
particular,
performance,
procedure,
responsible,
server,
sql,
track
Subscribe to:
Posts (Atom)