Database Weekly is the seven-day roundup from SQLServerCentral. We scour the Internet with a fine-toothed set of queries to compile the most informative weekly newsletter about SQL Server. Over 670,000 SQL Server professionals rely on it to kick-start their week.
Sign up to our newsletter now, to keep up to date with all the latest news.
Latest Database Weekly Newsletter Articles
Dear SQL DBA – Bleeding In Edgeville
Kendra answers a question about early adoption of SQL Server, discusses why testing in production isn’t necessarily crazy, and recommends how to handle requests to upgrade your SQL Server to use new features.
How to version a SQL Server Master Data Services model
In SQL Server Master Data Services all the entities are organized in a model. Once a model is ready to be released to subscribers, it should be frozen and marked as ready for subscribers. Until a model is marked as ready, a model is typically deemed as work in progress. In this article, Siddarth Mehta covers the standard process that's required to release a completed version of the model to subscribers.
How Oracle made its case against Google, in pictures
Oracle's lawyers have made their final pitch to paint Google as a copyright outlaw, and the decision is now up to a 10-person jury. Joe Mullin gives some more details on the case and presents some of the slides used in the closing statement of Oracle attorney Peter Bicks.
Why DBAs Need to Know about Kerberos
Though most DBAs don’t have the permissions to change the settings in Active Directory (AD) that affect Kerberos, it's still a good idea to understand Kerberos authentication so that you can help troubleshoot issues that come up. Kathi Kellenberger demonstrates how to see the settings, and what happens when you change the service account.
Database Restore Fails with Msg 3154
Have you ever tried to restore over an existing database only to receive an Msg 3154 error message? You 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, Patrick Keisler explains.