Skip to main content

SQL Saturday #40 South Florida. Here I come!

Need a few reasons to come to this event?

It’s FREE

You’ll learn from a master. A Microsoft Certified Master. 

Brent Ozar will do two sessions. His first at 0945 conflicts with my first session.  I hope they gave me a small room for my session.  I predict most attendees will be in his session, not mine. He’s guaranteed to keep you awake. No cover charge at the door. Costumes optional.

I’ll get to see Brent’s second session on Disaster Recovery in Hurricane Alley.                    

College football hasn’t started.  So, you won’t miss UF, UCF, USF, FSU or The U.

It’s FREE.

Another Microsoft MVP, Tim Ford, will be there to talk about indexes, DMVs, and mistakes to avoid. BTW, great post from him recently on how being involved in the SQL community allowed him to land softly at a new job when he wasn’t looking.

More MVPs, Twitterati and local experts galore. 

Did I say the whole thing is FREE!

I’m on the schedule for two sessions first thing in the morning:

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.

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.

I don’t think there is a better training or networking value than attending a SQL Saturday.

See you on Saturday bright and early.

Comments

  1. Hey Now Ronald,

    This event sure will be great!

    Thx 4 the info,
    Catto

    ReplyDelete
  2. Hahaha, nice. You give me too much credit though - it's really funny how the attendance thing works. The people who know me through Twitter/blogs/etc also know you, because we're all a pretty tight community, but we're the people speaking! The attendees don't usually follow blogs or Twitter, so they just pick the topic that interests 'em most. It's funny how it works.

    ReplyDelete

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

PASS Summit 2012 - Gone to the mountain and returned wiser

http://t.co/pmhsJ3rr I began my conference schedule by attending Allen White's pre-con "Automating SQL Server with PowerShell". Allen starts by telling everyone in attendance “We all can learn something from each other.  We all know something that someone else doesn't.” I thought this was a great intro and inspiration to the attendees to participate in the PASS Community. Later in the day while answering a question, Allen tells us he is not a PowerShell expert.  Which kind of surprises me.  He says he’s just figured out how to use PowerShell with SQL Server. I think he is being a bit too humble.   Afterwards, I talk to Allen about a script I’m working on and he points me in a direction that hopefully will help me finish it. All in all, it was e xcellent day of training on using PowerShell with SQL Server. As the main conference began, I tweeted about how tight the seating was in some of the rooms on the first day of the main conference.   After the Sum

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