Additional Articles

All authors

Technical Article

Building Reports Based On Stored Procedures

Usually developers like having full control over their reports but what happens if you have someone designated to build reports who does not quite know the backend schema. A good way to separate the building of the data for the report and the report design could be stored procedures. Now I consume stored procedures using Oracle which is not much different consuming stored procedures with SQL Server, however building the procedures is much different between the two. Even though I mention and show examples of stored procedures this is not an article for building them, just a guide for consuming a stored procedure within a Reporting Services Report.

2005-11-22

3,591 reads

Technical Article

SQL Server 2005 Learning Guide

It's been five years since Microsoft released a new DBMS, but both experts and users agree that this one was worth the wait. SQL Server 2005's enhancements and new features have made the system a much more attractive attractive option to both large and small shops. Nonetheless, upgrading to SQL Server 2005 is a serious undertaking, requiring extensive training, planning and testing. In this Learning Guide, you will find news, technical tips and expert advice to help address your questions and concerns regarding SQL Server 2005 and put you on the road to a successful upgrade.

2005-11-16

5,506 reads

External Article

Dynamic Management Views

The dynamic management views (DMVs) in SQL Server 2005 are designed to give you a window into what's going on inside SQL Server. They can provide information on what's currently happening inside the server as well as the objects it's storing. They are designed to be used instead of system tables and the various functions provided in SQL Server 2000. This article provides an introduction to DMVs and covers a few of the basic views and functions.

2005-11-15

2,315 reads

External Article

MDX Essentials : Set Functions: The DRILLDOWNMEMBER() Function

In this article, we will begin an extended examination of the MDX surrounding drilling up and down within our Analysis Services cubes. Comprising an analytical technique by which an information consumer can maneuver between summarized ("drilling up") and detailed ("drilling down") levels of data, drilling up or down occurs along the lines of drilling paths that are defined within the physical structures of our cubes. Often specified by the cube's dimensional hierarchies, these paths can also be based upon alternative relationships that exist within or between dimensions.

2005-11-11

2,036 reads

External Article

Bogus Resumes and Unblushing Lies

Simple Talk's newest commentator, Phil Factor, reveals the dark side of hiring database specialists: "Soon after he had been shown his desk in our crowded, open-plan IT office, he began laughing out loud, sporadically and inappropriately, while reviewing code. It wasn't my code, so I didn't mind."

2005-11-10

4,525 reads

All authors

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