In most organizations, the DBA team is seriously outnumbered by headstrong developers and clock driven managers, and "great" DBAs will often be outnumbered by...well...the not so great. In order to be heard in this environment, a DBA will not only need to be very skilled, but will also need a healthy dose of ego.
Although, generally speaking, source control is the truth, a database doesn't quite conform to the ideal because the target schema can, for valid reasons, contain other conflicting truths that can't easily be captured in source control. Dave Ballantyne explains the problems and suggests a solution.
Sept 15th, 2012 at the CAIT Campus of Washington University in St.Louis - 5 Jackson Avenue, Clayton, MO 63105
SQL Saturday #154 is the very first SQL Saturday event in the St.Louis area. It is a free one day event for SQL Server professionals and those wanting to learn about SQL Server. We are planning on a 4 track event with 200 attendees. We currently have several sessions aligned towards Database Administration, Application Development, Business Intelligence and professional Development Tracks. We also have several sessions focused on SQL Server 2012! Please visit our event website for more details and free registration.
Come visit Rhode Island and meet fellow SQL Server professionals from all over New England as SQL Saturday comes on Sept 15, 2012.
This editorial was originally published on Nov 19, 2007. It is being republished as Steve is on vacation. With the tremendous amount of digital storage that people can carry around these days, how do you balance the security risks.
Why does the transaction log fill up? There are a variety of reasons, and MVP Gail Shaw walks you through the various things to check.
SQL Server 2012 AlwaysOn Availability Groups provides a unified high availability and disaster recovery (HADR) solution that improves upon legacy functionality previously found across disparate features. Prior to SQL Server 2012, several customers used database mirroring to provide local high availability within a data center, and log shipping for disaster recovery across a remote data center. With SQL Server 2012, this common design pattern can be replaced with an architecture that uses availability groups for both high availability and disaster recovery. This paper details the key topology requirements of this specific design pattern, including quorum configuration considerations, steps required to build the environment, and a workflow that shows how to handle a disaster recovery event in the new topology.
An interesting method of preventing restaurant fraud and a poll for other ways to determine the accuracy of data. This editorial was originally published on Nov 2, 2007. It is being republished as Steve is on vacation.
I need to try and find all SQL Servers, not just the ones in my domain. We know there are a couple of appliances that are potentially running SQL Server and we want to see them, too. What can I use to do this?
The way you talk creates an impression at others. Steve Jones reminds us that we should be careful about using foul language.
By James Serra
Making Data AI-Ready, Part 3 (This is the final article in a three-part series...
By Steve Jones
I use ConEmu for my terminal interface. I’m still on Windows 10 at home,...
Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built...
I am not sure which is the best way to proceed. I have parent...
Comments posted to this topic are about the item Hyperscale Replicas III
Comments posted to this topic are about the item Development Is Fun
In an Azure SQL Database Hyperscale Edition, how many named replicas can be configured?
See possible answers