Technical Article

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:

SQLServerCentral Article

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.

Technical Article

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.

SQLServerCentral Article

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.

Technical Article

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.

Blogs

Word to the wise: don’t turn on SQL vulnerability checks on a blog about SQL

By

Recently, in an attempt to thwart leechers (1990s kids will know), I added some...

Dazzling Stuff in Databricks (SQL) – Qualify

By

Once upon a time I had a series about some cool stuff in Snowflake:...

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

Read the latest Blogs

Forums

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Adding Bits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits II

An Unlimited Token Budget

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unlimited Token Budget

Visit the forum

Question of the Day

Adding Bits II

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers