As I understand it, when you define a column on a table you define its precision. This precision takes 1 byte and is stored at the column level. If you use a precision of 5 or more, then a DateTime2 column will take 8 bytes per row. (The precision is not stored at the row level.)
Trying to use sp_stop_job to stop a simple job that inserts data on a table when 100 rows were inserted I got confused to see the table end up with more than 100 rows every time.
Under the Remarks section of the sp_stop_job doc it says:
I have the following query:
I’m trying to understand some execution plan caching metadata on a SQL Server 2016 SP3 system, and I can’t reconcile what I’m seeing with the docs.
If I upgrade a SQL server 2016 STD to ENTERPRISE and that server has the following services installed: SSIS and SSRS
can I just upgrade the version of the SQL and it will automatically upgrade the SSIS and SSRS on that server or do I need to take additional steps?
The following code creates a user that is able to restore a database:
I’m having trouble with deadlocks in a stored procedure.
One of the best protections against ransomware is to back up all of your database files to a completely separate system. Which we have done.
I have been doing some testing to try to better understand how SQL Server uses a histogram to estimate the number of rows that will match an equality predicate and also a < or > predicate
The Cost Threshold for Parallelism Setting on one of our servers is set at what is generally considered too low (15) and we are considering increasing to 50 in hope to reduce CPU as it is becoming high.