DECLARE @sql NVARCHAR(MAX) = N'

EXEC [YourDatabase]..sp_executesql N''CREATE USER [domain\bck_user] FOR LOGIN [domain\bck_user]''';

EXEC sp_executesql @sql;

SET @sql = N'

EXEC [YourDatabase]..sp_executesql N''EXEC sp_addrolemember N''''db_backupoperator'''', N''''domain\bck_user''''''';

EXEC sp_executesql

Recovery mode refers to the transaction log, which is not the same as server logs.

NOLOCK is not a performance tool and when used as such is dangerous.

http://eohmicrosoft.blogspot.com/2012/08/nolock.html

Hi,

If you cast your VARCHAR(MAX) to XML then SSMS can display the entire contents in an XML editor window.

DECLARE @Cmd NVARCHAR(MAX);

SET @Cmd = CAST('/*' AS NVARCHAR(MAX)) + REPLICATE(CAST('x' AS NVARCHAR(MAX)),50000)...

You have a comma just before the END statement. Remove that.

Note, @@FETCH_STATUS contains one of the following values:

0: The FETCH statement was successful.

-1: The FETCH statement failed or the row was beyond the result set.

-2: The row fetched is...

Increase the size of your variables to use a longer path

DECLARE @MyFileName varchar(255), @COMMAND VARCHAR(255)

AdventureWorks2012 as listed in your error message is 2012

Other way. You cannot attach a 2012 database onto an earlier version.

UPDATE Vehicle

SET Version = Version + ' BT'

WHERE unitnr = '140'

The book should be forward compatible.

Patch installed, all restores went through without an issue.

Thanks.

Thanks. I'll feedback as soon as it is installed on our test server.

I have a number of users connected to the server so I cannot try it without Intellisense.

I found a workaround for now:

1. Delete the database before restoring.

2. Open a remote desktop session on the server and run the restore there.

Strange.

Edit to add: This is not consistent,...