Installing and Configuring SQL Server Reporting Services

In this chapter, we discuss various installation setups you can use to install and configure Reporting Services. For the most part, this process is managed by the Setup.exe installation wizard, so expect to be prompted for a number of configuration options that determine how, where, and whether each segment of the Reporting Services package will be installed. We know that there are a variety of ways to install Reporting Services, so we've tried not only to address the common case, but also provide hints and techniques to be used for some of the more sophisticated installation scenarios. To make this process as painless as possible, we've broken this chapter down into several sections:

Changing SQL Server Passwords

SQL Server 2000 does not have the best or most secure password mechanism. In fact it does a pretty poor job of managing passwords and forcing changes. From the very knowledgable web team over at Orcsweb, a short article on how you change passwords in code.

Data Driven Architecture

Most SQL Server developers and DBAs are familiar with the concept of using a database as a back end to a web site or other application. However the database can be used to store more than just the data that users will edit. An interesting approach to application design begins with some knowledge of the metadata about the underlying data structures and using this to drive the application's behavior. New author Jim Craddock has utilized just such a concept in one if his applications and he brings us a look at how this works.

MDX Essentials: The CROSSJOIN() Function: Breaking Bottlenecks

In this article, we will return to a function we introduced in an earlier article, CROSSJOIN(), whose mission it is to combine two sets of dimension members into one. We will discuss how CROSSJOIN() works in general, and then discuss how its performance can become an issue in medium to large-sized data sets. We will then undertake a multiple-step practice example intended to assist us in gaining an understanding of the issues, before exposing approaches to minimizing the performance overhead that we can encounter in using CROSSJOIN() to reach our reporting and analysis needs.

Data Archiving: Problems and Solutions

SQL Server does an exceptional job at managing your data and making it available for your users and applications. However it doesn't know when you are done with data and there is not archival solution built. Author David Poole likens not having a strategy to leaving certain undesirable clothing items on your floor and provides some common problems and potential solutions based on his experiences.

eSubscriptions Are Here!!!

Last year we started a magazine, the SQL Server Standard, a publication devoted to SQL Server with articles written by you and me, people who work with the product in the real world. Now we're pleased to announce that eSubscriptions to the magazine in PDF format are now available.

The HAVING and GROUP BY SQL clauses

This month's topic is one that often baffles inexperienced SQL coders. We will look at the GROUP BY clause, and then the difference between conditions placed in the WHERE clause, and the HAVING clause. I have used MySQL to test all of the examples, but most of them should work without any problems on other DBMS' too.

A New MCP Benefit

We would like to think that most DBAs are certified as at least MCPs if not MCDBAs. We have worked out a deal with Microsoft to provide yet another benefit for MCPs. Read on to find out more.

Secure options for remote SQL Server administration

In this two-part series, Serdar Yegulalp explains how to remotely administer SQL Server without compromising network security. In part one below, he describes two methods for providing secure administrative access to remote employees. In part two, he'll examine practical problems you may encounter when remotely administering SQL Server and how to work around them.

Surrounding the ETL Requirements

November 13, 2004 / Issue TOC

Surrounding the ETL Requirements

Before designing an ETL system, you must first understand all of your business needs.

By Ralph Kimball , Margy Ross

Ideally, the design of your extract, transform, and load (ETL) system begins with one of the toughest challenges: surrounding the requirements. By this we mean gathering in one place all the known requirements, realities, and constraints affecting the ETL system. The list of requirements is pretty overwhelming, but it's essential to lay them on the table before launching a data warehouse project.

The requirements are mostly things you must live with and adapt your system to. Within the framework of your requirements, you'll have many places where you can make your own decisions, exercise your judgment, and leverage your creativity, but the requirements are just what they're named. They are required.