Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 SQL Database Running Slow

Author  Topic 

mark.innes
Starting Member

7 Posts

Posted - 2006-05-18 : 07:52:17
Hi,

I have two database applications, one is running fine and the other is so slow it's ridiculous. The slow application is Pegasus Opera II SQL which is running on a seperate box to SQL 2000. The App server has 2 GB memory and a 1 GB switch and the SQL server has double the memory.

I notice in Enterprise manager that the database without a problem is running at a fixed memory for 1 GB out of the 4 and the problem app is running dynamically, could this be part of the problem? The network has been checked to no avail and the traffic between the two servers are minimal which points me to either the SQL configuration or the fact that Pegasus OII SQL is just too slow!

Any idea's on the memory setting and anything else would be appreciated

Thanks

Mark

nr
SQLTeam MVY

12543 Posts

Posted - 2006-05-18 : 08:01:26
Try using the profiler to see if it is the server giving a slow response to queries or not.
Then try running the queries in query analyser to see how they run there.


==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

mark.innes
Starting Member

7 Posts

Posted - 2006-05-18 : 08:06:26
Thanks for that,

Do you have any recommendations to the events to use as I am new to this utiltiy?

thanks

Mark
Go to Top of Page

azmi
Starting Member

37 Posts

Posted - 2006-05-19 : 11:49:20
In your cause try take event using proflier, sp:stmtstarting/sp:recompile/sp:stmtcomplete.U can also also filter duration(ms) which take too much time when running the query or sproc. U need to pay attention with this query and sproc..
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2006-05-19 : 12:45:15
It will default to sql batch completed and rpc batch completed. Add the start events and remove the login things.
That'll do for a start.

You can also add the sp
http://www.nigelrivett.net/SQLAdmin/sp_nrInfo.html
to master and run it.
It will show you whats active and the command. You can look at what's taking a lot of disk io.



==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-05-19 : 13:15:11
"Do you have any recommendations to the events to use as I am new to this utiltiy?"

In the "Template Name" choose "SQL Profiler TSQL Duration" - that's a pretty good Starter-for-10 set for finding slow queries.

In the FILTERS put a LIKE test on the DATABASENAME so it is restricted just to the database you want to test - that may cut down the wibble.

Kristen
Go to Top of Page
   

- Advertisement -