Loading XML Data into SQL Server (SQL Spackle)
Learn how to load data in an XML file into a table in SQL Server.
The Bicentennial
Tomorrow is the bicentennial SQL Saturday event. SQL Saturday #200 takes place in Philadelphia, and Steve Jones has some thoughts as he travels to the City of Brotherly Love.
Why is your ASP.NET application running slow?
Any queries run against SQL Server or Oracle databases are recorded, along with how many times those queries were run and how long they took. That information is shown alongside your .NET code, so you can quickly see why the code you wrote resulted in those queries being executed. This can be particularly powerful if you’re using ORMs like Entity Framework to access data, which tend to be an impenetrable black box where performance issues can arise, but where it’s difficult to understand why.
Show off your Solutions
We're looking for scripts that you use in your daily job to find, fix, and solve issues in your environment.
Super Fast Transactional Replication Repair
Your production SQL Server transactional replication just failed and the business impact is critical. How do you get replication restored in minutes?
The Speed of Azure
There isn't a lot of acceptance of Azure from DBAs. Steve Jones talks about some of the advantages of Azure and thinks that we should be working to ensure that our internal systems respond at the same speed as people can get from Azure.
Extending SQL Server DDL Triggers for More Functionality
In this tip Aaron Bertrand describes some of the ways in which you can extend the DDL trigger functionality.
Helping MS Help Us
The Microsoft Connect system allows many of us to submit feedback, but is Microsoft doing anything with it? Join us and place your vote on some items and try to influence Microsoft.
SQLServerCentral Runs sp_Blitz - Query Plans
The fifth installment of the sp_Blitz script being run on the SQLServerCentral database server.
Database Deployment: The Bits - Agent Jobs and Other Server Objects
Databases often need more than just the database objects to run. There may be certain server objects and components, and SQL Agent objects, that are required as well. For an automated deployment, these need to be identified and their build script placed in source control. They then need to be deployed via the pre, or post deployment script. Phil spells out how and why.
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers