July 12, 2010 at 8:37 am
Hi guys,
if there is a large database.and someone fires a query(it can be t-sql or rpc).
its taking a hell lot of time.i dont wanna kill this process instead can we do something to speed up this process like playing with tempdb or log files.
July 12, 2010 at 9:11 am
Not while it's running.
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
July 12, 2010 at 9:17 am
I would agree with Gail. Once it starts, there's nothing you can do. Before it starts, there are some config possibilities (MAXDOP, Query limits), Resource Governer (SS2K8) that can help mitigate issues.
You also can tune the query, indexing, data file placement, to make specific types of queries run faster.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
July 12, 2010 at 9:25 am
If the query is blocked, you could kill the blocking connection, but something still has to die.
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
July 12, 2010 at 11:26 am
GilaMonster (7/12/2010)
If the query is blocked, you could kill the blocking connection, but something still has to die.
Yeah, I was going to say, killl all the other connections so the bad one has a clear path and all the resources.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply