Restore From Snapshot After Changing Recovery Model
Given the follwoing scenario: You create a snapshot of a database with full recovery model, change it's recovery model to simple, then perform several updates/modifications on the database, before you finally (due to an error) restore the database from the snapshot.
Will the log chain be broken or not? The resteore sets the recovery model back to full, but I'm still a bit "curious" about the transaction logs.
View Complete Forum Thread with Replies
Sponsored Links:
Related Messages:
Can We Pause Log Shipping, Bring Primary Db To Simple Recovery Model And Then Back To Full R Model?
We have the following scenario, We have our Production server having database on which Few DTS packages execute every night. Most of them have Bulk Insert stored procedures running. SO we have to set Recovery Model of the database to simple for that period of time, otherwise it will blow up our logs. Is there any way we can set up log shipping between our production and standby server, but pause it for some time, set recovery model of primary db to simple, execute DTS Bulk Insert Jobs, Bring it Back to Full recovery Model AND finally bring back Log SHipping. It it possible, if yes how can we achieve this. If not what could be another DR solution in this scenario. Thanks Much Tejinder
View Replies !
View Related
Best Recovery Model
What would be the best Recovery Model for: a database which is 4 gig in size and imports via MSAccess queries and also stored procedures approximately 400,000 meg of data each month (and some other update queries are run against it) and it is also queried off of for totals on weekly basis? The problem is that the SQL Server box only has 512 meg of memory and the tranlog on this database grows tremendously each import and when update queries are run against it. This tends to slow things down a bit on our other databases. We are getting a new SQL Server box but until then, what would be the best recovery model? I currently have it as Bulk-Logged and allow the tranlog to grow by 10% (with a base of 250 meg). The tranlog grows to up to 5-10 gig and in order to shrink it, I have to change the recovery model to Simple, and then back to Bulk-Logged in order to shrink it (I've tried all the dbcc shrinkdatabase, dbcc shrinkfile, dbcc showcontig, and dbcc checkdb commands as well as BACKUP LOG dbName WITH TRUNCACTE_ONLY and nothing will shrink it unless I change the recovery model to simple.)
View Replies !
View Related
DTS - Recovery Model
SQL Server 2000 SP3. Prior to SP3 the recovery model was switched to simple during transfer (Copy object task) and changed back to the previouis setting after DTS was complete. Nice thing because performance was increased and T-Log was keep small. Now I assume that the recovery model is switched to bulk-logged causing the T-Log to explode, to be onest not in all my databases. 1.Is my interpretation regarding recovery model correct? 2.Does anybody knows the reason of this change? Any suggestion is really appreciate. Thank you very much - kind regards.
View Replies !
View Related
Recovery Model
Hello, I'm new to MS SQL Server I want to know which recovery model is good, Full or Bulk Logged as I'm doing full backup at 11:00 PM and diffential Backup at 12:30 PM and from 8:00 AM to 6:00 PM 15 min log backups. Please guide me which recovery model should I choose. Thanks Lara
View Replies !
View Related
Recovery Model
I have created a database in SQL 2000, and I am trying to change the Recovery option to FUll,so I can backup the logs. But when I select Full under the Recovery Option the OK button is grayed out. This is only happing on 2 database. Is this a bug in SQL 2000? Also,I try to do this through Alter Database but I get syntax error. Here the syntax I use: Alter database archive <recovery option> ::=Recovery{Full} Thank You, John
View Replies !
View Related
Change Recovery Model
A quick question about changing recovery model using sql statement. ALTER DATABASE test set recovery_option = RECOVERY { BULK_LOGGED } Error message: [Microsoft][ODBC SQL Server Driver]Syntax error or access violation Immediate help needed !!
View Replies !
View Related
Recovery Model To Simple
We are using a .bat script to restore several client dbs onto our sql server 2000 db. We want to set the client dbs from full recovery to simple. What command should I use in the .bat file to make this change? .bat file == :: Second, restore data from SQL Server backup file to SQL server... isql -E -S ao3ao3 -Q "RESTORE DATABASE CBSN FROM DISK = 'D:MARS_SYSDATAUPDATESCBSNCBSN.BAK' WITH MOVE 'MEDISUN_BCNV_Data' TO 'D:SQLDATACBSN_data.mdf', MOVE 'MEDISUN_BCNV_Log' TO 'D:SQLDATACBSN_log.ldf',REPLACE;"
View Replies !
View Related
Simple Recovery Model
We have a fairly large database that we use to store mom alerts and it stopped alerting as it's transaction log became full. I suggested to the owner of the database to set the simple recovery model so the log could automatically be truncated. However, it appears that the database is frequently reaching it's limit (of 3gb) and I'm having to set the limit even higher on a daily basis. Can anyone tell me why this is occuring? I understood that when the log file reaches 70% it should automatically shrink? Kind Regards Mike
View Replies !
View Related
Recovery Model Problem; Db Properities
Hello,I've follow problem - thing to consider.SQLServer 200 sp3a, ms win 2003 serverdb simple recoveryThere is a production database, wich is around 20gb big. Db is backedup each day completely, but it takes up to 30 minutes.Because there is a simple recovery model, there is no transaction logbackup (it fails anyway), and we do not have up-to-point recovery.I'm considering to switch to full recovery model, but ....The problem is, I do not want to affect performance (when the backup isrunning, database is hardly avalible).So my question will be: does the full recovery model, will be betterfor db performance (for acces and blocking db; means, does it will takeshorter?)Strategy will be (I hope ok) to back up during the week onlytransaction log (incremental), and once at the weekend, full databasebackup.Generaly, which one is better for performance?Which strategy will be the best, to keep performance at high level, butalso have the possibility to restore data (in case of emergency) fromthe newest possible backup.Thanks for helpMatik
View Replies !
View Related
Recovery Model Of Subscription Database
Hi: I am having lot of log problems with Subscription databases. Currently all my subscription databases are on Full recovery mode. I am thinking to change them to simple because I don't I will be doing point in time recovery of them. Do the subcription databases have to be on Full mode? Can I change them to simple to keep my log small and then I do not have to backups of my logs also? Please let me know. Thanks
View Replies !
View Related
Model Database Recovery Planning
I cannot think of any reason, in our environment, why I would recover the model database. Change framework has all databases coming from DEV & QA before landing on PROD. We have never used the model database as framework of new databases either. So, if I discontinued backup of the database, what is my recovery method if it become corrupt? Since mine is not used, can I simply copy it from another server?
View Replies !
View Related
Full Recovery Model - Log Doesn't Grow?
Hi all,I have a SQL Server 2000 database that is using the Full recoverymodel. The database is purely receiving inserts (and plenty of them)with maybe some view/table creation for reporting.In this state I would expect the log to grow ad infinitum but it getsto about 32% used and then empties.The log is not being backed up at all so am I missing something else?CheersDee
View Replies !
View Related
Recovery Model To Be Used For A Data Flow Task
Hello there I have a SSIS 2005 DTSX Package which has several Data flow tasks which directly dump data between tables from 2 different databases. Suppose if my destination database is named, DestinationDB, what recovery model should I select for this database so that my ldf file size does not explode? I want to keep the ldf file as small in size as possible. Currently I have used Simple Recovery model, and the ldf file size goes to around 80 GB. (Inserting around 200 million rows) Will Bulk Logged model be a better option? Also what does a SSIS 2005 Data flow task use internally? (Insert operation or some sort of Bulk Insert between DBs) Please help.
View Replies !
View Related
Log Truncation In The Simple Recovery Model - Can You Help My Understanding Of It Please
On SQL 2000 or SQL20005 will a database's log file automatically be truncated if the database is on simple recovery model? The reason I ask is that we have a database (simple recovery) that keeps growing its logfile each weekend which causes disc space problems. I am kinda new to SS but from the reading in BoL I've done was under the impression that for simple recovery model log records are only needed until the transaction has been written to disc and committed, and that SS will handle truncating obsolete records from the log where necessary. I'm doing DBCC SQLPERF(logspace) which shows this first thing on a Monday morning: Database Name Log Size (MB) Log Space Used (%) -------------- --------------- --------------------- myDB 4841.93 99.19465 Note the size of the log file - the data file is only 700MB! Issuing a DBCC OPENTRAN doesn't show any open transactions, and a CHECKPOINT doesn't do anything to reduce the log space used (which if there were dirty records in the log still not written to disc this ought to do shouldn't it?). The database is only written to as a replication subscriber. Any suggestions what would be causing the log file to fill up? At the moment I'm resorting to BACKUP LOG myDB WITH TRUNCATE_ONLY and considering scheduling this as an hourly job over the weekend - any reasons why this could be a bad idea? Many thanks, Moff
View Replies !
View Related
Recovery Model Indicator - Which System Table?
Hi I hope you can help as I am really scratching my head on this one. I am pulling together an assessment of the Disaster Recovery readiness for an organisation I am working at. Part of the assessment I am doing is the recovery model of each of the databases. I have scripts that are already pulling lots of data from 40+ servers and 500+ databases. However, I cannot seem to find anywhere within the MASTER or MSDB or the database itself where the Recovery Model flag is held. Obviously I can right click on the database and click properties and it is there, but I need to automate this task (as it will probably be a weekly assessment). I have checked sysdatabases and almost every other table, but nothing obvious as to where this flag is. Any ideas?
View Replies !
View Related
Backup Of Ldf File In Simple Recovery Model
Hello, I have a question regarding the backup for the database in Simple Recovery Model. In this Model, I know we can restore only to the last full backup or can use differential Backup, if implemented as a part of backup. But my point of confusion is about the backup of '.ldf' file, should those file should be backed up in the Maintenance Plan, if yes does it help in reducing the size of Log file? Do we need the backup of '.ldf' in phase of Restoring? As I mention my database has Simple Recovery Model, but the size of log file is around 20GB, Could not understand why as in this Model, normally it automatically truncate the Log file? Help me to clear my these doubts, thanks,
View Replies !
View Related
The Statement BACKUP LOG Is Not Allowed While The Recovery Model
Hi All, SQL newbie here. I just looked at my Job Activity monitor and found that my Transaction log backups are failing. I looked at the error and it read as follows: Executing the query "BACKUP LOG [OperationsManager] TO DISK = N'D:\SQL\MSSQL.1\MSSQL\Backup\OperationsManager\OperationsManager_backup_200805061000.trn' WITH RETAINDAYS = 1, NOFORMAT, NOINIT, NAME = N'OperationsManager_backup_20080506100001', SKIP, REWIND, NOUNLOAD, STATS = 10 " failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE. BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. I read some of the posts regarding this error, but I am not sure how to do the steps. How do I change the recovery model? I am new to this so I have no clue how to do this. Any help would be greatly appreciated. Thank you.
View Replies !
View Related
Switch Simple To Full Recovery Model
I have convert all databases to Full from Simple Recovery model. As per documentation, it looks like simple. Based on your experiences , do you think of any problem may come while doing this ? Any impact on application performance after this ? Is this work perferened to do when no body using system ? Thanks
View Replies !
View Related
Changing Article Properties Without A New Snapshot
In our replication environment, the subscriber is initially set up with an snapshot of the publisher database. However, after that, the subscriber and publisher are different and we can never re-initialize from a snapshot again (we purge data on the publisher to reduce the database size but do not purge the same data on the subscriber; we do this by stubbing out the stored procedures on the subscriber that purge data on the publisher). If an article is added or dropped from the publication, using snapshot and synchronize, just these changes are propagated to the publisher (without an entire new snapshot). However, if an Article Property is changed (change SCALL to MCALL under Statement Delivery options for the UPDATE statement), the interface REQUIRES an entire new snapshot. Is there any way I can avoid the new Snapshot? It overwrites the subscriber database and this cannot happen! Linda
View Replies !
View Related
Changing To Simple Recovery Mode
Hi, What is the impact of changing the recovery mode of a database from Full to simple? The client I am at has set their database to full recovery mode, set their log files to grow automatically. But I don't think they have ever done a backup of their transaction log (it has grown to over 19Gig, where the data portion of the database is only around 400M). What is the impact of truncating the transaction log now? After truncating it, i would like to shrink the file to a managable number and change the recovery mode to simple (they don't need transaction log backups) Any info on this would be appreciated. Thanks in advance Jim
View Replies !
View Related
Changing Collation For Tempdb And Model
Hi,I've got a production server with the default collationand User DBs with the different collation.Now when I create temporary tables and compare with the permanent oneswe have collation problems. Is it possible to change tempdb ( andmodel) collations ?Would I need to change master and msdb collations as well?Can I change the master collation? What about all the tables thatalready exist in these system databases?Is it fairly straight forward to change collation for tempdb and modelor it might cause problems in the future - I obvioulsy don't want tomess up with the production serverThanks a lot
View Replies !
View Related
Restore With Recovery And Log Shipping
hello everybody I have custom log shipping . it run every 15 min DB1 located on Server1 DB1 backup logs to server 2 DB2 located on server 3(300 km away from server1 and server 2) Db2 restore logs from server 2 If server1 and server2 become unavailable 1. Would enough login to server3 and run RESTORE DATABASE Db2 WITH RECOVERY to bring db from read only to production mode up last restored log? Thank you Alex
View Replies !
View Related
RESTORE LOG With Different Recovery Path
I'm trying to RESTORE LOG with a different recovery path. Is there a way to do this? I'm getting the below error. I know I could RESTORE from the beginning, but need to RESTORE the log file to the same database schema but different database and server. What steps do I need to do? This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time. For more information about recovery paths, see SQL Server Books Online.
View Replies !
View Related
Database Restore - Norecovery/recovery
Hello all, I just restored a SQL 7 db using the Enterprise Manager GUI interface. I selected the "Leave database nonoperational, but able to restore additional transaction logs" option. I should not have selected this option as I do not have any transaction logs to apply. Anyway, my question is... Is there a way to mark the database as opertational without running the restore again? Thanks, Corey
View Replies !
View Related
SQL 7.0 Restore Fails- Says Use "with No Recovery " Option
Hello, I have a file backup of a database from machine 1. I create an empty database with the same name on machine 2 and copied the backup file to machine 2. When I run a restore database, I get "Preceeding restore operation did not specify WITH NORECOVERY OR WITH STANDBY.Restart tehe restore sequence, specify the options for all but the final step. Restore failed" Database : SQL 7.0 Trying to restore from the Enterprise manager ANy clues as to what might be wrong. Thanks, MMS
View Replies !
View Related
Log Shipping Restore && Recovery Test
I am trying to imitate a DR situation where the primary db is down and I need to recover the secondary db on another server. They are a log shipping pair and so to imitate a DR, I remove the log shipping in the primary server maintenance plan. Then I go to the secondary server and disable the log shipping jobs there and attempt to do the following RESTORE DATABASE database_name WITH RECOVERY but I can't get exclusive use because the database is in use. But I don't see any other users... am I wrong in thinking that the log shipping was completely deleted? Anything I can do to force exclusive access?
View Replies !
View Related
Changing The Primary/base Entity On The Report Model
Let's say there is a relationship A 1--* B defined in a report model. When using the model either in Report Builder or while defining the dataset in Report Designer I find that if I mean for entity A to be at the root and I accidentally click on B's fields, B becomes the root entity. While I understand the reasoning behind this, I cannot find any way to get back to A as the base entity. Even if all B fields are removed from the report, B remains as the root. This is very frustrating as the entire report/dataset will need to be rebuilt from scratch. Any ideas?
View Replies !
View Related
Model Db During Restore
Hello, i have no specific problem but i just want to know your opinion on the issue. Last week I tested my recovery scenario and after installing new server i successfully restored master db. Then I tried to start server, but it wouldn't come up because physical path of model db in master..sysdatabases table didn't correspond to the actual location of db on new server, so that tempdb couldn't be created from model db on server startup. I started server without recovering dbs with exception of master using trace -T3608. Now I hoped that I could restore model using MOVE clause but it gave me error saying that restore operation needs to use temporary table in tempdb. To break this vicious circle I used model db files from installation CD and put them to the expected location. After two restarts server accepted the files and I went on restoring msdb and user databases. But I'm sure I must be missing something and there must be better way to do this but i haven't been able to find anything relating to this problem. Thank you for your input. mojza
View Replies !
View Related
|
TRACKER
