If you’re interested in a free day of PowerShell training, there are numerous sessions on different topics in the dedicated PowerShell track at SQL Saturday #628in Baton Rouge, Louisiana this Saturday, July 29th. I’ll be presenting a session on how to “Automate Operational Readiness and Validation Testing of SQL Server with PowerShell and Pester”. ](/images/2017/07/sqlsatbr2017.jpg)Here’s a little information about what you can expect from my session: Automate Operational Readiness and Validation Testing of SQL Server with PowerShell and Pester How do you know whether or not all of the SQL Servers in your environment are configured based on your organizations standards?
Microsoft SQL Server
I’ll be presenting a webinar on how to “Automate Operational Readiness and Validation Testing of SQL Server with PowerShell and Pester” for the PowerShell Virtual Chapter of SQL PASSon Wednesday, November 16th at 11am CST. ](/images/2016/11/psvcsqlpass111616.pngpsvcsqlpass111616)How do you know whether or not all of the SQL Servers in your environment are configured based on your organizations standards? How do you know whether or not they are all operating properly when maintenance is performed on the systems in your environment?
I’ve used PowerShell to administer and manage Microsoft SQL Server for quite some time although I haven’t blogged much about it. I thought I would take the time to write a series of blog articles about using PowerShell to administer and manage Microsoft SQL Server to help others who are just getting started and to clear up some common misconceptions. Just to give you a little background information about myself, I’ve worked (professionally) in a data-center environment administering and managing every version of SQL Server since 6.
I need a few Active Directory users created in my mikefrobbins.com test environment so I thought why come up with fake information when I could use information that I already have in a SQL Server database? The Employees table in the Northwind database looks like an easy enough candidate since all the data I need is in one table. This is about the concept and not about seeing how complicated I can make this process.
This blog article is a scenario that I sent a coworker a while back about recovering a SQL Server database up to the point in time where a catastrophic hard disk drive failure occurs for the hard drive containing a SQL Server database. The transaction log for this database is on a separate physical disk and is still accessible. I added the Northwind database to SQL Express on my machine, changed the recovery model to full, and then backed up the database and transaction log: