Amy

[Amy @MSSQLServerDBA]

@SQLGrease I know it’s single threaded, that’s why I mentioned the edition, overall CPU stays low. I’ve enabled page compression many times and I’ve always seen CPU drop, I’ve never seen the negligible rise reported in the documentation. Have you?

[Amy @MSSQLServerDBA]

I just enabled page compression for all of the databases on a SQL 2022 SE server and DBCC CHECKDB has gone from 2 hours to 5 hours. I've never noticed this before. Has anyone else? Old slow spinning disks #sqlhelp

[Amy @MSSQLServerDBA]

@SQLRunr I experienced something similar last year when developers were changing their initial passwords for SQL logins. They had to use Azure Data Studio instead.

[Amy @MSSQLServerDBA]

@RochieWBZ @RedSox @wbz Very sad but the “kids” are adults.

[Amy @MSSQLServerDBA]

Actually it works in ADS when set to True as well but not in SSMS.

[Amy @MSSQLServerDBA]

When creating a new SQL Login with MUST_CHANGE, the user can connect with SSMS if Trust server certificate is true but the Change Password popup doesn't seem to honor that because the users are getting an error. RDS SQL 2022 #sqlhelp @erinstellato

[Amy @MSSQLServerDBA]

I was able to get it to work only in ADS by setting Encrypt to Optional.

[Amy @MSSQLServerDBA]

@SqlWorldWide @kewlsmoove A gMSA is different. It’s a computer account not a user account. I think your image is of permissions on the path. Either Everyone or Authenticated users must be given permissions on the share which looks like this image. Also gMSAs do not sync to Azure.

[Amy @MSSQLServerDBA]

@stridergdm Did you ever figure this out? I’ve seen that happen when there wasn’t enough space on the disk for the snapshot. Paul Randal has an old post called CheckDB from every angle that helped me a lot. Also the first release or CU of SQL 2019 broke CheckDB so make sure you’re patched.

[Amy @MSSQLServerDBA]

@codegumbo I know this is late but next time just pay here. You don’t need that dumb account.
https://t.co/OCpjT7DzVZ

[Amy @MSSQLServerDBA]

@MatthewCargile @leemarkum They can view it first like this:
$result = Invoke-Dbaquery
$result | Out-GridView
If they like it then:
$result | Export-Csv

[Amy @MSSQLServerDBA]

@MarlonRibunal 1 P30 will give you 5000 IOPs and 200 throughput so 8x5000=40000 and 8x200=1600.

[Amy @MSSQLServerDBA]

@MarlonRibunal Use storage spaces to stripe. It’s a math problem. In Azure 8 P30 disks striped together will give you 8TB of space/40000 IOPs/1600 throughput for $983 per month and 1 P60 disk will give you 8TB of space/16,000 IOPs/500 throughput for $860 per month.

[Amy @MSSQLServerDBA]

@erikdarlingdata @JonathanGennick Mine uses the toilet.

[Amy @MSSQLServerDBA]

@furt1v3ly @erikdarlingdata Glad you found it!

[Amy @MSSQLServerDBA]

@erikdarlingdata @furt1v3ly lol I wasn’t sure if y’all wanted it or not.

[Amy @MSSQLServerDBA]

@furt1v3ly @erikdarlingdata Andy Yun just blogged about a way to get it to integrate with SSMS 19.

[Amy @MSSQLServerDBA]

@BuckWoodyMSFT @mwdarab @DesertDBA And here I was thinking that word was just a buckwoodyism.

[Amy @MSSQLServerDBA]

@SqlWorldWide @psdbatools Yes - like this
Get-DbaDbStoredProcedure -SqlInstance SQL1 -Database DB1 -Name SP1 | New-DbaDbTransfer -SqlInstance SQL1 -DestinationSqlInstance SQL2 -Database DB1 -DestinationDatabase DB1 | Invoke-DbaDbTransfer

[Amy @MSSQLServerDBA]

@SqlWorldWide @psdbatools Use Start-DbaMigration and exclude the objects you don’t want to copy to the other server or use any of the copy commands under the migration category like Copy-DbaDbMail or Copy-DbaLinkedServer.