Our clients wnat us to retreive data from SQL Server 2000. It is unknown whether they have any service packs installed for that SQL Server. Assuming the worst (no sp), will there be a problem using OleDb driver to work with SQL Server 2000?
OleDb is working fine without any sp.
Related
i have 2 server.
one using Oracle database and other using SQL Server 2008.
how i can link that server?
can anyone give me solution?
How can I transfer a SQL Server Compact database to SQL Server 2008 by using
a SQL Server 2008 procedure?
Yes, you can create a SQLCLR procedure using the SQL Server Compact OLEDB provider. I have some sample code here: http://erikej.blogspot.dk/2008/10/accessing-sql-compact-from-sql-server.html
If you want to do a one off transfer from SQL Server Compact to SQL Server 2008, you can use my ExportSqlCe command line to in combination with sqlcmd to transfer the entire database
I have a dev workstation with sql 2005 installed and in it I created a linked server to a odbc connection to a clarion database. I can run select statements against it inside sql Mgt studio. When I take a second workstation and connect to the sql on the first box using sql mgt studio, then try the exact same query I get
OLE DB provider "MSDASQL" for linked server "liveclarion" returned message "[SoftVelocity Inc.][TopSpeed ODBC Driver][ISAM]ISAM Table Not Found".
Any thoughts? It appears to have the same functionality on a second sql server. No remote sql mgt studio connect success in queries against my linked ODBC clarion DB.
All done with windows authentication and the same AD user.
The error returned by the ODBC driver is "SAM table not found".
So I'm assuming you have a table called SAM - presumably in a table called Sam.Tps?
I'm wondering if you need to set a path to that file - ie if there's some difference in path or file name validity between your two tests. One assumes not, but I'd look in that direction first.
Is there a way to get SQL Server 2005 to query 3 or more separate Access databases (each returning 1 record) in one SQL statement?
Yes, but it will require you to create a Linked Server instance for each Access database. See here for details about creating Linked Server instances on SQL Server 2005 to MS Access.
Once you have those in place, you can query SQL Server and it will pass on the queries to the respective Access databases based on using the Linked Server instance notation when specifying tables in your SQL Server queries.
What you want is a Linked Server for each of the Access databases.
Just be aware that in SQL 2005 64-bit you won't be querying current versions of Access or Excel through linked servers any time soon.
Yes, set them up as linked servers using sp_addlinkedserver.
Between SQL 2000 and 2005 MS changed the syntax to connect to a local database from (local) to .\instanceName.
I have a client who has been using (local)\instanceName to connect to local SQL Server 2005 databases. Usually it works fine, but sometimes it doesn't and he has been using PCname\instanceName.
Why does this sometimes fail?
You can define alias for your instance in sql server configuration manager. You can define multiple aliases for same instace, so both (loacl) and instanceName will work.