If you dont know what the script does. Then dont run on live db server and live database.
First step setup a virtual or physical test db server.
You can easily setup one. If you are using virtual servers If not then you need a bit more time.
For safety you need a test server.
Backup of the live db and then Restore the backup in test server with the same name of live db.
Analysing of the scripts
You can use few methods to investigate the scripts.
- First Method:
Run Sql Server Profiler > New Trace > Run
This is a test server so we dont expect to be a noise of sql commands from other users and jobs.
Sql Profiler will show just your script runnings.
If you expect other query running from other sources then you need to filter the trace like in the following picture.
I suggest to use Sql Profiler for insulated test server with default config and filters but for production server you could need filters and common configs. You can set them with for events and columns.
You will see actual running portion of your script in profiler as in the following screen shot.
Run the first script and then save the Sql Profiler Trace to a Sql Table with File> Save As > Trace Table
Saved trace table will look like to the following picture.
You can copy TextData to a text or .sql file.
Then Compare, investigate the Trace Table Text data with your script.
Second Method : Add Print Statement lines into the scripts.
PRINT N'The running code line - command is 1000 - Select Customer ';
IF Condition
PRINT N'The running code line - command is 1000';
ELSE
PRINT N'The running code line - command is 1000';
GO
Third Method : Instead of using Print Statement Write a function to insert the running lines into a table.
Fourth Method : Make a stored procedure from a script that is you need to investigate. Then by using Visual Studio Data tools debug the procedure
