MSDE Performance

Question

Post reply

MSDE Performance

vy-454152

Newbie

Points: 6
More actions
July 5, 2007 at 6:00 am

#124897

Hi
Server is HP Proliant wth 2-GB Ram, Installed M.S.D.E and SQL-2000 Client Tool and my Database Size is approx 1.4 GB i have approx 6-user, application is developed in VB.NET,
Moment memory usage crosses 1 G.B. system becomes Unstable process goes slow. sometimes system gets hung despite server being Latest & Branded
Please Reply at Earliest
Thanking You

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

SwePeso SSC-Dedicated Points: 39757 More actions · Answer 1

Have you set an upper limit for SQL Server to use?

Operating system needs about 1 GB to function well.

N 56°04'39.16"
E 12°55'05.25"

Sugesh Kumar One Orange Chip Points: 27311 More actions · Answer 2

Are you running any queries that uses temp tables and results large number of rows i have faced the problem with some what similar kind of hardware thanwe moved to better machine and problem was solved.

Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 3

Hi vy

"* Maximum user connections: 5 before the work load governor will limit the performance."

this is from http://www.vialect.net/page25/page37/page37.html

Cheers

ChrisM

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

Mark Harr SSCrazy Eights Points: 9921 More actions · Answer 4

Actually, it is more than 8 connections when the workload governor kicks in.

Vy, you can check you server's Application Event Log, and see if there are any SQL Server 3629 messages that indicates MSDE is hitting the connection limits for the workload governor. If you are getting many of these messages, it could be that the governor is slowing down the database enough to see the effects that you are experiencing. If only a few messages, I doubt that you will see much effect.

Also note that this is the number of connections to the SQL Server system, not number of users. Depending on how the application was written (multiple concurrrent connections per user or process, using or prohibiting pooled connections), one application user could be using multiple connections. That would hit the workload governor quicker. See http://msdn2.microsoft.com/en-us/library/aa224554(SQL.80).aspx for more info on the governor.

You may want to try setting the upper memory limit for SQL Server to 1gb. You may be having a faulty memory chip that only occurs when stressed by SQL Server. By setting the max memory SQL Server can use, it will cause more tempdb use, and may bypass the memory problem.

If it is connections problem, easiest solution would be to upgrade to SQL Server 2005 Express. That runs essentially as MSDE does, but does not have the workload governor. It is only limited to databases of 4gb, single processor, but only 1gb of memory (vs 2gb for MSDE). It will also run quite a bit faster than MSDE.

Hope this helps

Mark