If you are really interested in the fastest performance, don't use Access as a front-end to a SQL Server database. While Access is relatively easy to learn and fast to develop in, its performance if poor when compared to other front-end options. But if you like to develop in Access, or don't have any choice, then the tips on this page will help a little to boost your application's performance.
The central place for Australia's SQL Server User groups and a list of their meeting times is now available.
SQL Server and Access are usually linked together as Access used for applications at the beginning of their lifecycle that are later moved to SQL Server when the load gets too high or the data sizes grow. There are often cases where you may also want to use SQL Server as a backend to an Access application. But how do you get your data from Access to SQL Server? Author Dinesh Asanka brings us an overview of the various ways that you can move your Access database to SQL Server.
To kick off our first column of the year, we're going to take on a challenging subject that all designers face: how to deal with changing dimensions. Unlike most OLTP systems, a major objective of a data warehouse is to track history. So, accounting for change is one of the analyst's most important responsibilities. A sales force region reassignment is a good example of a business change that may require you to alter the dimensional data warehouse. We'll discuss how to apply the right technique to account for the change historically. Hang on to your hats — this is not an easy topic.
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:
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.
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.
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.
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.
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.
By gbargsley
Recently, I was in a technical interview where the topic of running PowerShell at...
By alevyinroc
I don’t recall where this came up (probably in SQLSlack), but I had a...
By Steve Jones
One of the parts of getting older that really sucks is I seem to...
Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation
Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...
Comments posted to this topic are about the item Pushing the Limits of AGs
A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?
See possible answers