Hemanth is a SQL*Server DBA and a PowerShell enthusiast who loves to keep looking for new things to tinker around with. He maintains that he can write poetry. He blogs at http://sqlchow.wordpress.com and you can follow him on Twitter: @sqlchow
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. In earlier tips, we looked at how to add, read and update the extended properties of a SQL database.
Read More
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. In an earlier tip, we saw how we can read extended properties to a database.
Read More
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. Extended properties are an useful but, under utilized feature in SQL server. In an earlier tip, we saw that you can add extended properties to databases and other objects.
Read More
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. You might have seen several articles on the web discussing about the SQL database extended properties from a self-documentation point of view.
Read More
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. Sometimes we need to know if a particular DB is available on a given instance before going ahead and making any configuration changes.
Read More
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. In a previous tip, we checked out how to get the names of all databases to which a login is mapped and the username for that login in each database.
Read More
Hemanth C DamecharlaNote: This tip requires PowerShell 2.0 or above. One of the projects on which I work requires a validation step after each deployment.
Read More