Try this code below.

If all else fails, check your ISP. I know with Telus (my ISP) they have blocked most standard inbound TCP ports like 1433.  Of course that blocked any inbound connections...

Speaking from experience. I prefer default values in order to keep data consistent. Also for reporting purposes. I found when tracking down why certain records didn't appear...

.NET applications when closing the connection in the application itself, will still retain the connection to the SQL Server. This is not a bug by Microsoft. It is...

Also Like statements can be a resource hog as well.  It is generally a good idea to stay away from them, unless it's absolutely necessary to use them.

Look in the Books Online about "Isolation Levels".  Then take a look at the READ UNCOMMITED.  That may help in your locking issue.

This helped when there were several instances of...

I'm not sure if this may solve your issue.  But it might.

EXEC sp_add_jobserver @job_name = 'Your Job Here', @server_name = @@ServerName

Yep.  You could do it from the command shell if you wanted to.

declare @cmd varchar(255)

 set @cmd = 'C:\temp\pkzip.exe whatever.zip *.*'

   EXEC master..xp_cmdshell @cmd, no_output

I agree with Bryant.  I worked for an outsourced call centre a year ago.  I have seen how our managers have stretched the truth about reports and information that the...

Thanks for the reply sufian.  I looked in the Windows Services and couldn't find SQL Agent Service in the list.  I did some more searching on google and found that...

Instead of using the command shell to see if the SQL Agent Service is running.  You could use the following command.

EXEC master..xp_servicecontrol QueryState, SQLServerAgent