Re: sql server traffic shut down internet

There's no SQL Server 03. There's 2000 and 2005. If you are on 2000, you might have been hit by the slammer virus which could expose such behavior. Make sure you then are on at least sp3a.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"seeker" <seeker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:77CE2F33-C849-483A-98A0-54421E8B11A7@xxxxxxxxxxxxxxxx
we are running sql server 03 on win server 03 enterprise. when i took the
sql server offline everything went back to "normal". Thus the reason I am
thinking that it is the sql server that has the problem. This was a install
without tweeks so could some configuration of sql need to come into play?
How do i look at profiler? Thanks for all of your input.

"Aaron Bertrand [SQL Server MVP]" wrote:

While it is possible that you could write code that would bring your network
to a halt, I think that is unlikely. What version of SQL Server are you
using? If you shut the SQL Server service down, does everything return to
normal? I am guessing it is much more likely that you have an outage for a
very specific reason, that it has absolutely nothing at all to do with SQL
Server, and this is just a timing coincidence.

Do you have IT people on staff who look after the network?





On 5/20/09 4:01 PM, in article
BEA3DB30-EE0C-40EF-AE9C-19D5C3994804@xxxxxxxxxxxxx, "seeker"
<seeker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> I have place tables on my newly installed sql server and put it > live to our
> user base. Once all users were inputing data, looking at data > etc. our
> internet traffic degraded to total shut down. What is not > configured right?
> sql server? the winserver 03 os that it sits on? the routers? I > do not know
> where to even start to troubleshoot this one.
>
>



.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • It can be Done
    ... I just installed a 3 SQL Server 2005 instances on a 2 node Active/Passive cluster. ... IWiz will then offer you a choice of Group on where you can install teh Fail Over Clustered Instance of SQL. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)