April 6, 2008 at 10:50 pm
Only way to tell is to see the code 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2008 at 12:04 am
The SQL Engine, by default won't release memory. You can specify the min and max memory settings (if necessary) and SQL will manage its memory within those boundries. The only time it will release memory is if the OS signals a low memory condition.
Sounds like a badly tuned query. Table definitions please, along with any indexes and the query. An idea of the applicable row counts in the tables and resulting output will also be useful
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
April 9, 2008 at 6:11 am
Have you tried a REINDEX ?
http://www.ITjobfeed.com
April 11, 2008 at 3:05 am
Hi All,
thanks for yours fast responses and I'm sorry for the late of the update. The problem is solved by itself. I don't how it was happened, but this week the job lasted only five minutes as before.
Thanks a lot for your help and interest. I only think that there a was a problem on the machine.
Best Regards,
Danilo
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply