Additional Articles


External Article

SQL Server 2005 - SQL Server Integration Services - Part 6

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.

2005-08-22

2,338 reads

Technical Article

Business Intelligence with SQL Server Reporting Services - Part 3

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.

2005-08-19

2,418 reads

External Article

Database Geek of the Week - Shawn Wildermuth

Shawn Wildermuth is the “go-to guy” for information on ADO.NET. He is the author of Pragmatic ADO.NET: Data Access for the Internet World and numerous articles, is a Microsoft MVP, and works as an independent consultant in Atlanta.

Shawn’s web site, The ADO Guy, is a good resource for developers looking for answers to questions about ADO and ADO.NET. The site also lists interesting blogs, books and sites that are among Shawn’s favorites.

2005-08-11

1,821 reads

External Article

ADO.NET Data Sets

This article looks at how partial classes can be used to implement business logic into datasets so that they are more business aware and intelligent.

The dataset is an integral part of Microsoft’s new data access model ADO.NET. It introduces a simple offline method for retrieving and updating data. Before using the dataset, you should have an understanding of the Microsoft .NET platform and a basic understanding of the dataset model.

2005-08-05

3,652 reads

Technical Article

Michael Rys on XML in SQL Server 2005

Michael Rys is one of two program managers responsible for the XML features in SQL Server. He also represents Microsoft on the W3C XQuery Working Group, and on the ANSI working group for SQL. I asked him what is distinctive about the XML support in SQL Server 2005, as opposed to that found in rival database management systems. As Rys acknowledges, "all the three major vendors, Oracle, IBM and Microsoft, are moving towards second or third generation suppor

2005-08-04

1,979 reads

Blogs

Building the Team: Roles and Responsibilities in FinOps

By

In my experience, FinOps success has never been just about tools or dashboards. It...

Tooling for Success: The Best FinOps Tools and Technologies

By

As a DevOps person, I know that to make FinOps successful, you need more...

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

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)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

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)
GO
Today, 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 REPLACE
What happens?

See possible answers