Log Deadlock
Alert Log
Alert Log
Getting this error during updating a large number of records to a large table. Solutions Put the database recovery mode from “Full” to “Simple” to avoid generating transaction logs in the Full recovery mode. Update in batches. Update multiple columns at a time.
To import/export between Staging and Production server, use the SQL Server Import and Export Wizard Tool. Use “SQL Server Native client 11.0” Use query to import data to a temporary table and then insert into the destination table from the temporary table. 30 million records = 10 minutes to import data from source table to... » read more
Symptoms When you use SSMS to run an SQL query that returns a large amount of data, you receive an error message that resembles the following: An error occurred while executing batch. Error message is: Exception of type ‘System.OutOfMemoryException’ was thrown Cause This issue occurs because SSMS has insufficient memory to allocate for large results.... » read more
Reason for converting a foreign key to a check constraint After partitional a table where the primary key was modified. If an additional column was added to the primary key, all the foreign key reference will now error out. You can either drop the foreign key or create a CHECK constraint insteac. If the table... » read more
Insert the content of files into a database table.
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