Thank you for the article.  I feel aiming for the highest data quality somehow got lost by developers and staff in general.  Having an area code of VARCHAR(3) and phone...

The backup is run by the database engine service account.

Run the below query to find that service_account:

select *

from sys.dm_server_services

Try this query:

select *

from sys.dm_server_services

You want to make sure the service account associated with the database engine has the permission to write to the backup folder as that is what...

In working for the State of Wisconsin I do see any advantage of the cloud.  For starters we have really good data centers in Madison and Milwaukee that meet or...

My recommendation would be SQL Server 2019 at this point.  It is at CU16 at present and this is important.  For more than 8 years it has been my practice...

You are fine with SQL Server 2017 -- https://docs.microsoft.com/en-us/lifecycle/products/sql-server-2017.  October 2022 is end of mainstream support.  Extended Support is October 12, 2027.

https://www.brentozar.com/archive/2019/01/which-version-of-sql-server-should-you-use/ is worth reading on...

I would run the query with 'SET Statistics IO ON' and run the query with the actual execution plan.  Chances are the execution plan will give you a missing index...

I got the 50000 error also on a SQL Agent Job.  In my case Step 2 | Advanced |  On success action drop down was 'Quit the job reporting failure'. ...

My largest database is 1.6 TB and it takes 84 minutes for a full database backup.

The database is a content management database, Columbiasoft Document Locator, so the majority...

It has now been a good 2 weeks of modified cursor and my full and differiential backups are now backing up all user databases under my SQL Server Instance.  In...

Thank you munzelj for your post.

I am using a store procedure to backup my databases and once in...

Thank you. I copied and pasted the above code and it worked great!

When I tried this code I got a syntax error on the A - B as TEST. Am I doing something wrong?

In looking at my fulltext index within SSMS, the population status is now, 10/13/2014, reading Idle. After my upgrade and when I started the fulltext index rebuild as suggested...