Simple problem: we had to replace the config files for an app that hits the database, pointing it at a CNAME.
However, the file could be in use because the app was running. And the app only loads the file on startup. So we came up with this, which worked quite well. Note that we use WMI (see my other posts on it!) to grab the application info then a WMI method to terminate the app.
Click through for the script.
I used to think that this would be a complex requirement, possibly requiring a
TRIGGERor two to check the inserted value against whatever is already there; but there is a way to have this functionality and have it the way that SQL Server normally would enforce a uniqueness on a column; by using a
In case you’re thinking…
“Oh, a unique index doesn’t check what’s already there, is that it?”
I’m afraid that’s not the case.
This is one of my favorite uses of filtered indexes: “limited” uniqueness. In other words, I’m okay with an unlimited number of NULL values but all non-NULL values need to be unique.
Chrissy LeMaire has written about the new SQL Agent cmdlets
Aaron Nelson has written about the new Get-SqlErrorLog cmdlet
Laerte Junior has written about Invoke-SQLCmd
All four of us will be presenting a webinar on the new CMDlets via thePowerShell Virtual Chapter Wed, Jul 06 2016 12:00 Eastern Daylight Time If you cant make it a recording will be made available on YouTube on the VC Channel https://sqlps.io/video
There are 17 new Always Encrypted cmdlets and 25 new cmdlets in total.