Honestly the biggest gripe with Azure VMs (where we are now) is the lack of flexibility in drive sizing.  It's all multiples of 64, so 64 / 128 / 256...

I have the same things to deal with.  Getting more space requires divine intervention.  We started combatting this by creating a database named "MT" on the servers.  We size...

Honestly, two reasons:

1. We don't have the privileges in...

Two reason, both valid:

1. We don't have the level of access to do this (yeah, it's a weird hosting arrangement)

2. Larger disk = more $$$ = requires approval through our...

Well it's my own dang fault this happened...

The guy on our team responsible for managing our AVDs in Azure we (and the developers) connect to our servers from got an...

Would creating a small, empty database that you TDE-encrypt / decrypt, perhaps on a schedule be an option?  This would satisfy one of the reasons given in the MS Q&A...

--Double post--

• This reply was modified 8 months ago by jasona.work. Reason: double posted due to gateway timeout

The problem, ronaldkunenborg, though, is who decides?  Who decides Source A is reputable and Source B isn't for a given topic?  One person might consider anything coming from StackOverflow to...

One of the many reasons I don't trust the so-called "AIs."

There's one hosted by my employer and one of my co-workers asked it a relatively straight-forward question, "how many Federal...

From looking through the documentation on the site, there's no filtering at all for the invoke-dbaquery, it's just going to run the query you throw at it and spit out...

I'm thinking the best option, if it's an option, would be to specify the columns in the select query and just leave out the ID column.  Export-CV wouldn't see that...

• This reply was modified 8 months ago by jasona.work.

After reading Connie's comment, I believe we're going to hold off on even thinking about any upgrades until next year at the soonest.  The reason being, the applications our group...

Even more fun, every post has zero replies!

The bad part of me is whispering in my ear to try to nurse our SQL 2019 instances along until 5 years after the end of extended support...

So I can...

Anyone noticing a round of replies to posts that "feel" suspiciously like someone fed the OP's question into one of the chat-bot AIs and posted the "answer"?