August 17, 2015 at 9:48 am
- sms takes a good 3-5 minutes to open before it even let's me choose a database to connect to
Also make sure the msdb db is not overloaded with, say, obsolete backup rows and other extra rows. SQL uses msdb when opening ssms.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
August 18, 2015 at 8:55 pm
tfeuz,
You know that those numerous updates on #tables and persistent [tmp] table are extremely bad practices coming from procedural programming languages. They consume heaps of resources and slow everything down dramatically.
If you post the code of the stpred procedure I could possibly show you how replace all those syaging tables with simple DT's and complete the calculations in one or two queries.
_____________
Code for TallyGenerator
August 18, 2015 at 9:00 pm
And talking about resources.
From what you said - it must be the case of memory shortage/failure on the "slow" server.
Compare memory availability on each server, how much of it allocated to SQL Server instances (all of them, not only those you're looking at).
May be it's not only about physical memory. Check allocation and performance of tempdb's as well.
_____________
Code for TallyGenerator
August 18, 2015 at 9:01 pm
And talking about resources.
From what you said - it must be the case of memory shortage/failure on the "slow" server.
Compare memory availability on each server, how much of it allocated to SQL Server instances (all of them, not only those you're looking at).
May be it's not only about physical memory. Check allocation and performance of tempdb's as well.
_____________
Code for TallyGenerator
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply