Applied it to a few Non Prod Environments over the weekend. Testing will be going on this week. Patch applied without incident.

The query was being used in two different sql servers. One of the tables had the XID column as CHAR the other VARCHAR. It should have had the query...

We figured out the issue and fixed it. Thanks for your response.

It really is a 'it depends'. If the database starts at, say 100mb, but as they load data into it it turns into 5 TB then a 100MB autogrow...

It would help to know what query you are running. Is database2 on the same SQL Server or a linked server to another server.

Have stats been updated on both...

It is getting quite confusing of what patches to apply to each different version and CU version of SQL Server. We have so many versions and at different releases...

The HR Derby was great. I really like the new format... and.. of course being a Red's fan loved seeing Todd Frazier win it. 😀

CPU was at 100% and memory was at 97% before you started replication... and you thought that turning on Replication wouldn't have bad effects? Yikes. You have a...

You best bet might be to build a new VM, install SQL Server and restore everything to the new SQL Server VM

You will have to script out all of your SQL Agent jobs. Also, if you have any Linked servers you will need to recreate those as well.

I would find out which queries perform poorly, look at their execution plans when it runs good and when it runs poorly. If no other tuning indexes can help...

Am I reading this correctly that you are concerned about 1/4th of a second runtime for a query? 1000 milliseconds is 1 second.

It could be a ton of things...

The more memory the better. However, it is a 'it depends'. If you have one very small database planned for this SQL Server 96gig of memory is WAY overkill...

To answer your question... I have AUTO STATS on, plus I generally update stats in a Maint plan job once a week. There are a few key tables/databases that...

I would simply rename the table.