February 13, 2008 at 7:46 am
Hi,
I am getting so many section idle when I run sp_who2 and all is SQLDM0_123 etc.
Looks like one of the DTS is causing a problem but that job is executed successfully.
Any hint or suggestion what to do with this SQLDMO it is generating almost 30-40 idle section.
February 13, 2008 at 7:53 am
Most likely candidate is MOM (Microsoft Operations Manager) or NetIQ. Are you running either of these?
Tommy
Follow @sqlscribeFebruary 13, 2008 at 7:55 am
Hi Tommy,
Thanks for helping me out, MOM and Net how do I verigy weather this is running or not and why this is causing a problem. Can I stop it if they are using?
Please help
Nita
February 13, 2008 at 8:02 am
Check out TaskManager and look for the PID or Start -> Run -> Services.msc
You should be able to identify the service and follow up w/ your SysAdmin. Both of these applications are notorious for this 🙂
Tommy
Follow @sqlscribeFebruary 13, 2008 at 8:18 am
Hi Tommy,
I don't see any MOM (Microsoft Operations Manager) or NetIQ services.
Thanks
Nita
February 13, 2008 at 8:32 am
Are you using any SQLDMO ? i.e. sp_OACreate
The SQLDMO connections aren't being destroyed. What build are you running?
Tommy
Follow @sqlscribeFebruary 13, 2008 at 8:49 am
You are the King yes it is used in that SP which is called by that DTS.
EXEC @Details = sp_OACreate 'SQLDMO.SQLServer', @ids OUT
Now what should I do to avoid this problem or is there a way I can put to close this idle process after I call sp_OAcreate?
February 13, 2008 at 8:58 am
🙂
You need to destroy the object afterwards - sp_OADestroy - i.e.
EXEC @resultcode = sp_OADestroy @ids
if @resultcode = 0
Print 'destroyed object'
Tommy
Follow @sqlscribeFebruary 13, 2008 at 9:19 am
Thanks
Nita
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply