Odd SQL Server behavior

Hello everyone,
It seems like I've got a runaway SQL Server process.
Almost without fail, when I'm connected to the Internet
via my cable-modem, the SQL Server process starts to
consume 97-100% of the CPU resources on my machine after
about 45 minutes to 1 hour from the time the process is
started. Not only does it consume almost all my CPU's
power, but the number of packets sent out through the
Ethernet cable grows exponentially to gigantic proportions:
prior to SQL Server going nuts, I see the number of
packages SENT and RECEIVED in the order of a few thousand,
but afterwards the number of SENT packages skyrockets to
several MILLION, and keeps going and going.
When this happens, I cannot stop the SQL Server service,
nor can I kill the process. Only solution I have found up
until now is to reboot.
Any ideas? Could this be some sort of a SQL Server virus?
About my system:
Compaq Evo N600c
Tons of free space; 768MB RAM
Windows 2000 Server SP3
SQL Server 2000 SP3
Please send replies to:
jgiosone AT sofwerks.comThis is symptomatic of the Slammer worm but you are not vulnerable if you
have SP3 installed. You might double-check that SP3 is actually installed
with the following:
SELECT SERVERPROPERTY('ProductLevel')
Also, check to see if you have other unpatched instances on your machine.
See <http://www.microsoft.com/sql/downloads/securitytools.asp> for
information on the SQL Critical Update tool.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Jose P. Gisone" <jgisone@.sofwerks.com> wrote in message
news:448d01c3e45b$38ee6410$a301280a@.phx.gbl...
> Hello everyone,
> It seems like I've got a runaway SQL Server process.
> Almost without fail, when I'm connected to the Internet
> via my cable-modem, the SQL Server process starts to
> consume 97-100% of the CPU resources on my machine after
> about 45 minutes to 1 hour from the time the process is
> started. Not only does it consume almost all my CPU's
> power, but the number of packets sent out through the
> Ethernet cable grows exponentially to gigantic proportions:
> prior to SQL Server going nuts, I see the number of
> packages SENT and RECEIVED in the order of a few thousand,
> but afterwards the number of SENT packages skyrockets to
> several MILLION, and keeps going and going.
> When this happens, I cannot stop the SQL Server service,
> nor can I kill the process. Only solution I have found up
> until now is to reboot.
> Any ideas? Could this be some sort of a SQL Server virus?
> About my system:
> Compaq Evo N600c
> Tons of free space; 768MB RAM
> Windows 2000 Server SP3
> SQL Server 2000 SP3
>
> Please send replies to:
> jgiosone AT sofwerks.com

odbc over internet

We are running an sql server database on a Windows 2000 server, aproximately
15 clients on our lan use odbc connections to connect with acces 2002 front
end. No problem. Then i came up with the idea to connect a home-worker via
internet, using a vpn tunnel over isdn. Somehow this vpn-over-isdn
connection is unstable, as a matter of fact only few records can be entered
before the connection is lost. Is this a limitation of odbc connections or
just a miserable isdn solution wich need to be replaced?"b.binnenweg" <bobby01@.nospamxs4all.nl> wrote in message
news:402e0d12$0$557$e4fe514c@.news.xs4all.nl...
> We are running an sql server database on a Windows 2000 server,
aproximately
> 15 clients on our lan use odbc connections to connect with acces 2002
front
> end. No problem. Then i came up with the idea to connect a home-worker via
> internet, using a vpn tunnel over isdn. Somehow this vpn-over-isdn
> connection is unstable, as a matter of fact only few records can be
entered
> before the connection is lost. Is this a limitation of odbc connections or
> just a miserable isdn solution wich need to be replaced?
>
That sounds like a connection issue... are you experiencing high latency
from the client to the server? Also, linked Access tables are not that
efficient and not recommended for WAN access.
Steve

ODBC link across a vpn / WAN / internet link

Is it possible to achieve an ODBC link from a client pc to a remote SQL
server, either over a VPN / WAN or internet connection?
I'm looking to link a access front end to a SQL server, using a hosted
remote server.
TIAYes, it's possible and easy. However, the port 1433 (of the other one if
you set up the SQL-Server to listen to another port) must be open through
all firewalls; something that is easy to do on your side but less likely if
you are using an hosted server. For security purposes, most commercial web
hosting services will refuse to open the port 1433 through their firewall in
order to protect their sql-servers.
For OLEDB, make sure that you specify the TCP/IP protocol by indicating the
Network Library:
Provider=sqloledb;Data Source=190.190.200.100,1433;Network
Library=DBMSSOCN;Initial Catalog=myDataBase;User
ID=myUsername;Password=myPassword;
See: http://www.connectionstrings.com/?carrier=sqlserver or
http://www.carlprothman.net/Technology/ConnectionStrings/ODBCDSNLess/tabid/90/Default.aspx
For further explanations, take a look at the m.p.access.odbcclientsvr,
m.p.a.internet or m.p.a.externaldata newsgroups.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Fred" <fred@.blah.com> wrote in message
news:e7HoX4UQHHA.1364@.TK2MSFTNGP06.phx.gbl...
> Is it possible to achieve an ODBC link from a client pc to a remote SQL
> server, either over a VPN / WAN or internet connection?
> I'm looking to link a access front end to a SQL server, using a hosted
> remote server.
> TIA
>
>

ODBC link across a vpn / WAN / internet link

Is it possible to achieve an ODBC link from a client pc to a remote SQL
server, either over a VPN / WAN or internet connection?
I'm looking to link a access front end to a SQL server, using a hosted
remote server.
TIA
Yes, it's possible and easy. However, the port 1433 (of the other one if
you set up the SQL-Server to listen to another port) must be open through
all firewalls; something that is easy to do on your side but less likely if
you are using an hosted server. For security purposes, most commercial web
hosting services will refuse to open the port 1433 through their firewall in
order to protect their sql-servers.
For OLEDB, make sure that you specify the TCP/IP protocol by indicating the
Network Library:
Provider=sqloledb;Data Source=190.190.200.100,1433;Network
Library=DBMSSOCN;Initial Catalog=myDataBase;User
ID=myUsername;Password=myPassword;
See: http://www.connectionstrings.com/?carrier=sqlserver or
http://www.carlprothman.net/Technology/ConnectionStrings/ODBCDSNLess/tabid/90/Default.aspx
For further explanations, take a look at the m.p.access.odbcclientsvr,
m.p.a.internet or m.p.a.externaldata newsgroups.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Fred" <fred@.blah.com> wrote in message
news:e7HoX4UQHHA.1364@.TK2MSFTNGP06.phx.gbl...
> Is it possible to achieve an ODBC link from a client pc to a remote SQL
> server, either over a VPN / WAN or internet connection?
> I'm looking to link a access front end to a SQL server, using a hosted
> remote server.
> TIA
>
>

ODBC link across a vpn / WAN / internet link

Is it possible to achieve an ODBC link from a client pc to a remote SQL
server, either over a VPN / WAN or internet connection?
I'm looking to link a access front end to a SQL server, using a hosted
remote server.
TIAYes, it's possible and easy. However, the port 1433 (of the other one if
you set up the SQL-Server to listen to another port) must be open through
all firewalls; something that is easy to do on your side but less likely if
you are using an hosted server. For security purposes, most commercial web
hosting services will refuse to open the port 1433 through their firewall in
order to protect their sql-servers.
For OLEDB, make sure that you specify the TCP/IP protocol by indicating the
Network Library:
Provider=sqloledb;Data Source=190.190.200.100,1433;Network
Library=DBMSSOCN;Initial Catalog=myDataBase;User
ID=myUsername;Password=myPassword;
See: http://www.connectionstrings.com/?carrier=sqlserver or
http://www.carlprothman.net/Technol...br />
ult.aspx
For further explanations, take a look at the m.p.access.odbcclientsvr,
m.p.a.internet or m.p.a.externaldata newsgroups.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Fred" <fred@.blah.com> wrote in message
news:e7HoX4UQHHA.1364@.TK2MSFTNGP06.phx.gbl...
> Is it possible to achieve an ODBC link from a client pc to a remote SQL
> server, either over a VPN / WAN or internet connection?
> I'm looking to link a access front end to a SQL server, using a hosted
> remote server.
> TIA
>
>