A Brief History of SQL
Frank has been part of our community for a while now, posting more than 1000 times (wow!) in our discussion area. He's decided to contribute more of his time by putting together an article that discusses how SQL has evolved.
Frank has been part of our community for a while now, posting more than 1000 times (wow!) in our discussion area. He's decided to contribute more of his time by putting together an article that discusses how SQL has evolved.
DTS logging is a pretty handy feature - if you've got it enabled. Got lots of packages and want to turn it on for all of them? Thats a lot of point and click using EM, but with the code Haidong has put together, it's a snap. Other possibilities to this code as well. After all, it uses a DTS package to modify other DTS packages.
Where should SQL Server go in the future? Steve Jones continues to explore his wish list for future versions of SQL Server. This article looks at an area where much improvement is needed: the index tuning wizard.
Jon has been off in the land of C# and web apps for a while, but a recent project has him investigating OLAP and then coming up with a custom solution that met his needs. Jon helped us get this site off the ground, good to have him back for a guest appearance!
Troubleshooting performance problems takes a lot of time and work. This article outlines the process the author uses - pretty interesting.
This month Robert covers the process he uses for developing stored procedures. In many ways it reflects how software is developed, but it does have it's minor differences. This is a high level process discussion, not a line by line example of the entire process - by design of course.
Where should SQL Server go in the future? What enhancements are needed? Steve Jones takes a break from his wishes to include some feedback from users who have some wishes of their own. Read about what real users of SQL Server would like to see included in future versions.
Stateless programming can be tricky... In case you ever need to return a specified subset of a query without first returning the entire recordset, here's a method.
The second article in a 3 part series that presents another VBScript class file that creates a class that can be used to display the backup information from a SQL server's maintanence plans.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
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....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
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