MSSQL2--Going Nuts Now!

[Kpatel]

Today itself, MSSQl2 was went down or whatever but 50% of the time my application came up with an error either one of this

1) SQL Server Does not Exists Access Deined (Mostly this error, funny part is I am connected to SQL Server from EM all the time when the error shows up)

2) Connection Timedout

I don't want to even talk about speed

Sometimes the speed is GREAT (only 20% of time)
and most of the time it is horrible (I don't know other words to describe it!!!)

Is support reading this, I need help...any one else running a good size database application in ASP.NET and SQL Server here

[soky]

Originally posted by Kpatel
Today itself, MSSQl2 was went down or whatever but 50% of the time my application came up with an error either one of this

1) SQL Server Does not Exists Access Deined (Mostly this error, funny part is I am connected to SQL Server from EM all the time when the error shows up)

2) Connection Timedout

I don't want to even talk about speed

Sometimes the speed is GREAT (only 20% of time)
and most of the time it is horrible (I don't know other words to describe it!!!)

Is support reading this, I need help...any one else running a good size database application in ASP.NET and SQL Server here

This is concerning! I am about to move 15,000 product records to matrix sql... uhm... anyone there at Matrix wanna help me feel warm and fuzzy? p p please?

[Kpatel]

Good luck buddy,

[jmbeach]

frankly, I've been a bit hesitant upsizing any of my Access db's to SQL for all the negative thoughts on these MSSQL servers.

[soky]

Originally posted by jmbeach
frankly, I've been a bit hesitant upsizing any of my Access db's to SQL for all the negative thoughts on these MSSQL servers.

One would think Matrix would come pet us and make us feel better.

----

I wonder what they are doing to resolve the issues? I wonder what assurances they will offer? I have gone ahead and created my first SQL DB and will do some load testing.

If the original poster's issues are all related exclusively to the Enterprise Manager... then I'm okay. Not so happy... but okay.

[xweb]

mssql1 is no better.

[Alessandro]

Threads about MSSQL servers performance are increasing.
Probably this is a quite common thought between MSSQL users, but I hope one of the next new servers will be for MSSQL.

In my (not so long...) experience, usually Matrix tries to satisfy their customers as best as they can when an issue starts to spread, I believe also this will be the case.

BTW, I'm not having much problems with my MSSQL dbs (just one not worth a TT, if it doesn't repeat again). The only problem is a long wait when connecting with EM, but it seems no cure is available.

[Vixen]

Originally posted by soky
One would think Matrix would come pet us and make us feel better.

----

I wonder what they are doing to resolve the issues? I wonder what assurances they will offer?

I am sorry guys but I do my best on the weekends to keep Admin off the board since he works 12 hours a day, 5 days a week which is down from 12 hours a day, 7 days a week (for the past 2 1/2 years). He pops in here from time to time on Saturday and Sunday, as you can see from viewing some of his posts. I can tell you that he has been looking into the issue and with everything going on this past week, I am sure he is a lil behind on what he wants to get done.

[soky]

Originally posted by Vixen
I am sorry guys but I do my best on the weekends to keep Admin off the board since he works 12 hours a day, 5 days a week which is down from 12 hours a day, 7 days a week (for the past 2 1/2 years). He pops in here from time to time on Saturday and Sunday, as you can see from viewing some of his posts. I can tell you that he has been looking into the issue and with everything going on this past week, I am sure he is a lil behind on what he wants to get done.

Thank you Vixen!


.............. Again.

[admin]

We are trying to find how to kick these users off the system that are just sitting in mssql. We had to do this in mysql and it worked great. but mssql offers no way to do this very easy from what I have seen. So I may end up with 2 options. Start shuting off users that are just sleeping on the mssql servers and using up CPU, BANDWIDTH AND MEMORY..

If any one knows how to kill sleeping users say after 300 sec in mssql I am open that would fix a lot of the issue other wise I will start kicking users off that do this on monday from what we can tell.

[Kpatel]

soky My issues is not related to EM its related to Web application that uses MSSQL, I understand the problem with EM and I not complaining anything about it as there number of workarounds EM...

Today is saturday and I am again wasting my time on it...thanks finally someone from support replied

[Kpatel]

Is it possible to move me to MSSQL1, I was testing something and it seems more than two users are connected to web sites and sever gives up now I am also getting errors telling Check your network documentation...

[Alessandro]

Excuse me Kpatel, what do you mean for "...number of workarounds EM.."?

All hints are well accepted, of course when you are ok again with your sites...

[vonbrocklin]

Originally posted by admin
other wise I will start kicking users off that do this on monday from what we can tell.

Brad: will you be warning people prior to kicking them off? I highly doubt any of my clients are at issue (none are even on mssql2) but if they were, I would sure like to know about it before you kicked them off without notice. Thanks.

[Brangwyn]

Sleeping connections are either waiting for a lock or user input or are orphaned sessions caused by a lack of proper closing of the SQL connection by the client application. They do degrade performance when they are orphaned. But you can't indiscriminately kill the processes. Sleeping connections MAY simply be waiting for a user that *is* alive.

Windows periodically checks inactive sessions to ensure they are active. If a session does not respond, it is closed and SQL Server is notified. The frequency of the checking depends on the network protocol and registry settings, the default is around 2 hours.

I notice there's someone on MSSQL now with 50+ sleepers chances are this is bad code and if you can track this sucker down you could notify them.

To find a lot more good info if you have SQL Books Online installed then simply search for "orphaned sessions" it's got its own troubleshooting section.

Heres the all important REG Key you want to change.

{HLM\System\CurrentControlSet}
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
Description: The parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If the remote system is still reachable and functioning, it will acknowledge the keep alive transmission. Keep alive packets are not sent by default; this feature may be enabled on a connection by an application.

Try a setting of around 5-10 minutes to start with and see how that goes.

My invoice is in the mail