Browse by Tags
All Tags »
SQL Server 2005 »
SQL Server (
RSS)
CU 4 was released yesterday, and as in previous versions, contains the hotfixes that have been developed since the release of SP2. Like with cumulative update 3, this one is also multilanguage and is available through writing a request to Microsoft Online Customer Services at http://go.microsoft.com/?linkid=6294451 . To install cumulative update package 4 for SQL Server 2005 Service Pack 2, you need to enable the SMO and the SQL-DMO stored procedures. The cumulative update is also known as build...
I thought this time around, we'll discuss how solve order can affect your MDX calculations. I found that people tend to ignore this property, as it is not mentioned in the "Form View" of the Calculation Tab of the cube (which is what people usually tend to use when they write MDX for a cube. I hope this will be taken into consideration in SQL Server 2008). Now, this is a shame, as solve order can greatly affect your calculations. For each calculation you do in MDX, you can specify the optional property...
There are quite a few ways of ways of documenting the changes a business entity goes through over time. The most famous of them all (and the most difficult to build) is a Slowly Changing Dimension (SCD) type 2. doing this in a table, you would create a table which would include: an incremental key, the business key, the attributes you'd like to track for that entity, a start date and an end date (for which the information was right) and a flag which would equal 1 when we are looking at the last...
Goodness, it's feels like I just blinked there for a moment, and already Microsoft is releasing a new cumulative update for SQL Server 2005 SP2! The build of the cumulative update package is also known as build 3186. The knowledge base article is here and the download itself is available here , and you can download the version in which ever language suits you. And just so you don't think the guys at Microsoft are resting on their laurels, I would tell you that obviously, Cumulative Update #4 is already...
Hi everybody, What’s up? Thought I’d share with you something strange I found while using named queries in the DSV layer in SQL Server Analysis Services. I have developed quite a complex layer of connected tables in my DSV. As development had evolved (with the customers demand) I found myself turning 3 of my regular tables into named queries. The named queries were basically using the same table twice in an inner join to compare the state of the entity in two different times in the table. After this...
About a week a go (I admit I'm only catching up to it now…) Microsoft released the SQL Server 2005 Best Practices Analyzer . The tool analyzes and monitors the SQL Server Profiler files. It uses a predefined list of recommendations to determine if there are potential issues in the database environment. Now if you're like me, then after downloading and installing the tool, you can't help but think to yourself "yeah great, but how do I use it?..." Well all you need to do after that is run the SQL Server...
Fresh! Straight from the oven! Microsoft has just released the second cumulative update package for SQL server 2005 SP2. The basics? You must apply a SQL Server 2005 Service Pack 2 (SP2) hotfix to an installation of SQL Server 2005 SP2. It includes the SQL Server 2005 hotfixes that have been released since the release of SQL Server 2005 SP2 occurred. At the end of the installation, the SQL Server service will have to be restarted (though the set up program does that for you). Enjoy!
We define names for our tables and columns following the guidelines defined in our company. we might even adhere to international naming conventions. Still, nothing promises us the names we give our DB objects will be comprehensible to our customers. And this is where SSAS steps in - Analysis Services enables you to give alternative names to your dimension attributes in the following two ways: Translations may be given to: dimensions, dimension attributes, user hierarchies, measures, measure groups...