MSSQL 2008 R2

Question

MSSQL 2008 R2

pallavi.unde

SSCommitted

Points: 1987
More actions
December 31, 2011 at 12:23 am

#262243

Server pc has Operating system :- Windows Server 2008
and other pc (windows xp) accessing database from Server pc
I am Using MSSQL 2008 R2 database.....
it made a system too slow... It takes 45 min to open 18,876 rows
also other application of .net which are connected to the database takes too time.
those PC which having visual studio that are affected badly for slow work...
Is it Hardware issue(RAM Size)? or MSSQL 2008 R2...???
Thanks & Regards,
Pallavi

Viewing 9 posts - 1 through 8 (of 8 total)

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

Devendrakumar SSC-Forever Points: 42493 More actions · Answer 1

It depends on various factors. For example network bandwidth, server utilization, RAM, the table structure itself and calling query. We can’t guess with the minimum information provided by you.

Performance Tuning of Server Instance is a big assignment. Please hire professional services if you find difficulties in it. Please DON’T change server configuration (if you read / suggested by someone) on PROD environment. Test is applicability in a test server.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

Is the problem isolated to one or more tables?

What happens is you log onto the Server?

Have you looked at task manager, Select run 'taskmgr' on the Server.

How about the SQL Server Logs?

Have you tried executing sp_who2 and look for blocking,etc?

I like sp_who3 which you will have to download.

Try querying the master.dbo.sysprocesses table and look at the wait times & types for the processes that are querying the table?

Have you considered running Performance Monitor?

You may want to run profiler as well.

Good Luck!

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 3

I'd check wait stats and use sp_whoIsActive (a lot more info than sp_whoX)

http://sqlblog.com/files/default.aspx

http://www.sqlskills.com/BLOGS/PAUL/post/Wait-statistics-or-please-tell-me-where-it-hurts.aspx

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 4

Actually can you post the actual execution plan?

Unless you have major blocking this is more a case of tuning the query than tuning hardware & server.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

If the system in general is slow, I'd start here.

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

Btw, what business does an app have for pulling 18 000 records down? No one is ever going to read that volume of data. Sounds like some database-side filtering or aggregation needs doing, or some rethinking of the app in general.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 6

Ninja's_RGR'us (12/31/2011)
I'd check wait stats and use sp_whoIsActive (a lot more info than sp_whoX)
http://sqlblog.com/files/default.aspx
http://www.sqlskills.com/BLOGS/PAUL/post/Wait-statistics-or-please-tell-me-where-it-hurts.aspx

Thanks for the link. 🙂

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 7

GilaMonster (12/31/2011)
If the system in general is slow, I'd start here.
http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/
http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/
Btw, what business does an app have for pulling 18 000 records down? No one is ever going to read that volume of data. Sounds like some database-side filtering or aggregation needs doing, or some rethinking of the app in general.

Good points Gilamonster. 🙂

I see that you reverted to your old Avatar?:cool:

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 8

Welsh Corgi (12/31/2011)
I see that you reverted to your old Avatar?:cool:

Yeah. I'm playing KOTOR again (SWTOR not available in my region) and playing in an online PBP starwars RPG, so figured it was time to pull an old favourite out.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass