Here are a few pointers for this common problem. Chances are very high that your databases are in FULL recovery mode, but that you don't have log backups set...

I am bringing in some help on this one. I may be horribly wrong in what I've been saying.

Are you letting constraint names or similar be automatically generated? That could lead to the issue. Stuff like that is likely the cause.

I work for Redgate, so take what I say with a grain of salt...

You want to go and get a copy of Redgate SQL Monitor. You can check it out...

So, you should be able to merge changes from two different tables, just fine. Nothing SQL Source Control does this. It's all in the source control system. The issue is...

Yeah, hard coding isn't perfection, but, that's the situation. Work within it.

The negative is, that index probably won't be used for a lot of SELECT queries since it doesn't eliminate...

Yeah, it should work as described.

Ordering by a function is just going to kill you more and more as the data grows. Best suggestion I can make is to not do that. Nothing will make...

Nothing marks a table as being "used" by queries. You can look at sys.dm_db_index_usage_stats, assuming the table in question has indexes. That will tell you something of the access...

Create a file group in a different location and move those indexes to that file group.

Your best bet to see missed connections is setting up an Extended Event session and capturing the even connectivity_ring_buffer_recorded. That's the one mechanism I know that captures stuff like timeouts....

By default, neither. It supports both. Extended Events is first though. We have several metrics that are taking...

OOps. Sorry. And yeah, that's really odd.

Another one?

Test

Post 16 in test