mallikachowdhary 98955 (7/24/2014)
I have a job defined in SQL server 2008 which runs a stored procedure of select query which fetches around 230000 rows . One one server this job runs in 6 hr but on another server this jobs takes around 1 day and 15Hr+.
6 hours for 230,000 rows sounds horrible in the first place, nevermind the extended time.
If you take a look at the link in my signature for index/tuning help, it'll show you how to get us what we need to help you. In particular, we need the execution plans. Understandably it'll be tough for you to get the actuals here (which are the preferred), but even the estimated ones and being able to see the differences between them would help.
This is more than a "Oh, it's this..." type of simple answer. It could be a tipping point in the data volume, a bad statistic, or any other number of items. It could even be a concurrency problem, but at 6 hours for the code I can't see us not being able to help you get that running with more speed.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA