start by looking here

https://blogs.msdn.microsoft.com/karthick_pk/2011/02/01/sql-agent-maxworkerthreads-and-agent-subsystem/

way back in sql 2000 there were registry settings for the max number of concurrent threads sql agent could run. these were broken down into subcategories... replication, job agent, maint...

you might have saved me a lot of time with this script! 🙂

I "inherited" 7500 databases - unfortunately one of the server monkeys built a server with a default collation...

this is a table that is used by many processes, dropping the indexes and constraints would affect customer usage.

we're standardising names as we go. but as I said, the script works fine if I just run CMD and copy the contents into the window.. the issue is "permission...

depending on what you want to achieve then you may want to add a hierarchyid column to your table and then use the .GetDescendant / .GetAncestor functions rather than using...

I think what a lot of people have missed here is that sometimes you won't be the only person to touch that code.

you may write exceptional code the first time...

as a DBA who specialises in helping test professionals I see unit tests as a valuable cost saving exercise for the business

if you look at the ISTQB data for...

the only issue I've found with this is that the object_id of the tables will change (same as if you drop proc rather than alter proc)

if you rely on object_id...

it is transactional publication, but multiple publishers pushing to a single subscriber database (not a single table). no merge replication at all.

i'm not interested in replication topology or which initialization...

microsoft documentation states that it is linear fill for log files ....

we can't do initialise from backup as there are multiple publications replicating to the subscriber database - restoring from...

I'm sorry , but I can't even begin to describe how much I disagree with this article

my main gripe is the fact that the author has not realised that a...

that 100% categorically does not give you internal fragmentation, external fragmentation or any other kind of fragmentation.....

While this is a great innovation, i can see it potentially causing more issues than it actually fixes...

if you've ever tried using an XL amazon instance to run a DB...

is auto shrink turned on ? is there a dbcc shrinkfile/shrinkdb command being issues?