Showing posts with label older. Show all posts
Showing posts with label older. Show all posts

Monday, March 12, 2012

Help needed to restore SQL Database

Hi Gurus,

Can anyone assist?

How to recover the database if I have only the current transaction log and a older version of .mdf & .ldf files. No backup had being performed via Enterprise Manager.

I have installed MSSQL2000 on Windows 2003 Server. Created a new database 'sample' and inserted some data into the 'sample' db. Afterwhich, I offline the 'sample' db and copied the .mdf & .ldf to another backup directory.

Restart the database by bring it online again and continue to insert more data ... (approx 100,000 rows of data).

Afterwhich, I tried to damage the running database .mdf file and the database went into offline / suspect mode.

How can I recovered to the point in time of failure based on just current transactional log & older version of .mdf & .ldf files?

Can any gurus out there advises?If you have not been making backups, you will not be able to recover to a point in time. Recovering to a point in time requires that the database be in the 'Full' recovery model and that you make periodic full backups combined with transaction log backups. The best that you *might* be able to do in this scenario is to perform a single file attach (see sp_attachdb).

Regards,

hmscott

Friday, February 24, 2012

Help me please! (production DB marked as suspicious)

Hi everybody,

DBMS - MS SQL 6.5
I have removed physical files: Name.DAT and NameLog.DAT
from folder and put older files there with the same names.
After restarting the engine has marked my DB as suspicious.

Then I moved previous files back - database still suspitious!!!

I have no idea how to restore data base status after removing phisical files?

I need help as my MS SQL 6.5 marked as suspicious my production
database.If you can replace the DB by this way,why MS give some backup,restore function?|||If you don't have a valid backup and all you have is the .Dat and .Log files. Try attaching those rather than just replacing the old files. Otherwise have a look at sp_resetstatus.

Cheers|||Sorry, I just noticed that you are on version 6.5. I'm not sure if the info will be valid for that version, you will have to try it to find out.

Thanks,

Originally posted by bmalar
If you don't have a valid backup and all you have is the .Dat and .Log files. Try attaching those rather than just replacing the old files. Otherwise have a look at sp_resetstatus.

Cheers|||True you should use SP_RESETSTATUS, before that use:

sp_configure 'allow updates',1
go
reconfigure with override
go

After the procedure is created, immediately disable updates to the system tables.
sp_configure 'allow updates',0
go

reconfigure with override
go

... then use SP_RESETSTATUS and reboot the server.

Help me please with SQL!!!

I was wondering if anybody could help me with this problem for access97 SQL

I want this code to inquiry records that are 3 yrs and older, with a year_type of 1. Can somebody help me code this please!!!!!!!!!!!!

Here's what i have so far:

DELETE [ArchBOILER].[Inspection_Date], (DateDiff("d",[Inspection_Date],Now()))/365 AS Differance, Year_Type
FROM [ArchBOILER]
WHERE ( ( ( ( DateDiff ("d", [Inspection_Date], Now() ) ) / 365 )>=3 )are you using DELETE to to inquiry records ?|||yes

Originally posted by Bigced_21
I was wondering if anybody could help me with this problem for access97 SQL

I want this code to inquiry records that are 3 yrs and older, with a year_type of 1. Can somebody help me code this please!!!!!!!!!!!!

Here's what i have so far:

DELETE [ArchBOILER].[Inspection_Date], (DateDiff("d",[Inspection_Date],Now()))/365 AS Differance, Year_Type
FROM [ArchBOILER]
WHERE ( ( ( ( DateDiff ("d", [Inspection_Date], Now() ) ) / 365 )>=3 )