hen database developers must deliver time values that are accurate to the millisecond, many assume Access can’t handle that requirement. They might deem SQL Server the obvious choice, not realizing
he histogram is a mathematical tool that is invaluable when analyzing large quantities of data. A histogram may be represented in a table of numbers or in a chart. Because
ften when developing reports in SQL Server Reporting Services (SSRS), mixing summary (or grouped) data with transactional detail becomes a requirement. Show a sales manager how her top products or
atrix components are great for visualizing data that you might normally export to Excel, or in a Pivot Table (year-over-year analysis is a good example). But if an analyst wants
ne of the largest changes in SQL Server 2008 Reporting Services (SSRS) is that it no longer relies on IIS. Due mostly to feedback from end users on security (most
Often developers are tasked with not only developing functional code but also with ensuring that the code they develop scales well and performs in the application environment. The tests that
f you’ve ever worked with sophisticated database systems or large applications you’ve probably accumulated sizable libraries of stored procedure code. Such libraries typically hold a few hundred stored procedures, ranging
he data-loss scenario I described in the DevX article SQL Server 2005 Bug Alert: Merge Replication Could Mean Data Loss (published November 2, 2007) is mainly due to the difference
iltering is an important aspect of writing most complex queries. While there may be instances where you don’t need a filter, such as a simple query that retrieves a list