2016

A Goal of Speaking at PASS Summit

Everyone has goals or at least they should have goals. As a young professional out of college, I had plenty of goals, but none of them involved SQL Server. I really had no idea of where I wanted my career to go other than working in IT. Finally in 2000, I stumbled upon an opportunity that started me down the career path of a DBA. It didn’t take long to realize I enjoy this type of work. Over the next decade, I learned a lot from my coworkers, training classes, and especially my mistakes. Yes, I really did drop the...

Continue reading...

SQLPSX is Finally Getting Updated

The most current code is now on Github, with the Codeplex version being depreciated. You can read all about the planned updates from Mike Shepard. The Future of SQLPSX https://powershellstation.com/2016/07/13/the-future-of-sqlpsx/ SQLPSX Update https://powershellstation.com/2016/07/31/sqlpsx-update/

Continue reading...

TSQL Tuesday #79 -SQL Server 2016 Launch Discovery Day (aka Hackathon)

The host for T-SQL Tuesday #79 is Michael J. Swart (b|t), and his topic of choice is to write about the new release of SQL Server 2016. This past weekend I attended the SQL Server 2016 Launch Discovery Day in Raleigh, NC. I have attended several SQL Server launch events over the years, but this one was quite different. While it wasn’t a real launch event, it was marketed as a hands-on event to learn about the newest release of SQL Server. The hands-on part for everyone to breakup into teams of five to solve a pre-determined problem. Basically, this was...

Continue reading...

Database Restore Fails with Msg 3154

Have you ever tried to restore over an existing database only to receive the following error message? Msg 3154, Level 16, State 4, Line 1 The backup set holds a backup of a database other than the existing ‘AdventureWorks2012’ database. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. We could easily avoid this error by using the WITH REPLACE option in the RESTORE DATABASE command, but we want to know why this error occurs and how SQL Server knows they are not from the same family. The answer is the database_guid. The database_guid is a...

Continue reading...