SQL Server Magazine January 2005

    Options
Innovative SQL Server Solutions
Dive into the top four 2004 Innovator Awards solutions by exploring the business problems the winners faced. We also get you started with SQL Server 2000 Reporting Services, show you how to find and resolve memory pressure, and more!
  Subscribe
Renew
Master CD
Change Mailing Address
Customer Service
Back Issues
Article Reprints
Group Discounts

Browse Archived Articles By: Issue | Author | Subject | Department |



[Focus]

COTS It's Not

Find out how Michael Rhodes and the Teksouth development team created an advanced decision-support system for one of the largest and most complex networks in the world.

Dynamic Reloading

Innovator Awards runner-up Mike Smith uses a dynamic stored procedure solution to give him the speed and flexibility to offer his end users more pre-built business intelligence results.

Monitoring the World

Learn how Innovator Awards grand-prize winner Arindam Sen created a monitoring, alerting, and reporting system that increased systems availability, boosted revenue, satisfied end-users and Sarbanes-Oxley auditors, and polished SQL Server's image.

Seamless SQL Server Encryption

A seamless database server-side encryption solution based on the Microsoft .NET Framework and SQL Server extended stored procedures was the second runner-up in our 2004 Innovator Awards.

SQL Server Magazine Innovator Award Winners

Dive into the top four 2004 Innovator Award solutions, exploring the business problems the winners faced, how they developed their solutions, and the benefits and ROI their companies experienced from the creative use of SQL Server and .NET technology.




[Features]

Reporting Services 101

Although much excitement surrounded last year's release of SQL Server 2000 Reporting Services, some SQL Server professionals have put off adopting it. If you're ready to give Reporting Services a try, here's a tutorial that will get you started.

Semantic Heterogeneity Spells Trouble

If you've had to combine data sets from different databases, you've probably encountered a semantic heterogeneity: data that doesn’t match in format and therefore is difficult to merge.




[SQL Server Savvy]

Choosing SELECT Statements

Many people incorrectly think that ANSI doesn't support the ability to define a JOIN condition in a query's WHERE predicate. In truth, ANSI lets you define a JOIN condition in either a query's WHERE clause or its JOIN clause.

OSQL Returns Strange Results

Have you seen OSQL -L return servers that don't have SQL Server or Microsoft SQL Server Desktop Engine (MSDE) installed? Here's why...




[Editorial]

Extreme Outsourcing: Risky Business?

Offshoring, outsourcing's extreme cousin, might save organizations some money in the short term, but it has costs of its own.




[Inside SQL Server]

Index Internal Information

You can't always get the information you want about indexes--at least not in Microsoft-approved ways. Here are some less-traveled paths to enlightenment.




[T-SQL Black Belt]

Grouping Ranges

Find groups of dates in a sample retail-activity application, then try a purely logical exercise to strengthen your mental muscles.




[Letters]

Letters, January 2005

Readers ask about when cursors are better than set-based approaches and share tips for managing trace files.




[New Products]

New Products, January 2005

Check out the latest SQL Server-related products.




[SELECT TOP(X)]

Calling All COM Objects

SQL Server stored procedures and extended stored procedures perform a variety of database-related functions. Here are seven sp_OA stored procedures that you can use for OLE Automation.




[Lessons from the Field]

Memory Matters

Memory pressure can be a drain on your system’s resources. Microsoft’s SQL Server Customer Advisory Team shows you how to find and resolve memory pressure--before you decide you need more memory.




[Ask Microsoft]

IF Statements and Stored Procedure Performance This article is only available to registered users.  Sign up now and get instant access!

Microsoft's Gert Drapers says that if SQL Server is selecting different query plans based on different branches in a stored procedure, you're better off splitting the code into separate procedures.



 

ADS BY GOOGLE