The release of SQL Server 2005 is a few months away and there are many people that are excited and looking forward to moving the new release into production. But what percentage of people are really looking to adopt the new platform soon? Edgewood Solutions has put together a survey to see. Enter and you could win a prize.
The amazing 4S sale! Our space constraints are your gains as we've put a bunch of books on sale. Check them out and save.
We recently published an article about logic in the database about how you might structure the TSQL code in your SQL Server and decide what goes inside the database. New author Mike Dillon brings us a response to that article and some ideas about how you might make those decisions.
SQL Server 2000 replication is the easiest so far to setup and work with. However there are some areas that you can get yourself into trouble with if you are not careful. New author Chris Rock brings us a few lessons learned in getting replication working with a remote office.
In this article, we are continuing coverage of Foreach Loop container functionality, by discussing different types of loop enumerators. So far, we have presented methods for working with files in a folder as well as records in a recordset (using Foreach File and Foreach ADO enumerators, respectively). Our next enumerator is based on the SQL Server Management Objects technology (hence it is referred to as the SMO enumerator), which is the SQL Server 2005, .NET-based management framework providing replacement for COM-based DMO (Distributed Management Objects) that served an equivalent role in earlier versions of SQL Server.
Reporting Services exposes web methods via XML web services to facilitate cross platform reports management and delivery. It's a simple SOAP based API makes it very easy to add full functionality of reporting services in your application. It provides a set of rendering and viewing functions as well as complete set of management routines. Reporting services web service is the one stop shop for subscription, management, publishing, scheduling and rendering reports.
We've spent quite some time investigating career issues for SQL Server DBAs lately. I've received quite a few emails from friends on their adventures in interviewing and now Sean McCown shares an experience he had interviewing a few prospective DBAs.
If you run PowerChute 6.x on any of your servers, be very careful of patching and rebooting them. You might end up with more downtime and problems than you expected.
A look at Parameterized reports, stored procedures to retrieve data and the Report Viewer.
If you are near the Jacksonville, FL area on Saturday, August 27th, check out this code camp with our own Brian Knight. Get the chance to learn some great development from Brian and a few other experts.
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