Skip to main content

In the works…

Speaker abstracts I've submitted...

SQL Saturday #40 in Miramar, FL.

Automating ID Administration with PowerShell and SQLPSX

I will demonstrate how I automated ID provisioning using PowerShell, SQLPSX, and my company's standard job scheduler.

Database Hardening via PowerShell

I will demonstrate how I use PowerShell to handle the issues encountered in a Fortune 50 corporate environment that has over 500 database servers and 3600 databases.

Why DBAs Should Learn PowerShell

I will detail my reasoning why a DBA would benefit from learning PowerShell.

A DBA can use PowerShell in conjunction with SQL, WMI, and SMO to automate repetitive tasks and better manage their workload.

The bonus for attending SQL Saturday #40, meeting Brent Ozar and Tim Ford in person.

SQL PASS Summit 2010

Why DBAs Should Learn PowerShell

Described above

Automating SQL Server Login Administration and Compliance Audits with PowerShell

Are your internal auditors asking that the administration of SQL Server logins be handled by a third party other than the DBAs? Is your Compliance and Audit departments asking you to determine if password policies are being enforced, who are sysadmins on your servers, who owns databases? If so, come to this session to learn how to complete these tasks quickly and efficiently using PowerShell and SQL PowerShell Extensions (SQLPSX). This automation is capable of adding or dropping logins and adding or dropping members in database or server roles on any server. Also, I will demonstrate how to automate compliance reporting via PowerShell and SMO to report on the usage of password complexity/expiration policies, database owner, sysadmin role members, and other security related information defined in the SMO object model.

Labels:

Comments

Post a Comment

Popular posts from this blog

Modifying Endpoint URLs on Availability Group Replicas

I recently had to modify the Endpoint URLs on our SQL Server Availability Group replicas.  The reason for this blog post is that I could not answer the following questions: Do I need to suspend data movement prior to making this change?  Would this change require a restart of the database instance? I spent enough time searching on my own to no avail that I tossed the question to the #sqlhelp hashtag on Twitter and Slack but didn't get an answer prior to executing the change request. After reading the relevant documentation, I think it's probably a good idea to suspend data movement for this change. The T-SQL is straightforward.  USE MASTER GO ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-1' WITH (ENDPOINT_URL = 'TCP://10.10.10.1:5022'); ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-2' WITH (ENDPOINT_URL = 'TCP://10.10.10.2:5022'); ALTER AVAILABILITY GROUP [AG2]  MODIFY REPLICA ON 'SQL2012-1
Post a Comment
Read more

Set Azure App Service Platform Configuration to 64 bit.

If you need to update several Azure App Services' Configuration to change the Platform setting from 32 bit to 64 bit under Configuration | General settings, this script will save you about six clicks per service and you won't forget to press the SAVE button. Ask me I know. 🙄 Login-AzureRmAccount Set-AzureRmContext  -SubscriptionName  "Your Subscription" $ResourceGroupName  =  'RG1' ,  'RG2', 'RG3' foreach  ( $g   in   $ResourceGroupName ) {       # Set PROD slot to use 64 bit Platform Setting      Get-AzureRmWebApp  -ResourceGroupName  $g  | Select Name |  %  {  Set-AzureRmWebApp  -ResourceGroupName  $g  -Name  $_ .Name  -Use32BitWorkerProcess  $false  }       # Set staging slot to use 64 bit Platform setting      Get-AzureRmWebApp  -ResourceGroupName  $g  | Select Name |  %  {  Set-AzureRmWebAppSlot  -ResourceGroupName  $g  -Name  $_ .Name  -Slot  "staging"  -Use32BitWorkerProcess  $false  }  }
Post a Comment
Read more

PowerShell: Quick SQL Server Version Check

I have to keep track of our SQL Server version inventory.  The goal is to reduce the SQL Server 2000 population as fast as possible. The following PowerShell script will produce a csv file containing the database server name and the version of SQL Server it's running. 1: ## Get SQL Version installed on multiple servers ## 2: ## ./sqlver.ps1 3: $start = get-date 4: write-host "Start: " $start 5:   6: [reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | out-null 7:   8: $FilePath = "C:\Output" 9: $OutFile = Join-Path -path $FilePath -childPath ("SQLVersions_" + (get-date).toString('yyyyMMdd_hhmmtt') + ".log") 10:   11: # Version inventory 12: @(foreach ($svr in get-content "C:\Input\AllLOBServers.txt") 13: { 14: $s = New-Object "Microsoft.SqlServer.Management.Smo.Server" $svr 15: $s | select Name, Version 16:   17: }) | export-csv -noType $OutFile 18:   1
1 comment
Read more