SQL Server 2012 delivers enhancements to the Resource Governor that reflect a growing need for centrally managed database services to provide multitenancy to customers who require isolated workloads. This document describes the enhancements and why they were added. It includes a self-contained walk through that you can try in order to gain familiarity with the new features.
Things on the ranch inspire Steve Jones in the rest of his life. He's one you might not have thought about. Today's editorial was originally published on Nov 3, 2008. It is being re-run as Steve is out of town.
Working with SSAS time related accounting functions can be tricky. SQL Server 2012 now offers Lag and Lead functions. Are these functions available in SSAS? What other related functions are available?
Auditing, conflict resolution, tamper & concurrency protection are some of the most common requirements for any enterprise system – this 2-part series presents an in-depth look at the various change detection mechanisms available within SQL Server.
It is late evening. Something is wrong with a database. You narrow down the possibilities, getting more frustrated and puzzled. Stay calm. Check the inputs systematically. No! The data going into that table is right, but when you then read it in the table, it's wrong. Why did I stop believing in the supernatural? Then it hits you. Every time it comes as a surprise. They're using triggers. (This editorial was originally published on Nov 10, 2008)
SQL Server Integration Services (SSIS) can be used effectively as a tool for moving data to and from Windows Azure SQL Database, as part of the total extract, transform, and load (ETL) solution and as part of the data movement solution. SSIS can be used effectively to move data between sources and destinations in the cloud, and in a hybrid scenario between the cloud and on-premise. This paper outlines best practices for using SSIS for cloud sources and destinations and for project planning for SSIS projects to be used with Azure or hybrid data moves, and gives an example of maximizing performance on a hybrid move by scaling out the data movement.
The big data revolution seems to have failed to materialise, and for good reason - it's really difficult.
Corrupt SQL Server databases are the worst nightmare of any SQL Server professional. In any environment, from small business to enterprise, the compromise of integrity and availability of the data can constitute a business emergency. This is especially the case in those organizations reliant on an OLTP data model, for a high-volume website. SQL Server database corruption and disruption of the transaction processing system can cause business repercussions such as large financial losses, a drop in reputation or customer retention, or contractual SLA problems with the service provider, if not managed in-house.
The Bay area gets another SQL Saturday this weekend, on Feb 23, 2013. Come have a free day of SQL Server training.
Don’t miss the Bay Area’s largest SQL Server event of the year! You can choose from sessions on SQL Server 2012, DBA, Development, Business Intelligence, and Big Data.
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers