I been given a task to convert all VB.NET routine execution process into SQL Server JobS.
Now here are my basic questions. 1. I beleive that SQL Jobs will run in their own threads? so no harm if I run 100 Jobs on same time intervals? Offcourse I should have enough resources.. 2. I have around 10 Jobs which runs every 3 minutes, what about if I make 10 different jobs or is it best to encapsulate in one SP, and run it through one Job...?
Thank you so much Amighty SQL Goddess. One further and last question.
If my SYSTEM Restarts and normally awaits for Login, in background SQL Services will be started, so all my jobs can still be executed without even login? Sorry about that quicky one, I shoul dhave to to give it a try, but havn't got any extra system with SQL on to restart to test...
Jobs use the SQL Server service account. Your system does not need a person logged into the console in order for anything in SQL Server to work.
In fact, we don't have people logged into our consoles. We make them connect to a client machine and work on the SQL Server from there. Our SQL Servers are almost always in a logged off state unless we are doing maintenance on them such as installations.