any SQL Server developers eagerly anticipate the long-awaited release of SQL Server 2005, formerly code-named “Yukon.” Major goals for Business Intelligence (BI) in the 2005 release are better integration of
ost report design tools attempt to please both developers and non-technical end users by combining high levels of flexibility and power and ease-of-use. This accommodation naturally requires various sacrifices on
f you’re a database developer, you’ve no doubt heard of On-Line Analytical Processing (OLAP) and the advantages of analysis using multi-dimensional, pre-aggregated data. Maybe you’ve even thought about creating your
QL Server Reporting Services (RS) is: A new component of the SQL Server platform that Microsoft recently made available (January 27, 2004) A server-based package that comes in four configurations:
rganized to provide conceptual understanding of high availability, this book includes a section on ?HA Workshops,? step-by-step instructions to get you through certain implementations, plus real-world inspired case studies. While
he database server is a fixture in almost every business these days. The common commercial databases, such as Oracle, Microsoft’s SQL Server, and IBM’s DB2 server, include many features that
ike most DevX readers, anticipating change is an important part of my job. As a software developer and system architect, it is particularly important that I make sure our middle-tier
uch of the buzz surrounding the release of SQL Server Yukon seems to be about its new integration with the CLR. However, there are plenty of other worthwhile features in
f you sell a product that needs a database, you have a business quandary on your hands, namely: “What database should I use? Will my customers have SQL Server? Oracle?