We have installed SQL 7.0 Client to connect to the SQL server 7.0. After installing the client (which updated all ODBC drivers) the database connections, even ODBC calls using MS access drivers become extremely slow. Any hints where to look?
View 3 RepliesI 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?
When I create a new odbc connection to a SQL server 2005 Db I get a failure telling me dat de SQL server does not allow remote connections.
How can I allow the server to allow this.
Any help appreciated
regards
Hi!
I have a SQLServer 2005 running om a 64bit cluster. It is used to run a SharePoint 2007 portal. My problem is that the access to the database from the other servers in the farm is very slow.
I made a test program in C# that creates a standard .Net sqlConnection and runs a simple query 100 times. When run on the database server it takes less than a second, but when I run it from the web frontend server it takes 30 seconds. It never fails, it's just slow. The network connection is fast when copying files etc.
I see nothing out of the ordinary in the event log.
Do any of you have an idea what might be the problem or know how I could try to find the problem?
Thanks!
I have a linked tables from access 2003 to sql server 2005 connected using odbc.
the connection is very slow.
when i use the same linked tables to sql server 2000 the connection is fine.
what seems to be the problem???
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 ?
Hi,
I use a Remote Sql Server Express instance, and I have a strange behavior.. The first connection is really slow and I don't know how to fix that.I read some posts about this topic but I didn't find the right solution.Is there a way to "keep alive" the connection between my IIS server and the SQL one ?I check the auto-close property and it sets to false.
Any help ?
Stan
I have had a problem with Enterprise Manager connecting to SQL Server. At first this problem was experienced with one particular network user... whichever PC he logged onto, Enterprise Manager took ages to connect to SQL Server and every operation was painfully slow. Creating a new Windows NT logon fixed the problem.
I now have this same problem but only on my PC. It doesn't matter which Windows NT logon I use, using Enterprise Manager is painfully slow. I've tried creating a new Windows NT profile, checking the hard drive for errors, defragmenting the disk, reinstalling Enterprise Manager etc but nothing works.
What is strange is that connections from VB applications on my PC are fast. It is only Enterprise Manager that is slow.
I am using the latest service pack for SQL Server.
I thought it could be a problem with the Enterprise Manager registry values but don't want to start messing with them!
Has anyone else experienced this problem? Any advice would be great as I can't find any help from microsoft other than installing the latest service pack for SQL Server.
Thanks
Hello,I have a Win2K3 Server with SS2005 developers edition. I am working on aWindows XP Pro workstation which has SQL Server 2000 installed as well asthe SQL Native Client. I'm using an MS Access ADP to connect to the serverand for some reason it's extremely slow, even to the point of throwing timeout errors and "can't generate SSPI context" messages. I've hit the MSwebsite and found info on the SSPI error, but none of the items thatgenerate the error apply to my situation. I've tried using the surface areamanager to change the connection to name pipes, name pipes and tcpip etc,but no luck.Is there anything I should be looking at or any known issues that wouldaffect this kind of performance?Thanks!Rick
View 2 Replies View RelatedHi,I am seeing very slow connections from some client enterprise managersto server. Even at server level it takes 1 minute or less to open adatabase. I have adjusted some of the memory for the SQL server, butthere are only about 60 Dbs on the server, totalling about 2 GBs.CPU is very low at all times, 1 GB of ram, p3 1.4Ghz. SQL 2k.I know I should refrag the disk, but is there anything else I can doto speed up SQL operation via enterprise manager--ODBC connections is fairly fast, as well as query analyzer.Adam
View 2 Replies View RelatedDear All,
When trying to connect to the server outside the firewall through an ODBC connection string, we get the following error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database requested in login '[database name]'. Login fails.
When trying to uncover some more information pertaining to this problem, we get the associated error number, 4060. When researching this number, we see that the number has an associated error severity code of 11. Thus Microsoft is saying that it is a problem that could be corrected at the user level. Ok, I am missing something. I give. Does anyone have a new idea or an approach on which I can begin to uncover new information? We have also checked the database login and the login for the MTSServices is in fact able to access the database through an integrated login with NT Security. Also the Domain Administrator for User Rights does not have the specific NT Group enabled to log onto the computer from the network but the 'Everyone' field is still on the server. If anyone has specific questions, email me directly. Thanks for your help in advance. Daimon
I'm writing a VB app to read and write data to an SQL server database.
I have successfully done so using ADO however I now need to do it using ODBC.
I have set up the appropriate DSN and have no trouble reading data from the database but when I try to write to it I get a message indicating that the database is open for read only access.
I'm no sure whether the restriction is and the VB, ODBC, or database level.
Here's the code which opens the database and recordset.
Set dbsWarehouseServer = OpenDatabase(ODBCDSName, _
dbDriverNoPrompt, False, _
"DSN=" & ODBCDSName)
Set rstRailSet = dbsWarehouseServer.OpenRecordset("Select Store_date, SLN From " & TBName & " where Rail_set_ID = '" & RailID & "'", dbOpenDynaset)
Any help is greatly appreciated.
I use Business Objects XI R2 (BOXI) to report against a SQL Server 2000 database using an ODBC connection.
When I query the database using Enterprise Manager on the server I can make use of all functions available within SQL Server, yet when I access it via the ODBC connection I only get a very small subset of SQL Server functions available.
I can use the inbuilt BOXI functions, which work on the data locally, but would like the functions processed on the server instead.
Is this constraint a property of the ODBC driver, and if so are there other drivers which would expose all of the available SQL Server functions.
Any suggestions appreciated.
I have an application written in VB6 that creates a ADO connection using the (native SQL2005 clien)t from the client to SQLServer 2005 on Server 2003 configured as a stand alone server. The application works great on XP and has for a number of years.
Now I am attempting to deploy in Vista and using the same code the connection speed CRAWLS. it's in the magnitude of atleast 10 times slower. It eventualy works but the selects and doing a readnext against the resulting record set is at a snails pace.
What am I missing. It's has to be some sort of configuration problem somewhere.
I have an application built with Access 2003 (MDB). It is running under Windows XP without any problems. If I run it under Vista, it works technically well but I get the data very slow from the server.
Server:
Windows Server 2003 R2, SP2
SQL Server 2005, version 9.00.3054.00
Firewall: off
Client:
Access 2003, SP3
Connection strings:
ODBC;DRIVER={SQL Native Client};UID=SD_Admin;DATABASE=SDX;SERVER=MARS;PWD=xxx;
or
ODBC;DRIVER={SQL Native Client};DATABASE=SDX;Trusted_Connection=Yes;SERVER=MARS;
Windows Firewall on client: off
Onecare Firewall on client: off
How can i Fix this issue?
Hi,
I am new to the windows world. We use Informatica on UNIX for ETL process. We have a requirement to load approx. 200,000 rows to a MS SQL Server table . The table is not that big and it is a heap table (no indexes). Inserts are taking 69 rows/per minute. We are using DataDirect Closed 4.10 SQL Server ODBC driver.
SQL Profiler tells us that is is doing a row by row processing and using sp_execute procedure.
Is there a way we can speed up the ODBC process?
-Thanks in advance
srv
SQL Server Version:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Hi,
I have a strange problem accessing a MS SQL Database from my network.
I'm using an application that is based on BDE which uses ODBC to connect to a MS SQL DB.
When I tried to connect from the network with BDE,I got this error message:
BDE Error : 13059
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
On the server side I'm using W2003 EE ,MS SQL 2000 Standard with SP4, BDE5.11.
On the client side it's an XP SP2 with MS SQL Client installed, same BDE 5.11
When I create an alias using ODBC and mapping to my server, it connects and the communication with the Database Server succeds:
TESTS COMPLETED SUCCESSFULLY!
When I'm trying to connect using BDE Admin and double clicking on the + sign of the alias I created usind ODBC admin I get the message I listed above.
Any help would be appreciated,
Thanks.
Hi, I have an access 2003 database which connect to sql server via aDSN that goes through a VPN. The database works fine and everyone cancoonect from their normal computers but for anyone working on theirLaptops (IBM Think Pad T42's) they cannnot connect to the datasource.The DSN fails upon connection attempt with :Connection Failed:SQLState: '01000'SQL Server Error: 1326[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()).Connection Failed:SQLState: '08001'SQL Server Error: 17[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not existor access is denied.This has been driving me insane as i cannot understand why it works forour desktop computers and not for our laptops. The version of MDAC isthe same on a computer that connects as it is on a laptop that doesn't.TCP/IP is enabled on the server and is using the default 1433 port.severs, desktops and laptops all patches and up to date with the latestSP's. DSN has been dropped and re-created. Domain user has been put inlocalAdmin group for laptop.I hope i'm mising something really obvious....can someone please pleaseput me out of my misery and tell me they have come accross this beforeand have a solution. Ive tried everything i can think of.CheersDan
View 3 Replies View RelatedCreating a web application. Running a simple query "SELECT username FROM vwCustomer"
vwCustomer is a view built on top of an Access DB which is set up as a linked server. Within SQL Server that view responds immediately. But when I try to access it from an ASP page it takes over 20 seconds to respond.
Used the following to create the linked server:
EXEC sp_addlinkedserver 'DBName', 'Jet 4.0', 'Microsoft.Jet.OLEDB.4.0', 'c:databasesdatabase.mdb'
GO
EXEC sp_addlinkedsrvlogin 'DBName', FALSE, NULL, 'Admin', ''
GO
The view is simply(this works fine in SQL Server):
SELECT * FROM DBName.db.dbo.customer
The ASP page:
SELECT * FROM vwCustomer
Can anyone give me a hint as to where the bottleneck is? Or how I can figure that out using SQL Profiler or something?
Please help!
hello,
im trying to create an ODBC data source from a SQL SERVER 2005 database located in a remoted pc.
Client----------->PC1 : win 2000 sp4, not sql server
Remote server--->PC2 : win 2000 sp4, sql server 2005 express
From the Command Prompt, im typing "ping PC2" successfully.
After, in the ODBC datasource administrator-->System DNS tab, i choose "sql server" as a new data source , and in the server box , i'm typing PC2/SQLEXPRESS.
In the next steps, im typing the user-passwords.
The error :
connection failed
...
[microsoft][odbc sql server driver][named pipes]ConnectionOpen(CreateFile()).
Connection failed:
SQLState: '08001'
..
Client unable to establish connection
What goes wrong?
I follow the same steps locally, and everything is OK.
Sorry for my bad english:cool:
Hi,
I have created a DSN from the ODBC(Windows Control Panel) in Administrative tools.
Is there a way I can connect to that DB from my Microsoft SQL Server Management Studio?
PS:The Provider for this DB does not exist in LinkedServer
Thanks
Hi,I have two, similar SQL Server 7.0 databases (in the same SQL ServerGroup) that I use as the backend for two Access 2000 front endapplications - one is the live version, the other is the developmentversion.The live version works fine. But the other version is read-only, i.e.no changes can be made to the data in the tables, over the ODBCconnection.Both systems have similar ODBC connection properties, the permissionsettings on the SQL Server databases are the same - users, tableaccess, database access, etc. The connections use Windowsauthenication and the users are set up in SQL Server security loginswith public and db_owner selected.Has anyone seen or heard of this problem and does anyone have anyideas on how to fix it?I appreciate any comments or suggestions you may have.Thanks,Chris
View 3 Replies View RelatedHi everybody
I have installed SqlServer 2005 on my server but my Windows application on the client computers should connect to server via ODBC connection
so what should i install on the client computers (that don't have any sql server installed) to enable them to connect?
When i want to create ODBC connection on client computers through (Control panelAdministrative ToolsData Sources) i don't see SQL-Server 2005 ODBC driver in the list ....could anyone help me?
Kind Regards.
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.
View 1 Replies View RelatedI have a Microsoft Access application which uses linked SQL Server tables. I would like to create an ODBC DSN which would be available to all users so that I don't have to create a DSN on each machine. Can this be done? The Access application resides on a shared drive (Windows). Thanks for your help.
Hi all-
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.
Any tips how to get this ODBC working?
Thanks
Ben Prusinski
I just want the simple steps. I think this is linking through get external db? Is it different from SQL Server 2005?
Is this an Access question or a SQL server question.
thanks,
Hi people i am getting a problem when im creating a dsn to sonnect the SQL server as the database for my content server.....................i tried all the tricks given by you people but its still not workin it is showins a message that .............
Connection failed.
SQL State'01000'
[Microsoft][ ODBC SQL Server Driver][Named Pipes]Connection Open
(Connect()).
Connection Failed:
SQL State:'08001'
SQL Server Error:17
[Microsoft ][ODBC SQL Server Driver ][Named Pipes]SQL Server doe not exists or access denied............................
Please any body can help me out with this problem..............?
--------------------------------------------------------------------------------
Chetan
We have a legacy C++ application which uses ODBC to connect to SQL server. The application is a server process that opens a connection and caches it. Unfortunately on a connection drop, it does not refresh the connection. The standard installation is a 3 machine web/app/sql setup.
It has been working fine since last 4-5 years unless the SQL Server goes down. In that case, I keep seeing "Function sequence error" and "Communication link failure" errors. On one particular client installation on application server, I started getting this exception while SQL Server was up and running (on a different machine). I would see the connections randomly dropping in the activity monitor after 3-4 hrs of inactivity.
I wrote a .NET test app which uses ODBC drivers for SQL Server and makes a connection and then just waits. Out of 5 connections established by this application I saw one connection being dropped as well. Another test app used ADO.NET and it did not drop any connections. I asked the IT to check the network and they say its fine.
The servers are W2k3 SP2 and database is SQL Server 2005. IsAutoClose on all the databases is false. Nothing goes in the logs even after turning on traces using DBCC.
Since the connection drop was very random, I turned off connection pooling on "ODBC driver for SQL Server" on the application server and now it is working fine.
Can someone explain me what could be the reason? Also, is there a way to upgrade or downgrade ODBC drivers on W2K3 machines?
Thanks,
Pranav
I have an application that talks to a SQL backend using an ODBC DSN connection. It works fine when running on a 32bit machine but fails in the 64bit environment. The DSN is setup properly on the 64bit box and the Test Connection returns sucess. However when my application tries to use the DSN to connect to the database I recieve the following error.
IM002 - Data source name not found and no default driver specified.
The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.
Any help would be appreciated.
hello there! i have a problem importing data from a remote connection using Sybase ASE ODBC driver(the sybase odbc driver is the only way we can access the database from the remote connection, we've already tried this in crystal reports). in the sql server import export wizard i chose the .net framework data provider for odbc. then below the wizard requires the following info: the connection string, DSN and driver. i specified the correct driver and dsn. in the connection string i specified the user id and the server name but it still produces error. the error says:
the operation could not be completed.
additional information:
ERROR[01000][SYBASE][ODBC Sybase driver][Sybase]ct_connect(): user api layer: internal Client Library error: HAFAILOVER: Trying to connect to server.
ERROR[01000][SYBASE][ODBC Sybase driver][Sybase]ct_connect(): user api layer: internal Client Library error: HAFAILOVER: Trying to connect to server.
i need your help guys... thnx
Our program report the error like this:
[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.
I used VC++ and ADO.
How does this error happen?
How can I fix it?
Does this can be caused by mutil-thread?
We use the SqlServer 2005.
Thanks
Our program report the error like this:
[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.
How does this error happen?
How can I fix it?
We use the SqlServer 2005.
Thanks