Before you update or delete data from a table, it is always a good idea to make a backup just in case. Using the INTO clause in your sql statement, allows you to do this.
Quick, you need to get all of the code for all of your stored procedures in your database! All you need to do is go to your source control system and get them right? What do you mean you do not have them, well here is how to extract them from the database so you can create a source control baseline.
Last week we made a backup of our Oracle database using the RMAN tool. Today, I am going to show you how to be a hero and restore your database. This will be another long post, but saving your companies data is worth it.
Some workplaces have multiple database platforms that you will be responsible for. The main thing a DBA is responsible for is being able to recover the database in case of a disaster. Below is an easy way how to backup an Oracle database using RMAN. Is it the only way to do this? Of course not, there a literally dozens of ways depending on how complicated your environment is, but it is a legitimate way to create a backup and it will save you. In the next posting, I will show you how to restore the database onto a new server.
If you have ever tried to run or create a SSIS extract package that exports to Excel, you may run into the error below:
[SSIS.Pipeline] Error: Excel Destination failed validation and returned error code 0xC020801C.
Have you ever deleted a row of data and then needed to put it back due to being told it was the wrong row, but the table had an identity column and will not let you insert the row back? Using the Set Identity_Insert command, you can insert into the table.
Do you have files stored in your SQL Server database and need to see what they are. Here is a way using my favorite add-in SSMSBoost.