sql server traffic shut down internet

You need to start at the top.

Did anything else change in the deployment or was it just your new tables
and the code to access them? Are you sure the problem is directly related to
your new changes?

Was the code to access the new tables strictly T-Sql or was there
application coding as well? (Java etc.) . Has the code been reviewed?

Do you have the same problems in your development / testing environments? If
not, what’s different?

Have you tried Profiler to see what SQL Server is doing? Is it causing
deadlocks? Are the tables properly indexed? How big are these tables? Have
you looked at query execution plans?

Tracing down performance issues is an art but you always want to eliminate
what is NOT causing the problems. You give very few details, so the
responses are going to be very general in nature.

Good luck with your issue!


"seeker" 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.
>
>

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-19D5C3994804atmicrosoftdotcom, "seeker"
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.
>
>

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-19D5C3994804atmicrosoftdotcom, "seeker"
> 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.
> >
> >
>
>

> How do i look at profiler?

I don't think I would be able to give you an accurate step by step from
scratch in a newsgroup post. Maybe start with these topics at MSDN:

http://msdn.microsoft.com/en-us/library/ms187929.aspx

http://msdn.microsoft.com/en-us/library/ms979207.aspx

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" wrote in message
news:77CE2F33-C849-483A-98A0-54421E8B11A7atmicrosoftdotcom...
> 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-19D5C3994804atmicrosoftdotcom, "seeker"
>> 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.
>> >
>> >
>>
>>