Return to Answer

Welcome to DBA.SE. Sorry to hear you're having a bad time.

Handling Your Current Situation

If FULL Recovery model is enabled for this database do the following:

1. Stop all transactions/connections to the database. NOW !!

2. Think about your next steps.

3. Take the database OFFLINE and make a copy of the *.MDF and *.LDF files.

4. Bring the database back ONLINE.

5. Perform a Transaction Log Backup (TLOG backup) with the option WITH ... NO_TRUNCATE .... This ensure the data isn't deleted from the TLOG. This step will only work if the database has previously been backed up with a FULL backup

6. Restore database to point-in-time on a different database server using the initial FULL backup (before step 1.) and TLOG backup from the second step. The time should be before the accident happened.

7. Search for the modified data.

8. Extract data.

9. Import data into production server after confirming it is correct.

10. Bring production back online.

If you didn't have the database in FULL recovery model, then changing it now will have no impact. You won't be able to rescue the data, because it probably has already been committed to the database and is no longer available in the TLOG file. If no initial FULL backup has been performed, then these steps won't work.

Cleaning Up

1. Talk to management about what happened.
2. Implement a Change Management process.
3. Implement a solid backup procedure for your database systems.

DBA Tips

Here a couple of basic tips:

1. Always think about your next steps.
2. Ensure you have a backup, before you modify data.
3. If the data is important/productive, ensure you have FULL recovery model enabled and Transaction Log backup is being performed.
4. Only change data in a productive environment after management has told you to do so and if you have an official Change Request that has been signed off.
5. Never touch productive data manually, unless it is during a down-time and you have met the requirements for 1. and 2. and 3.

DISCLAIMER
Please be advised that these steps are by no way complete and do not guarantee a restore of your database and/or data. Please use them as a guideline in your specific situation and be aware that a multitude of unknown causes, could result in complete data loss.

Step 1.) and Step 2.) can be used in any situation

Further additional steps may be required to bring your data back.

Welcome to DBA.SE. Sorry to hear you're having a bad time.

Handling Your Current Situation

If FULL Recovery model is enabled for this database do the following:

1. Stop all transactions/connections to the database. NOW !!

2. Think about your next steps.

3. Take the database OFFLINE and make a copy of the *.MDF and *.LDF files.

4. Bring the database back ONLINE.

5. Perform a Transaction Log Backup (TLOG backup) with the option WITH ... NO_TRUNCATE .... This ensure the data isn't deleted from the TLOG. This step will only work if the database has previously been backed up with a FULL backup

6. Restore database to point-in-time on a different database server using the initial FULL backup (before step 1.) and TLOG backup from the second step. The time should be before the accident happened.

7. Search for the modified data.

8. Extract data.

9. Import data into production server after confirming it is correct.

10. Bring production back online.

If you didn't have the database in FULL recovery model, then changing it now will have no impact. You won't be able to rescue the data, because it probably has already been committed to the database and is no longer available in the TLOG file. If no initial FULL backup has been performed, then these steps won't work.

Cleaning Up

1. Talk to management about what happened.
2. Implement a Change Management process.
3. Implement a solid backup procedure for your database systems.

DBA Tips

Here a couple of basic tips:

1. Always think about your next steps.
2. Ensure you have a backup, before you modify data.
3. If the data is important/productive, ensure you have FULL recovery model enabled and Transaction Log backup is being performed.
4. Only change data in a productive environment after management has told you to do so and if you have an official Change Request that has been signed off.
5. Never touch productive data manually, unless it is during a down-time and you have met the requirements for 1. and 2. and 3.

Welcome to DBA.SE. Sorry to hear you're having a bad time.

Handling Your Current Situation

If FULL Recovery model is enabled for this database do the following:

1. Stop all transactions/connections to the database. NOW !!
2. Perform a Transaction Log Backup (TLOG backup) with the option WITH ... NO_TRUNCATE .... This ensure the data isn't deleted from the TLOG. This step will only work if the database has previously been backed up with a FULL backup
3. Perform a Full Backup.
4. Perform a Transaction Log Backup (TLOG backup).
5. Restore database to point-in-time on a different database server using the initial FULL backup (before step 1.) and TLOG backup from the second step. The time should be before the accident happened.
6. Search for the modified data.
7. Extract data.
8. Import data into production server after confirming it is correct.
9. Bring production back online.

If you didn't have the database in FULL recovery model, then changing it now will have no impact. You won't be able to rescue the data, because it probably has already been committed to the database and is no longer available in the TLOG file. If no initial FULL backup has been performed, then these steps won't work.

Cleaning Up

1. Talk to management about what happened.
2. Implement a Change Management process.
3. Implement a solid backup procedure for your database systems.

Junior DBA Tips

Here a couple of basic tips:

1. Ensure you have a backup, before you modify data.
2. If the data is important/productive, ensure you have FULL recovery model enabled and Transaction Log backup is being performed.
3. Only change data in a productive environment after management has told you to do so and if you have an official Change Request that has been signed off.
4. Never touch productive data manually, unless it is during a down-time and you have met the requirements for 1. and 2. and 3.

Welcome to DBA.SE. Sorry to hear you're having a bad time.

Handling Your Current Situation

If FULL Recovery model is enabled for this database do the following:

1. Stop all transactions/connections to the database. NOW !!

2. Think about your next steps.

3. Take the database OFFLINE and make a copy of the *.MDF and *.LDF files.

4. Bring the database back ONLINE.

5. Perform a Transaction Log Backup (TLOG backup) with the option WITH ... NO_TRUNCATE .... This ensure the data isn't deleted from the TLOG. This step will only work if the database has previously been backed up with a FULL backup

6. Restore database to point-in-time on a different database server using the initial FULL backup (before step 1.) and TLOG backup from the second step. The time should be before the accident happened.

7. Search for the modified data.

8. Extract data.

9. Import data into production server after confirming it is correct.

10. Bring production back online.

If you didn't have the database in FULL recovery model, then changing it now will have no impact. You won't be able to rescue the data, because it probably has already been committed to the database and is no longer available in the TLOG file. If no initial FULL backup has been performed, then these steps won't work.

Cleaning Up

1. Talk to management about what happened.
2. Implement a Change Management process.
3. Implement a solid backup procedure for your database systems.

DBA Tips

Here a couple of basic tips:

1. Always think about your next steps.
2. Ensure you have a backup, before you modify data.
3. If the data is important/productive, ensure you have FULL recovery model enabled and Transaction Log backup is being performed.
4. Only change data in a productive environment after management has told you to do so and if you have an official Change Request that has been signed off.
5. Never touch productive data manually, unless it is during a down-time and you have met the requirements for 1. and 2. and 3.

Welcome to DBA.SE. Sorry to hear you're having a bad time.

Handling Your Current Situation

If FULL Recovery model is enabled for this database do the following:

1. Stop all transactions/connections to the database. NOW !!
2. Perform a Transaction Log Backup (TLOG backup).
     This step will only be required if the database has previously been backed up with a FULL backup
3. Perform a Full Backup.
4. Perform a Transaction Log Backup (TLOG backup).
5. Restore database to point-in-time on a different database server using the initial FULL backup (before step 1.) and TLOG backup from the second step. The time should be before the accident happened.
6. Search for the modified data.
7. Extract data.
8. Import data into production server after confirming it is correct.
9. Bring production back online.

If you didn't have the database in FULL recovery model, then changing it now will have no impact. You won't be able to rescue the data, because it probably has already been committed to the database and is no longer available in the TLOG file. If no initial backup has been performed, then these steps won't work.

Cleaning Up

1. Talk to management about what happened.
2. Implement a Change Management process.
3. Implement a solid backup procedure for your database systems.

Junior DBA Tips

Here a couple of basic tips:

1. Ensure you have a backup, before you modify data.
2. If the data is important/productive, ensure you have FULL recovery model enabled and Transaction Log backup is being performed.
3. Only change data in a productive environment after management has told you to do so and if you have an official Change Request that has been signed off.
4. Never touch productive data manually, unless it is during a down-time and you have met the requirements for 1. and 2. and 3.

Welcome to DBA.SE. Sorry to hear you're having a bad time.

Handling Your Current Situation

If FULL Recovery model is enabled for this database do the following:

1. Stop all transactions/connections to the database. NOW !!
2. Perform a Transaction Log Backup (TLOG backup) with the option WITH ... NO_TRUNCATE .... This ensure the data isn't deleted from the TLOG. This step will only work if the database has previously been backed up with a FULL backup
3. Perform a Full Backup.
4. Perform a Transaction Log Backup (TLOG backup).
5. Restore database to point-in-time on a different database server using the initial FULL backup (before step 1.) and TLOG backup from the second step. The time should be before the accident happened.
6. Search for the modified data.
7. Extract data.
8. Import data into production server after confirming it is correct.
9. Bring production back online.

If you didn't have the database in FULL recovery model, then changing it now will have no impact. You won't be able to rescue the data, because it probably has already been committed to the database and is no longer available in the TLOG file. If no initial FULL backup has been performed, then these steps won't work.

Cleaning Up

1. Talk to management about what happened.
2. Implement a Change Management process.
3. Implement a solid backup procedure for your database systems.

Junior DBA Tips

Here a couple of basic tips:

1. Ensure you have a backup, before you modify data.
2. If the data is important/productive, ensure you have FULL recovery model enabled and Transaction Log backup is being performed.
3. Only change data in a productive environment after management has told you to do so and if you have an official Change Request that has been signed off.
4. Never touch productive data manually, unless it is during a down-time and you have met the requirements for 1. and 2. and 3.