Viewing 15 posts - 16 through 30 (of 54 total)
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...
June 13, 2016 at 4:04 am
Well it defaults to "Restore with Recovery" - is this correct?
June 13, 2016 at 3:48 am
No I'm afraid not. I will keep digging - thanks for your assist this far.
J.
June 3, 2016 at 8:04 am
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...
June 3, 2016 at 3:41 am
Awesome Drew. This works. Thank you both. J.
November 4, 2015 at 8:52 am
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...
October 6, 2015 at 4:56 am
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...
October 6, 2015 at 4:07 am
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.
October 6, 2015 at 3:56 am
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...
October 6, 2015 at 3:33 am
Thanks. I figured this out. I''m a db owner and cannot belong to both.
J.
September 25, 2015 at 9:24 am
Thanks grant. Food for thought all right.
Cheers,
J.
August 7, 2015 at 9:42 am
Thank you Grant - I found what I'm looking for. I notice that there is a verify only option to restore.
RESTORE VERIFYONLY FROM DISK=blah
Worth considering from my pov.
Thanks,
J.
August 7, 2015 at 7:06 am
Thank you Orlando - probably ignorance on my part (to answer your question).
I'm calling this from inside a maintence plan package. I will refactor and see if it works....
July 20, 2015 at 3:56 am
Hi, thanks for that. Actually I found that this works a treat for me in my env:
set @SqlCmd = 'powershell.exe Robocopy C:\share\testSource \"c:\share\test Destination\" *.bak /S'
Cheers & thanks,
J.
July 17, 2015 at 7:20 am
Thanks John for your comments. I got this sorted with this article:
https://www.mssqltips.com/sqlservertip/1618/using-the-forfiles-command-to-delete-sql-server-backups/
July 8, 2015 at 4:41 am
Viewing 15 posts - 16 through 30 (of 54 total)