July 29, 2004 at 1:25 am
Hi ,
One of my friend has a serious problem at one of his client site.
Problem is, the client admin took a copy of both mdf & Ldf file. by stopping the sql server service to another location to back up his data (instead of taking a full backup he copy every night both files) !
That point of time file size were
E:\DATA\RTDEFACC.MDF 65 MB
E:\DATA\RTDEFACC.LDF 76 MB
Next day morning the Files were missing in the sql server Data Folder. it Happedn teh second Time for him so he copied this file (Previous days back up in MDF and LDF )to the data folder and started the sql server the data file sizes became.
E:\DATA\RTDEFACC.MDF 9 MB
E:\DATA\RTDEFACC.LDF 1.3 GB
so they dettached and try to attach the files from his copy folder again but giving the following error .
LOCATION : FILEMGR.CPP : 3422
EXPRESSION : FEB -> GETFILESIZE() >= NEW SIZE
SPID :8
PROCESS id : 652
CONNECTION BROCKEN
I know that they made a mistake of not using teh back up utility. but can any one tell what is this error and how they can get the data back ?
Thanks in Advance
Jeswanth
--------------------------------
July 29, 2004 at 5:41 am
What 's happening if he copies the 65/76Mb files again from his backuplocation to another location (or renames them) at the db-server and then sp_attachdb them to a new db ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
July 29, 2004 at 5:56 am
Thanks for the reply. He tried attaching again then he was getting that same error I mentioned. But he didnt try the second suggestion to rename the files and attaching again. I will ask him to do the same and will post here teh result again.
Thanks
Jeswanth
--------------------------------
July 30, 2004 at 6:55 am
I've seen smaller file size when coping files like that before, plus they were corrupt. The only why I got around it was using xcopy on the cmd line. That gave the the correct file and size.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply