You could always restore the backup so you can then back it up splitting it across multiple backup files to ensure they are less than 10GB.

It could be related to having too many VLFs in the log file. See the article below and the related articles in the "Resolution" section.

http://support.microsoft.com/kb/2028436

I have a Windows 2012 cluster running a default instance of SQL 2012 and a named instance of SQL 2008R2 without issue. The named instance will eventually go away once...

It's known as a double hop issue. You need to setup delegation or use a SQL login for the linked server.

http://msdn.microsoft.com/en-us/library/ms189580(v=sql.105).aspx

I was actually thinking about doing this same thing today with a SQL 2012 cluster but since it's active/passive, I didn't want to license both node by installing RS on...

Here's an idea from the SQLCAT team. I assume it would work with data files as well. I would test this thoroughly in a test environment first.

http://sqlcat.com/sqlcat/b/msdnmirror/archive/2010/04/05/moving-the-transaction-log-file-of-the-mirror-database.aspx

You could grant view definition rights in the test and production environments to the developers for the dbo schema. This way they would not need to grant view definition to...

Under the advanced tab for the job step where you specified the output file, there is a checkbox for "Append output to existing file". Without this box checked the output...

If you are trying to find out which node SQL is running on(the active node), you can use the query below.

select SERVERPROPERTY('ComputerNamePhysicalNetBIOS')

Check out sysjobs and sysjobsteps in the msdb database.

http://www.sqlservercentral.com/articles/SQL+Server+2008+R2/70092/[/url]

If all the stored procedures are in the same schema you could grant execute on the schema like so.

GRANT EXECUTE ON SCHEMA::[dbo] TO [UserOrRoleName]

It is a system stored procedure and I've never had any issue executing it to reduce the size of the current error log. You can read more about it if...

EXEC sp_cycle_errorlog ;

GO

Thanks for the explanation Gail! That was what I was looking for.