The service side is no problem, use Microsoft SQL Server Management Studio can be connected, can also be connected in python,
Linux using Centos, ubuntu,
Program is someone else has written, can't change the Delphi source code, can only be used to find a way to set,
Please help me give an idea
Thank you very much ~
CodePudding user response:
Delphi 7 should be using ADO or ODBC connection, the client connection MSSQL is need have MSSQL drive to,So, you can try the can in the ODBC to connect to your data services (on your computer run Delphi process),
Also, you can check the network connection and the server's network configuration,
CodePudding user response:
See if we can ping ping server IP,This is actually the look and the remote SQL server 2000 server physical connection exists, if not, please check the network, check the configuration, of course, make sure the remote SQL server 2000 server IP correctly spelled,
2 under Dos or command line input Telnet server IP port, see whether connected,
Such as Telnet 202.114.100.100 1433
Usually port value is 1433, because 1433 is SQL server 2000 for Tcp/IP default listener ports, if there is a problem, often cause problems in this step, the message usually is "... Unable to open the connection, the connection fails, "
If you have a problem in this step, you should check the following options,
1 check the remote server whether to start the SQL server 2000 service, if not, then start,
2 check the server side has not enabled Tcp/IP protocol, because of the remote connection (via Internet) need to rely on the agreement, inspection method is to open on the server start menu - & gt; Program - & gt; Microsoft SQL Server - & gt; Server network utility, see enabled if there is a TCP/IP protocol in the agreement, if not, enable it,
3 check the TCP/IP port server configured for port 1433, still in the server network utility view enabled protocol in TCP/IP properties, make sure that the default port is 1433, and hide the server check box without hook,
In fact, if the default port has been changed, and may be used, but the client do a Telnet test, write server port number must be consistent with the server configuration of port, if the hidden server check box is checked, means that the client to see this server through enumeration server, play a protective role, but does not affect the connection, but the default port of Tcp/IP protocol will be implicit changed to 2433, when the client connection must be made corresponding change,
4 if the server operating system called sp2 patch, is a certain configuration, the Windows firewall to open port 1433, it often can directly turn off the Windows firewall when testing (also turn off the best other firewall),
5 check the server is listening on port 1433, if the server is not in a TCP connection port 1433 to listen to, is connected, not check method is in the server's DOS or command line input below
Netstat -a - n or netstat - an, in result list to see if there are similar to TCP 127.0.0.1 1433 listening, if not, often need to SQL server 2000 sp3 patch, at least in the server startup query analyzer, the select input @ @ upon implementation of version can see the version number, version number under 8.0.2039 require patching,
If above all no problem, then you do a Telnet server IP 1433 test, you will see the screen flash after the cursor in the upper left corner kept flashing, congratulations you, you can start immediately in the enterprise manager or query analyzer connected,
3 check the client Settings
Program - & gt; Microsoft SQL Server - & gt; Client network use tools, like in the server network utility, make sure that the client TCP/IP protocol is enabled, and the default port is 1433 (or other port, consistent with the server side),
Four in the enterprise manager or query analyzer connection test
Enterprise manager - & gt; Right click - essentially a group & gt; Essentially a new registration - & gt; The next step - & gt; Write the remote IP - & gt; The next step - & gt; Choose essentially landing - & gt; The next step - & gt; Write the login name and password (sa, password) - & gt; The next step - & gt; The next step - & gt; Complete the
Query analyzer - & gt; File - & gt; Connection - & gt; Write the remote IP - & gt; Write the login name and password (sa, password) - & gt; Sure
Usually do suggest in the query analyzer, because by default, through the enterprise manager to register another one SQL Server timeout is 4 seconds, and query analyzer is 15 seconds,
The method of change the default connection timeout:
Enterprise manager - & gt; Tools - & gt; Options - & gt; In the "SQL Server enterprise manager properties" window, click the "advanced" TAB - & gt; Connection Settings - & gt; The box behind the login timeout (in seconds) enter a larger number
Query analyzer - & gt; Tools - & gt; Options - & gt; Connection - & gt; The box behind the login timeout (in seconds) enter a larger number
Usually can be connected, if prompt error, is to enter the next step,
Five errors are usually caused by SQL Server using the "Windows" only way of authentication, so users can't use SQL Server login account (sa) to connect, the solution is as follows:
1 on the Server side using the enterprise manager, and select "use Windows authentication" SQL Server connection,
2 "SQL Server group", the right mouse button click on the name of the SQL Server Server, select "properties", then select "security" TAB,
3 under the "authentication", select "SQL Server and Windows,"
Restart the SQL Server service, 4 (net under DOS or command line stop mssqlserver stop service, net start mssqlserver start the service, is also a kind of efficient method),
Note: the connection to the local server, usually use a named pipe agreement (in the server network utility can see enable agreement has this), the default port is 445, so what can locally connected is not problem, is a completely different protocol to connect to a remote server,