Why on earth would I go to the bother of using SSRS to develop a report for something I want to run once? Our company only moved to Office...

As I mentioned a while back - I deal with extremely large ad-hoc reports that often have LOTS of null values in them. When you're trying to do a...

Easy to fix this - make it an setting that one can change in options. That way DBA purists can see their NULL text and people who have to...

The amazingly annoying thing to me is they didn't fix this in 2012 (I see it as a bug, not a feature or acceptable way of doing things).

I think I figured it out, windows authentication isn't going to work I think due to the way SQL Server was installed under the admin user ID (getting IT to...

I actually had to handhold them in packaging SSMS 2008R2 - took about 9 months to finally get it - and of course they've packaged none of the SP's since...

Sounds lovely Mr. Magoo - however, I am stuck on a locked down machine onto which I cannot load anything that hasn't been approved and packaged by our IT department,...

To give you an idea of the data volumes I deal with regularly - I'm looking at one day of lab orders. There's 776,000 records, and just one of...

Besides which - if the results grid isn't designed for copy/paste to Excel or other programs - what the heck is it actually for? Who runs a query and...

It's recurring - but it's different every time, so there's no easy way to construct a workaround. It's hard to believe that everyone who uses this hasn't been screaming...

It is just incredibly frustrating the number of days worth of work I've spent doing copy/replace on "NULL" strings over the last 4 years because of this design flaw. ...

I have had to deal with this constantly - SSMS 2000 did not do this, SSMS 2008R2 does. At least give me an option I can set to have...

I just did more testing and found the following:

If I set up a simple maketable job on my database (not using the linked server at all) but use Run As...

In the link you provided, one of the key passages is:

"Job steps that execute Transact-SQL do not use SQL Server Agent proxies. Transact-SQL job steps run in the security context...

I have never worked with proxy's or credentials...up until a few months ago I was using SQL Server 2000 exclusively. I'm also a developer, not really a DBA, though...