January 22, 2010 at 5:39 am
Rebuild your indexes on a somewhat regular basis, defrag the hard drive if possible, look for tuning indexes and keep stats up-to-date. Those things will help out performance as well by themselves.
January 22, 2010 at 7:49 am
In addition to query tuning, and Index maintenance - I suggest proper indexing.
Another expensive option is to replace your disks with solid state disks or flash drives - very very fast.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 24, 2010 at 6:44 pm
Maybe you can try to use a virtual machine to run the three database, and use another vm to run the others database, and allot appropriate memory to each VM
January 24, 2010 at 11:23 pm
That's a lot more complex than just adding a second instance and moving the 3 DBs there, as has been earlier recommended.
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
January 24, 2010 at 11:38 pm
Heh... with so many folks talking about separate servers, now I know the real reason why MS deprecated such a useful tool as being able to pin certain tables. $$$
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply