Error 105, incorrect syntax near...

There should not be commas after the

istask = 1,

AND

isparent =1,

I've removed the brackets and commas below:

If you keep finding issues, just run the statement without...

The user is probably selecting SQL authentication rather than Windows / AD authentication.

Error 4145 is:

An expression of non-boolean type specified in a context where a

condition is expected

Looks like the "istask" clause is missing a matching statement.

ie. istask = 1

Also space out your...

In msdb.dbo.sysjobactivity there is a run_requested_source column. That will tell you if a schedule or a user executed a job.

Values are documented here: https://msdn.microsoft.com/en-us/library/ms190484.aspx

If a user, check the job...

Not sure why, as I just tried the same thing and it did not hide the text box in the header after hiding the column in the tablix.

You can set...

If enterprise edition, then as per Eddie's linked licencing document, you need to licence all physical cores of the host, so 32 cores, which gives unlimited VMs.

If you licence just...

I'll give you my take on it.

We use mostly 1 instance per VM as well, you are licencing the ESX host cores, not the virtual machine, so there is no...

Since no one else has responded, I've had a similar rendering problem where the reports displayed the parameter header area but blank report:

http://stackoverflow.com/questions/5968082/ssrs-2008-r2-ssrs-2012-reports-are-blank-in-safari-and-chrome

You need to update the correct DIV based...

BIDS VS2010 is for SQL 2008 R2 SSIS, BIDS VS2012 is for 2012.

I'm not sure about the .Net version, but you can probably assume 2008 is .NET2.0 and...

Check the SQL Job owner. If it is set to a login that is a member of the sysadmin role, then the job will run as the SQL Agent...

I also get a collation conflict on line 85 for databases like sharepoint which have a different collation to server default.

I've found it works fine when changing line 85 from

...

Thanks I've found this script very useful.

However the last update for contained databases seems to have broken the script for SQL2005 & SQL2008.

Line 63 has a reference to...

Have you seen this?

http://blog.glo-networks.com/2012/08/08/microsoft-sql-transaction-log-shipping-to-a-remote-server-without-smbcifs-not-actually-that-tricky/

Unless you have the log backups back to May 2nd 2015 then you'll need to restore a new full backup.

I dont get this issue in SQL 2014 SP1 or SQL 2014 CU6?

It's the same statement generated with or without data.