December 9, 2011 at 7:30 am
Dev (12/9/2011)
prashant-507002 (12/9/2011)
I think i have to post support ticket to microsoft for the same.I am not sure on it. It's not a bug or product flaw. It also depends on your support agreement. Also, they can’t jump in immediately to rescue you. They will take their own time.
They will not do any magic except what we have already suggested to you.
If you say this is an urgent matter with prod down + you are willing to be there 24/7 to fix the issue, then you get a call back within 2 hours and no breaks untill the issue is resolved. I did 1 call like that on a week-end. It started at 695$ (overtime fee).
It ended up costing me nothing because it was a real bug. But in this thread's case there's clearly no bugs involved.
December 9, 2011 at 7:31 am
prashant-507002 (12/9/2011)
I think there are some hidden command in sql server which Microsoft not make it public.Can any body know the powershell command?
I'm calling troll. And Steve too.
December 9, 2011 at 7:36 am
prashant-507002 (12/9/2011)
I think there are some hidden command in sql server which Microsoft not make it public.Can any body know the powershell command?
Now I will silently watch the thread... I would like to see how Powershell can save us from such mistakes.
December 9, 2011 at 7:37 am
Ninja's_RGR'us (12/9/2011)
Dev (12/9/2011)
prashant-507002 (12/9/2011)
I think i have to post support ticket to microsoft for the same.I am not sure on it. It's not a bug or product flaw. It also depends on your support agreement. Also, they can’t jump in immediately to rescue you. They will take their own time.
They will not do any magic except what we have already suggested to you.
If you say this is an urgent matter with prod down + you are willing to be there 24/7 to fix the issue, then you get a call back within 2 hours and no breaks untill the issue is resolved. I did 1 call like that on a week-end. It started at 695$ (overtime fee).
It ended up costing me nothing because it was a real bug. But in this thread's case there's clearly no bugs involved.
Unfortunately OP is not that lucky... 🙁
December 9, 2011 at 7:40 am
Nothing to do with luck.
And do you not read what we post on purpose or you just like to post?
December 9, 2011 at 7:41 am
prashant-507002 (12/9/2011)
I think there are some hidden command in sql server which Microsoft not make it public.
There are lots of hidden commands in SQL Server that Microsoft doesn't make public. (eg sp_MSForEachDB). They're not going to undo an update and get you your data back.
Restore your database to another instance or another server and copy the data over. That will get you the data back with minimal additional fuss. If you want to faff around chasing magic unicorns and undocumented commands for a few days, well it's your database and your job.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 9, 2011 at 8:17 am
Ninja's_RGR'us (12/9/2011)
Nothing to do with luck.And do you not read what we post on purpose or you just like to post?
Don’t you like me to be observer? 😀
Well, I read it. My point was the support call to Microsoft will cost him, which you saved luckily (coz they found bug).
December 9, 2011 at 8:31 am
Dev (12/9/2011)
Ninja's_RGR'us (12/9/2011)
Nothing to do with luck.And do you not read what we post on purpose or you just like to post?
Don’t you like me to be observer? 😀
Well, I read it. My point was the support call to Microsoft will cost him, which you saved luckily (coz they found bug).
Obvserving is usually silent & internal ;-).
Commentating and giving useful output is another beast altogether. :Whistling:
December 9, 2011 at 8:38 am
Ninja's_RGR'us (12/9/2011)
Obvserving is usually silent & internal ;-).Commentating and giving useful output is another beast altogether. :Whistling:
So where do I stand in your classification? :w00t:
BTW Did you call Steve? I am seriously waiting for Powershell Magic.
December 9, 2011 at 8:41 am
Dev (12/9/2011)
Ninja's_RGR'us (12/9/2011)
Obvserving is usually silent & internal ;-).Commentating and giving useful output is another beast altogether. :Whistling:
So where do I stand in your classification? :w00t:
BTW Did you call Steve? I am seriously waiting for Powershell Magic.
Yes.
And Yes.
December 14, 2011 at 7:40 am
Hi guys
I have find one link in which they mention recover data from transaction log file.
December 14, 2011 at 7:45 am
No it tells you to do a RESTORE of your backups. The same thing we told you 50 times to do already.
You can't use only the logs to rebuild a DB.
December 14, 2011 at 7:52 am
Ninja's_RGR'us (12/14/2011)
No it tells you to do a RESTORE of your backups. The same thing we told you 50 times to do already.You can't use only the logs to rebuild a DB.
+100
@Prashant: What's the update on your issue?
December 14, 2011 at 8:01 am
I did the backup restore but i am yet in curiosity to know the alternate way.
December 14, 2011 at 8:06 am
prashant-507002 (12/14/2011)
I did the backup restore but i am yet in curiosity to know the alternate way.
Don't screw up the data.
If you screw up the data you need a backup.
This is a binary scenario. No in betweens here.
Happy to have helped!
Viewing 15 posts - 31 through 45 (of 58 total)
You must be logged in to reply to this topic. Login to reply