Hi everyone,

Thank you all for your comments & practices you suggestions, many of which we are already doing. To answer you queries:

We are doing the weekly full back directly to...

Hi Sue,
   
   Thanks for the suggestion. I t was already added but I tried again and moved it around etc for blank and standard templates and tested a...

Hi Jeff (no, the other one)
    Thanks for the suggestions. I tried a few different templates and a few other variations and while handy, I still cannot get...

Hi Jeff, yes the "TextData" column is displaying. I have played with it's location relative to the other ie first, second last position but when I click on the rtow...

Lets use a database restore as an example:

RESTORE DATABASE TestRestore

FROM DISK = 'SomeCorrectPath'

WITH RECOVERY,

MOVE 'WrongDataName' TO 'D:\SQL2014\Data\TEMPCOPY.mdf',

MOVE 'WrongLogFile' TO 'E:\SQL2014\Logs\TEMPCOPY.ldf'

The above will throw an error as the logical file names...

Thanks for the advice. Forgive me but how do you create a different SQL instance lets call it "TestInstance"

I think so - Above the words :"Tail-Log backup" it says :"Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored"

However I feel...

Well it defaults to "Restore with Recovery" - is this correct?

No I'm afraid not. I will keep digging - thanks for your assist this far.

J.

Yes, of course - your right joeroshan. Good spot I should have seen it myself. Well, that's a dead end then. It does not really explain why sometimes the error...

Awesome Drew. This works. Thank you both. J.

I do recall seeing message "x rows effected" but it may have been syntax error on my part. I *may* have done something like:

update someTable

set='newValue'

where someField='oldValue'

As I say - this...

Yes, that's what I thought. But the second SQL (ie the one using the key as unique identifier) is more stable so far. Must be something else kicking in after...

Sorry - I think it poor SQL on my part is the cause. Better to use syntax like this:

UPDATE someTable

SET soemFieldd= 'New Value'

WHERE key = blah

I'm such a dumba**. Apologies

J.

I'm just running ad-hoc update, standard syntax, nothing special. I have never experience anythign liek this before. The syntax is:

UPDATE tableName

SET someField = 'newValue'

WHERE someField = 'OldValue'

Command works and...