Powershell would be a good option and the one I'd pursue.

However for those that don't want to dabble in Powershell and don't want to enable xp_cmdshell, you can pipe the...

ROFL

iHurt

You need to use two single quotes

eg:

@query = 'exec uspEmailSQLServerHealth10 ''192.168.1.120'', ''abc'', ''suyog.pagare@gmail.com;;'', ''test'', ''MYSELF''',

If you're editing the SQL statement in Management Studio the entire value for the @query...

Yes.

Basically the global variable has become "corrupted", the GUI interface can't handle correcting the problem, so you have to delete and re-create the variable.

You may be able to fix it...

A selection of examples

http://www.sqlservercentral.com/articles/powershell/65324/[/url]

http://www.simple-talk.com/sql/database-administration/why-this-sql-server-dba-is-learning-powershell/[/url]

http://itknowledgeexchange.techtarget.com/dba/powershell-sql-server-health-check-script/[/url]

Actually xp_dirtree has been around for a...

Unfortunately, as evidenced by a number of replies to this article, its not only executed by...

nplace6530 (2/2/2010)

---

Hi All

...

With:

select @STR = 'EXEC Master.dbo.xp_DirTree "' + @URL + '",1,1'

INSERT #dirpaths SELECT 'PATH: ' + @URL, 1, 1

This replaces the "EXEC master.dbo.xp_cmdshell" command with the...

louis.young, One thing I can think of is to make sure you are in the same database that you created the queue in.

Great article Jonathan, looking forward to more. Especially...

Try this one, http://support.microsoft.com/kb/918992

Using this procedure, you can use OSQL to output all the logins to a single file. If you want individual files per login, just loop through the...

I use the following on SQL 2008 to pull messages off the event queue that are related to a 'sa' login event. Another procedure processes the records in the work...

Top stuff 😎

Now for SQL Server 2000, I would do ... :ermm::crying:

philcart (10/1/2009)

---

Firstly, you're using SQL Server Express which has a hard wired limit of 4GB for the maximum database size. Individually, not that big really, but you have alot of...

Both valid points. But bear in mind that reducing SQL Server memory even further will push more work onto the disks where your real problem is.