I am a real newbie to SQL Server 2000 and databases in general. I am on a WINXP box. I am using an ODBC connection in a perl script. My problem is this. I get this error in my perl script when I try to execute a query against an existing table in my database:
DBD::ODBC::st execute failed: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'wrk_taxonomic_unit'. (SQL-42S02)
[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared. (SQL-42000)(DBD: st_execute/SQLExecute err=-1) at validate.pl line 89.
DBD::ODBC::st fetchrow_array failed: (DBD: no select statement currently executing err=-1) at validate.pl line 90.
The problem seems to be the table name. if I append the owner of the database to the front of the table name, it works. I don't really like this solution. Is there something I can specify in my DSN to avoid this dilemma? Any help is appreciated.
Hi, Just upgraded some development desktops to Vista Business. However we need to still connect to some older remote windows 2000/SQL 2000 servers.
Trying to setup an ODBC system DSN on our Vista Business local desktop we get the following errors -
-START ERROR WINDOW- Connection Failed: SQLState: '01000' SQL Server Error: 772 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (SECDoClientHandshake()0. Connection failed: SQLState: '08001' SQL Server Error: 18 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error -END ERROR WINDOW-
Any help greatly appreciated as this is stopping us from making database/table connections etc. We've checked the firewall setup and all is well there.
PS - we can still connect fine using XP or windows 2000 desktops and their local DSNs.
SQL Server and the service pack seemed to install fine on a Windows 2003 Standard box. I configured the ODBC connection and got a "connection successful". However, when the next application tries to install, i am getting the "data source name not found and no driver specified". My client and db box are the same. Is my client not configured correctly?
Hello, We're upgrading to SQL Server 2000 and need to update all our clients with the latest version of the ODBC and SQL Server Drivers. Can someone tell How do I upgrade the ODBC driver so that they can connected to SQL 2000. The client pc's have an older version of ODBC drivers which supports Sql 7.0 Which dll do I need ? ? Where do I get it? Does it have on sql 2000 cd?
We're upgrading to SQL Server 2000 and need to update all our clients with the latest version of the ODBC and SQL Server Drivers. Can someone tell after updating the ODBC driver to SQL 2000 would it support SQL Server 7.0 ?
I have two servers named Zulu and Zul1 with SQL Server 2000 Standard Edition. I am trying to implement SQL Server 2000 replication. Before do this, I would like checking the connectivity between the two servers by using "ping" and "odbcping" command. With ping command, the result is good (I get the reply from other server).
When I use odbcping, from Zulu to reach Zul1, I get this error:
“ Could not connect to sql server SQLState: 08001 Native Error:17 Info. Message [Microsoft][ODBC SQL Server Drive][DBNETLIB]This Sql server doesn't exist or access is refused SQLState: 01000 Native Error:1326 Info. Message [Microsoft][ODBC SQL Server Drive][DBNETLIB]ConnectionOpen <Connect<>> ”
But when I use odbcping from Zul1 to reach Zulu, I get the good message
Note: * I use the same SQL Server user i.e. sa with the same password in the odbcping command. * Zulu1 is under a firewall, Zulu is on our DMZ zone for public access. * Zulu1 is a Windows NT 4.0, SP 5 and Zulu is a Windows 2000 server.
I have a customer who has a SQL Server 2000 DB and we are needing toget to this DB through ODBC. I had setup a DSN last week thatconnected fine to this DB, and was preparing to build a script tomanage transfers of data to and from one table to another.The then began to have troubles with their DB Backup (this is not atall related to the issue at hand). The problem they claim was that the"sa" was needing to have certain roles applied to it that were not partof it's default properties. My understanding is that the "sa" is theKing of the Kingdom sotospeak, and has all rights, permissions, rolecapabilities, etc...To make a long story short she tried to apply the write and read rolesto the "sa" and it would not allow for this to be applied. She thenapplied a password to the "sa" account (previous it did not have oneand was set to blank) and upon doing this she then removed the passwordand set it back to blank.Since she made these changes we have not been able to connect to her DBvia our DSN. When we get to the point of telling the DSN to use SQLAuthentication, and apply the sa account for use with a blank password- it comes back with an error similar to "database is not available orpassword is incorrect".Has anyone had this problem before, and if so is there any simpleresolve? Something other than the customer having to restore a previousbackup of the DB?Much thanks in advance...
Hello all!I have such question to all of you.I have some tables linked from MS SQL Server 2000. Is time of processingquerybased on these linked tables from MS SQL Server 2000, faster or slower thanthe time of processing the same query based on tables, which are not linkedbutimported to MS Access?Can you answer this question?Thank you in advance for postsMarcin from Poland.
How viable is it to use MS Access as a front end (via ODBC) to a SQL Server2000 database?The users would access via the internet using a netgear vpn setup.Thanks,Paul S
hi all,I am trying to create a dts package to transfer data from tables in mysql server 2000 database to a db2 UDB v8.1.4 database. When I use ibmdb2 oledb driver for the destination this works fine except that rowsare committed on a row by row basis thus performance is slow. I wantto use the odbc driver but when I define it as the destination, i geterrors saying that the maximum number of rows failed has exceeded theminimum.Does anybody know what to do in order to get the transfer workingusing ibm db2 odbc as the datasource?ThanksLyn
I setup a new ODBC connection to MS SQL Server 2000 on Windows XP and keep getting the following errors when I try to either register a new SQL Server 2000 group within Enterprise Manager or test the new ODBC connection:
Current configuration
- MS SQL Server 2000 -Windows XP -ODBC 3.85.1117
Errors:
I. Within SQL Server 2000 Enterprise Manager
Error: SQL Server connection open
II. When I test the ODBC connection:
Microsoft SQL Server ODBC Driver Version 03.85.1117
Running connectivity tests...
Attempting connection [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.
TESTS FAILED!
Now here is what has me totally confused:
I can use the command line ISQL to access the database on the server and IP is all correct and port is available.
Here's my situation:I have an ODBC DSN setup for Timberline Data (An accounting packagethat uses pervasive.sql) on my sql box. I set up a linked server usingthe supplied timberline odbc driver. I have two sql instances setup,the default instance and a named instance. On the default instance,the linked server works great no matter who is logged in using it (allauthentication is NT integrated). However on the named instance onlythe NT account that the MSSqlserver$NAMED service is logged in undercan utilize the linked server. All others get a ODBC error:"error 7399: OLE DB Provider 'MSDASQL' reported an error. AccessDenied. OLE DB error trace [OLE/DB Provider 'MSDASQL'IUnknown::QueryInterface returned 0x80070005: Access Denied.]."Far as i can tell, both instances are setup the same, except that oneis the default and one is a named instance.Why the different results for the default instance vs a named instance.Any ideas?Thanks
I changed from Access97 to AccessXP and I have immense performanceproblems.Details:- Access XP MDB with Jet 4.0 ( no ADP-Project )- Linked Tables to SQL-Server 2000 over ODBCI used the SQL Profile to watch the T-SQL-Command which Access ( whocreates the commands?) creates and noticed:1) some Jet-SQL commands with JOINS and Where-Statements aretranslated very well, using sp_prepexe and sp_execute, including thesimilar SQL-Statement as in JET.2) other Jet-SQL commands with JOINS and Where-Statements aretranslated very bad, because the Join wasn´t sent as a join, Accesscollects the data of the individual tables seperately.Access sends much to much data over the network, it is a disaster!3) in Access97 the same command was interpreted wellCould it be possible the Access uses a wrong protocol-stack, perhapsJet to OLEDB, OLEDB to ODBC, ODBC to SQL-Server orJet to ODBC, ODBC to OLEDB and OLEDB to SQL-Server instead ofJet to ODBC and ODBC direct to SQL-ServerDoes anyone knows anything about:- Command-Interpreter of JetODBC, Parameters, how to influence thecommand-interpreter- Protocol-Stack of a Jet4.0 / ODBC / SQL-Server applicationThanks , Andreas
I am getting the error message as "DIAG [00000] [ODBC Access Driver 52.1.150.0] -26 Driver not capable (-26)" at the time of retrieving the catalog infromation by SqlTables methode. it is shown "?" as catalogname but this not supported by odbc access driver. can you please help out how can i resolve using C++ code in SqlTables methode.
I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.
I am running Windows XP Pro SP2. I have installed the SQL Native Client for XP. However, when I try to add a new data source through ODBC Connection Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the SQL Native Client to not show up in the list of available ODBC data sources?
I would like to seperate the data between years 2005 and 2006 from SQL 2000 database.And i also want to access those seperate data from the client pc through ODBC.Is it possible.
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application. --------------------------------------------------------------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I normally use Microsoft Access to retrieve data , via ODBC connection, from a table in a SQLserver database. One of the fields in the table has a value 1 but at times when the data is retrieved into MS Access it turns out to be 100 in Access. Moreover, when I try to change it in Access my computer hangs or it takes a long time before the change is effected. It does not matter from which client Pc this action takes place it remains the same. I am using ODBC SQLserver ODBC driver version 2000.81.9042.00.
I would be grateful if you could help me out of this strange situation.
Hi, I wonder if anyone can shed some light on this issue -
We have a client/server program for MSSQL7 and MSSQL2000. When running client/server - we have our own broker, etc, the program ends up locking itself on SQL2000; this is not a problem on SQL7. We noticed that it seems some system tables locking tempdb. We also noticed that SQL2000 no longer has insert-into/bulkcopy option like SQL7. But, here we don't have temporary tables at all. It's just that we found the lockings in tempdb caused by some sysobjects, sysindexes, etc. Also, this does not happen to all the systems we have. Some of our machine does not have the self-lock problem; most of the machines have this problem though.
If we don't run client/server, then the program works fine. Same logic, the difference is when we use client/server logic to connect to the remote SQLServer 2000 server, the locking might happen on most of our machines.
Anyone is familiar with tempdb and locking issues, please provide some hint??? Is it possible that there are some system parameters that we can set to avoid the problem. We haven't found out why some of our machines do not have problem, while most of the machines have this locking problem.
i have msde 2000 running on a server i am able to create an odbc connection to my db on that pc. when i try to create anpther odbc connection on another pc on that network i get the following error:
sql state '01000' server error 2 [microsoft][odbc sql server driver][named pipes] connectionopen (connect()). connection failed sql state '08001' server error 17 [microsoft][odbc sql server driver][named pipes]server does not exist or access denied.
what do i have to do to get this odbc connection on this pc working?
I'm having trouble using Informix 2000 database as a source. I have an OpenLink v 5.2 driver installed and a System DSN set up. I can successfully test the connection.
I added the ADO.Net DSN to the connection manager and added it to a DataReader Source. I then added the SQLCommand property. I was able to map columns (took a long time for the columns to show up) and then I get an error: "Function sequence error:". Can not save the DataReader.
Please help share with me if you know the version compatibility matrix of Ms SQL Server, ODBC driver (sqlsrv32.dll), Driver Manager (odbc32.dll) and ODBC API spec. For instance, how can I know Ms SQL Server 2000 can work with which version of sqlsrv32.dll, a particular version of sqlsrv32.dll can work with which version of odbc32.dll and a certain version of sqlsrv32.dll/odbc32.dll conforms to which version of ODBC API spec (e.g. 3.5).
I am trying to use a DTS package to extract data from an old Pervasive SQL 2000 (Btrieve) data source, and copy into an MS SQL Server table.
I have installed the Pervasive ODBC driver and got linked tables in Access working. I can see the data.
When I create the DTS package, it shows a list of the tables in the drop-down, but when I hit the Preview button I get an unspecified error. I can finish setting up the DTS package, the new MS SQL Sever table gets created, and the field transformations all look correct. However, when I execute the package it fails. In the logs, I get an unspecified error, the only error code I get in log is: 80074005.
I am using SSIS 2014 with the below .net framework version and installed in Windows server 2012 R2 . I have installed my client's odbc drivers (both 32 bit and 64 bit) in my production server and created ODBC system DSNs for 32 bit and 64 bit.
When i open SSIS 2014 and tried to create the odbc connection but i can able to see only the 32 bit system DSN connection ,i can't able to see my 64 bit odbc system dsn connection.
Microsoft Visual Studio 2012 Shell (Integrated) Version 11.0.50727.1 RTMREL Microsoft .NET Framework Version 4.5.51650
SQL Server Integration Services   Microsoft SQL Server Integration Services Designer Version 12.0.1524.0
And i installed my client odbc drivers(32,64 bit) and created ODBC system DSNs in my local system and when i open ssis 2014 and i can able to see both the ODBC system DSNS(32,64) connections from SSIS ODBC connection.
I am using below version of .net framework in my local system which was installed in windows 7 and i have SSIS 2012 also installed in my system and i can able to see both ODBC connections using 2012 as well in my local system.
Microsoft Visual Studio 2012 Shell (Integrated) Version 11.0.50727.1 RTMREL Microsoft .NET Framework Version 4.5.50938
SQL Server Integration Services   Microsoft SQL Server Integration Services Designer Version 12.0.1524.0
why i can not see the ODBC 64 bit system DSN connection from SSIS in my production server ?
I am using VB.NET 2005 and set up an ODBC connection via ODBC.ODBCConnection to a MDB database. Therefor, I use the "Microsoft Access ODBC Driver (*.mdb)".
When I set up a ODBCCommand like "ALTER DATABASE..." or "CREATE TABLE..." and issue it with the com.ExecuteNonQuery() command, I get an error from ODBC driver, that a SQL statement has to begin with SELECT, INSERT, UPDATE or DELETE.
How can I use DDL statements via ODBC?
I would appreciate if you could help me to use ODBC for that - no OLE, no ADO.
I am getteing need help Query analyzer error Unable to connect server local Msg17, level 16,state 1 ODBC SQL server driver [DBNETLIB]SQL server does not exist
Hi all,I am having trouble getting linked Oracle 9 server in MS SQL Server2005 Express to work properly. My machine is running Windows XP.The Microsoft and Oracle OLE DB Providers have problems dealing withOracle's Numeric Data Type, so I decided to use Microsoft's OLE DB forODBC Provider and an Oracle ODBC source. When using the Microsoft ODBCfor Oracle Driver in my ODBC source I have inconsistent behavior.Sometimes my queries are processed properly, then other times I get thefollowing errorOLE DB provider "MSDASQL" for linked server "ODBCBEAST" returnedmessage "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttrfailed".OLE DB provider "MSDASQL" for linked server "ODBCBEAST" returnedmessage "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttrfailed".OLE DB provider "MSDASQL" for linked server "ODBCBEAST" returnedmessage "[Microsoft][ODBC driver for Oracle][Oracle]".Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "MSDASQL"for linked server "ODBCBEAST".I have no idea why sometimes I can connect to the linked server with noproblems andwhy other times it performs like this. I'm not changing anything aboutthe system I can think of. When I use an Oracle client (PL/SQL) I haveabsolutely no problems connecting. TNSPING returns that the connectionis good.This is unacceptable so I decided to try my luck with the Oracle 10gODBC driver. However when I use this and perform an openquery selectagainst the linked server I get back only 11 rows, when I know that thedatabase has over 100 rows (in fact when using the Microsoft ODBCdriver and it works that's what I get). I figured maybe the buffersetting needed to be raised in the ODBC configuration so I took it from64000 to 600000 (a magnitude of 10) but I still get back only 11 rows.I'm at my wit's end.Any suggestions on resolving one or the other problem would be muchappreciated.Thanks much
Dear all,On Win2000 server with SP3, I am trying to access a SQL Server 7.0database, "TestDB", from VB6 via a SQL Server ODBC system DSN using ADO2.7. In SQL Server Enterprise Manager, there is a login named "Tester".In its property window, NO "Server Roles" was assigned but its"Database Access" was set to "TestDB". This login was also made as theuser of "TestDB" with "public", "db_datareader" and "db_datawriter"selected as its "Database role membership". All the tables I am tryingto access in "TestDB" were created under "Tester".My code is like:Set conn = New ADODB.Connectionconn.Open "DSN=TestDSN;UID=Tester;PWD=test"Set cmd = New ADODB.Commandcmd.ActiveConnection = conncmd.CommandText = SQLset rs = cmd.Execute()If I set the SQL to something like "SELECT * FROM tbl_test", I alwaysget an error of "-2147217865" saying "[Microsoft][ODBC SQL ServerDriver][SQL Server] Invalid object name tbl_test". If I set the SQL to"SELECT * FROM Tester.tbl_test", everything runs properly. Could anyoneplease kindly advise why the first SQL is not working? Or in otherwords, why must I prefix the table name with its owner while the DBconnection is already made under that owner name? Thanks in advance.Tracy
