Friday Greetings! 😀

The "Always On" high-availibilty cluster is reason enough for us to upgrade our production environment. Doing away with an older marathon solution and offloading our SSRS reports to...

I was afraid of this. Over to the 3rd party app developers to make the connection string within their client customizable, which slows the delivery of this greatly.

Thanks for the...

"Like I said, once you are connected to SQL Server you are on that box, and it doesn't use/know about a .NET connection string to hop over to another server"

Sorry,...

I think I explained myself incorrectly. I want to do this in a SQL Query.

I have a 3rd party application that allows me to run SQL against the database...

Been using Dynamic grouping for quite awhile within SSRS now. I even apply this over multiple groups within the same report to give an even more valuable piece of work.

It...

Good question - pity the answer was given was wrong :-). Alas folks we're not robots and everyone is allowed a mistake...

I have to say I am a big fan of Tuning Advisor. Some of the databases I work with are an absolute nightmare for performance and the nature of the...

Yeah, but the question did ask for the "output" - SQL Server will append the 00:00:00.000 onto the end, so technically none of the answers are correct.

None of these are correct - as you are casting as "datetime" the results will be as follows;

2002-02-02 00:00:00.000

2049-02-02 00:00:00.000

1950-02-02 00:00:00.000

2000-02-02 00:00:00.000

I am getting the same error when trying to setup a maintenance plan in SSMS 2008. Does anyone know what this error represents or how to get around it?

Thanks

Shay

It turns out one of our Network Admins had decided to install Backup Exec on this same instance of SQL and then removed the databases again leaving the login BUILTIN\Users...

Good point. the last step of normalisation is de-normalisation!