Note: Run the following on the source server and run the output on the destination server. Run after database has been restored. Apply to restored databases from PROD backup. Apply to AlwaysOn databases.
Moving data from Transaction database to Archive/Reporting database. After the records has been moved, delete the records to avoid duplicates. Note: If your database is involved in AlwaysOn or in Full Recovery mode, make sure you backup the database and log file to clear out the log files on the database before preceding. After you... » read more
To create a job category In Object Explorer, click the plus sign to expand the server where you want to create a job category. Click the plus sign to expand SQL Server Agent. Right-click the Jobs folder and select Manage Job Categories. In the Manage Job Categoriesserver_name dialog box, click Add.
NOT FOR REPLICATION indicates that when a record is replicated to this table, any value that is inserted into the identity column via the replication agent keeps it’s original value from the source system, but any records added locally still increment the identity value. All about “Not for Replication” “Not for Replication” is a property... » read more
Specifies whether SQL Server automatically rolls back the current transaction when a Transact-SQL statement raises a run-time error. The THROW statement honors SET XACT_ABORT. RAISERROR does not. New applications should use THROW instead of RAISERROR. When SET XACT_ABORT is ON, if a Transact-SQL statement raises a run-time error, the entire transaction is terminated and rolled... » read more
Transactions are intended to run completely or not at all. The only way to complete a transaction is to commit, any other way will result in a rollback. Therefore, if you begin and then not commit, it will be rolled back on connection close (as the transaction was broken off without marking as complete). As... » read more