First, we assume that our dimension already exists (and we were using some other checksum or MERGE to maintain it). We have to add a column to store the MD5 hash:

ALTER TABLE dbo.DimCustomer ADD
	MD5 VARCHAR(34) NOT NULL DEFAULT ''

Second, we need a staging table to store updated/changed rows. Script out the current dimension as a CREATE, remove all unneeded constraints and indexes, and create a staging table as a heap:

CREATE TABLE [dbo].[Staging_DimCustomer_UpdatedRows](
	[CustomerKey] [INT] NOT NULL,
	[GeographyKey] [INT] NULL,
	[CustomerAlternateKey] [NVARCHAR](15) NOT NULL,
	[Title] [NVARCHAR](8) NULL,
	[FirstName] [NVARCHAR](50) NULL,
	[MiddleName] [NVARCHAR](50) NULL,
	[LastName] [NVARCHAR](50) NULL,
	[NameStyle] [BIT] NULL,
	[BirthDate] [DATETIME] NULL,
	[MaritalStatus] [NCHAR](1) NULL,
	[Suffix] [NVARCHAR](10) NULL,
	[Gender] [NVARCHAR](1) NULL,
	[EmailAddress] [NVARCHAR](50) NULL,
	[YearlyIncome] [MONEY] NULL,
	[TotalChildren] [TINYINT] NULL,
	[NumberChildrenAtHome] [TINYINT] NULL,
	[EnglishEducation] [NVARCHAR](40) NULL,
	[SpanishEducation] [NVARCHAR](40) NULL,
	[FrenchEducation] [NVARCHAR](40) NULL,
	[EnglishOccupation] [NVARCHAR](100) NULL,
	[SpanishOccupation] [NVARCHAR](100) NULL,
	[FrenchOccupation] [NVARCHAR](100) NULL,
	[HouseOwnerFlag] [NCHAR](1) NULL,
	[NumberCarsOwned] [TINYINT] NULL,
	[AddressLine1] [NVARCHAR](120) NULL,
	[AddressLine2] [NVARCHAR](120) NULL,
	[Phone] [NVARCHAR](20) NULL,
	[DateFirstPurchase] [DATETIME] NULL,
	[CommuteDistance] [NVARCHAR](15) NULL,
	[MD5] [VARCHAR](34) NOT NULL)

Now in to SSIS - We will be building:

1. Execute SQL Task to Truncate our Staging table(s)
2. Data Flow Task to Insert new rows and Stage updated rows
1. OLE DB Source to retrieve our source data
2. Script Component to Generate Row Numbers
3. Conditional Split to Evenly Distribute Rows
4. Script Component to Generate MD5 Hashes
5. Union All to Squish it all back together
6. Lookup to get the existing MD5 Hash (if it exists)
7. Conditional Split to separate Unchanged and Changed rows
8. RowCount Transformation
9. OLE DB Destination for Changed rows
10. OLE DB Destination for New rows
3. Execute SQL Task to Update changed rows

Completed Control Flow

Completed Data Flow

1: Execute SQL Task to Truncate our Staging table(s)

TRUNCATE TABLE Staging_DimCustomer_UpdatedRows;

2.1: OLE DB Source to retrieve our source data

Configure the Connection Manager - for the source we'll just select from the dimension minus the surrogate key and MD5 column:

You most likely won't need to exclude any columns - here we unselect the surrogate key and the MD5 column:

2.2: Script Component to Generate Row Numbers

Add one output column to Output 0 in your Row Number Script Transformation

The following code will assign the current row number and increment it for the next row through the buffer:

using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
 
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
{
    private int _rowCount = 1;
 
    public override void Input0_ProcessInputRow(Input0Buffer Row)
    {
        Row.RowNumber = _rowCount++;
    }
}

2.3: Conditional Split to Evenly Distribute Rows

Now in the conditional split, we distribute rows across multiple outputs by using the modulo operator. Modify to suit the number of threads you need to remove any bottlenecks in the MD5 calculation (you may only need one thread):

2.4: Script Component to Generate MD5 Hashes

Add one output column to Output 0 in your Generate MD5 Script Transformation

Select all input columns or just select ones that are going to be in the hash. Since we explicitly specify columns in the script, the hash will only be generated with exactly what columns you tell it to use.

The following script will generate a string representation of a MD5 hash. We do this so that we can do direct comparisons with HASHBYTES converted output (and virtually everything likes dealing with strings better than binary). We do end up doubling the storage cost of the MD5 hash by storing it as a string, but we were fine with that:

using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
 
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
{
    private System.Security.Cryptography.MD5 _md5 =
                new System.Security.Cryptography.MD5CryptoServiceProvider();
 
    public override void Input0_ProcessInputRow(Input0Buffer Row)
    {
        try
        {
            string hashSource =
                (Row.GeographyKey_IsNull ? "" : Row.GeographyKey.ToString())
                + (Row.Title_IsNull ? "" : Row.Title)
                + (Row.FirstName_IsNull ? "" : Row.FirstName)
                + (Row.MiddleName_IsNull ? "" : Row.MiddleName)
                + (Row.LastName_IsNull ? "" : Row.LastName)
                + (Row.NameStyle_IsNull ? "" : Row.NameStyle.ToString())
                + (Row.BirthDate_IsNull ? "" : Row.BirthDate.ToString())
                + (Row.MaritalStatus_IsNull ? "" : Row.MaritalStatus)
                + (Row.Suffix_IsNull ? "" : Row.Suffix)
                + (Row.Gender_IsNull ? "" : Row.Gender)
                + (Row.EmailAddress_IsNull ? "" : Row.EmailAddress)
                + (Row.YearlyIncome_IsNull ? "" : Row.YearlyIncome.ToString())
                + (Row.TotalChildren_IsNull ? "" : Row.TotalChildren.ToString())
                + (Row.NumberChildrenAtHome_IsNull ? "" : Row.NumberChildrenAtHome.ToString())
                + (Row.EnglishEducation_IsNull ? "" : Row.EnglishEducation)
                + (Row.SpanishEducation_IsNull ? "" : Row.SpanishEducation)
                + (Row.FrenchEducation_IsNull ? "" : Row.FrenchEducation)
                + (Row.EnglishOccupation_IsNull ? "" : Row.EnglishOccupation)
                + (Row.SpanishOccupation_IsNull ? "" : Row.SpanishOccupation)
                + (Row.FrenchOccupation_IsNull ? "" : Row.FrenchOccupation)
                + (Row.HouseOwnerFlag_IsNull ? "" : Row.HouseOwnerFlag)
                + (Row.NumberCarsOwned_IsNull ? "" : Row.NumberCarsOwned.ToString())
                + (Row.AddressLine1_IsNull ? "" : Row.AddressLine1)
                + (Row.AddressLine2_IsNull ? "" : Row.AddressLine2)
                + (Row.Phone_IsNull ? "" : Row.Phone)
                + (Row.DateFirstPurchase_IsNull ? "" : Row.DateFirstPurchase.ToString())
                + (Row.CommuteDistance_IsNull ? "" : Row.CommuteDistance)
                ;
 
            byte[] hashBytes = _md5.ComputeHash(
                System.Text.UnicodeEncoding.Unicode.GetBytes(hashSource));
 
            System.Text.StringBuilder sb = new System.Text.StringBuilder();
 
            for (int i = 0; i < hashBytes.Length; i++)
            {
                sb.Append(hashBytes[i].ToString("X2"));
            }
 
            Row.MD5 = "0x" + sb.ToString();
        }
        catch (Exception e)
        {
            Row.MD5 = "Error";
        }
    }
}

To quickly generate the string concatenation statement:

1. Script DimCustomer As SELECT to Clipboard and paste in to Notepad++
2. Search > Replace... (Ctrl+H)
3. Select Regular expression for Search Mode
4. Find: ^.*?\[(.*?)\].*$
5. Replace: + (Row.\1_IsNull ? "" : Row.\1)
6. Replace All, remove the leading +, and remove the garbage at the bottom, remove surrogate and business keys
7. Paste results in to the script
8. Add .ToString() to non-string columns and fix any column names (issues will be underlined in red)

Copy your completed script component once for each thread you'll be running. When you copy a script component, you need to actually open the script after copying it and click Edit Script before it will validate.

2.5: Union All to Squish it all back together

2.6: Lookup to get the existing MD5 Hash (if it exists)

Configure the Lookup component to redirect rows with no matches to the No Match output:

For your connection, select the surrogate key, business key(s), and MD5 hash from your existing dimension table:

Lookup based on the business key(s) and bring back the existing MD5 and surrogate key

2.7: Conditional Split to separate Unchanged and Changed rows

Name the output for rows where the ExistingMD5 is the same as the new MD5 "Ignore" and name the Default output "Update"

2.8: RowCount Transformation for Ignored Rows

For your Ignored Rows Row Count transformation, you'll have to create a variable to store the rowcount in (we don't use it, but that's just how the transformation works):

2.9: OLE DB Destination for Changed rows

We'll insert rows that need to be updated in to the previously created Staging_DimCustomer_UpdatedRows table:

2.10: OLE DB Destination for New rows

Finally, insert new rows directly in to the dimension:

3: Execute SQL Task to Update changed rows

The final step is to take those rows we staged for updating and actually perform the update:

UPDATE a SET
 [GeographyKey] = b.[GeographyKey]
,[CustomerAlternateKey] = b.[CustomerAlternateKey]
,[Title] = b.[Title]
,[FirstName] = b.[FirstName]
,[MiddleName] = b.[MiddleName]
,[LastName] = b.[LastName]
,[NameStyle] = b.[NameStyle]
,[BirthDate] = b.[BirthDate]
,[MaritalStatus] = b.[MaritalStatus]
,[Suffix] = b.[Suffix]
,[Gender] = b.[Gender]
,[EmailAddress] = b.[EmailAddress]
,[YearlyIncome] = b.[YearlyIncome]
,[TotalChildren] = b.[TotalChildren]
,[NumberChildrenAtHome] = b.[NumberChildrenAtHome]
,[EnglishEducation] = b.[EnglishEducation]
,[SpanishEducation] = b.[SpanishEducation]
,[FrenchEducation] = b.[FrenchEducation]
,[EnglishOccupation] = b.[EnglishOccupation]
,[SpanishOccupation] = b.[SpanishOccupation]
,[FrenchOccupation] = b.[FrenchOccupation]
,[HouseOwnerFlag] = b.[HouseOwnerFlag]
,[NumberCarsOwned] = b.[NumberCarsOwned]
,[AddressLine1] = b.[AddressLine1]
,[AddressLine2] = b.[AddressLine2]
,[Phone] = b.[Phone]
,[DateFirstPurchase] = b.[DateFirstPurchase]
,[CommuteDistance] = b.[CommuteDistance]
,[MD5] = b.[MD5] 
FROM DimCustomer a
	 INNER JOIN Staging_DimCustomer_UpdatedRows b
		ON a.CustomerKey = b.CustomerKey

To quickly generate the update statement:

1. Script DimCustomer As SELECT to Clipboard and paste in to Notepad++
2. Search > Replace... (Ctrl+H)
3. Select Regular expression for Search Mode
4. Find: ^.*?\[(.*?)\].*$
5. Replace: ,[\1] = b.[\1]
6. Replace All, remove surrogate key and garbage at the bottom, remove leading comma
7. Add UPDATE a SET at the top
8. Add appropriate FROM clause at the bottom

And bob's your uncle.

In closing...

Why not write a reusable code block for the MD5 hash that you could cut and paste? Why hardcode columns?
Well, there's really only two ways to do it dynamically. One is to loop over each column in the InputBuffer and concatenate them. Man, that's a bunch of extra logic when we know very well what columns are, null handling is a little sketch, and proper datatype handling requires some special logic. Looping over the InputBuffer also just plain feels dirty. The second option is Reflection. Now we could approach reflection two ways - first we could iterate over the Row definition and concatenate the columns for each InputRow, but this is INCREDIBLY expensive (reflection is crazy slow). The second Reflection approach would be to construct a DynamicMethod at runtime and call that dynamic method for each row. While this could certainly be as fast as hardcoding, it's very obscure and difficult for most people to understand. Do you want code in your packages that's hard to understand?

We chose hardcode the columns because this is the absolute minimum amount of work that needs to be done to generate a reliable MD5 hash and is therefore the fastest possible solution.

Why not do that Reflection and DynamicMethod thing in a custom transformation?
Because one of the main goals here was to rid ourselves of 3rd party dependencies (all custom assembly dependencies really) and we wanted to do the minimum amount of work required to generated a reliable MD5 hash.

Why bulk update at the end rather than update each row via OLE DB Command?
Because the OLE DB Command isn't set based and it can block/be blocked by inserts. Also, parameter mapping to all those Param_XX parameters and counting question marks is just terrible. So, so terrible.

How do I know how many threads I need to distribute the MD5 calculation over?
First we'll usually watch the source query in the database engine to see what it's waiting on. PREEMPTIVE_OS_WAITFORSINGLEOBJECT tends to point at SQL Server waiting to send data to SSIS because it's not accepting rows fast enough. For a starting point, take your source query and see how long it takes to just insert the entire thing in to a heap - somewhere around there is what we're shooting for. Faster if you ignore many rows, slower if you update/insert many rows.

How does it perform?
It's ridiculously fast. One of our dimensions (55 columns, varying datatypes, ~5 million deep, ~4.5 million evaluated for changes 3 times a day) went from 50+ minutes per run to 5-9 minutes per run. More importantly, we were previously using the CRC32 algorithm in the Checksum transform and that wasn't producing reliable checksums so we would either update unchanged rows or even miss changes to rows - now the hashes are dead on and reproducible via HASHBYTES.

As a side note, we were able to get Checksum to keep up with sql server by spreading it across 6 threads but the lack of reliable output forced us to abandon it.

Is there a quick way to mimic the SSIS MD5 using HASHBYTES?

1. Script DimCustomer As SELECT to Clipboard and paste in to Notepad++
2. Search > Replace... (Ctrl+H)
3. Select Regular expression for Search Mode
4. Find: ^.*?\[(.*?)\].*$
5. Replace: +ISNULL(CAST([\1] AS NVARCHAR(255)),N'')
6. Replace All, remove surrogate key, business key(s), leading +, and garbage at the bottom
7. Add CONVERT(VARCHAR(34), HASHBYTES('md5', at the top
8. Add ),1) AS [Hashbytes] and an appropriate FROM clause at the bottom

Now if all your columns are chars, nchars, varchars, nvarchars, ints, and decimals - you're good. If some of your columns are the more unique datatypes (datetime, money, bit, etc) - then you've got more work to do. The issue lies in the difference between how sql server converts these datatypes to NVARCHAR and how C# converts them to strings. Here are a few examples:

The dates are the biggest debacle as they're sensitive to localization settings. If you actually had to generate the hashes using HASHBYTES on a regular basis, we would recommend modifying the date formatting when concatenating columns for the hashSource variable in the script so they match sql server. For us, we only generate MD5s using HASHBYTES for troubleshooting and updating the hash using purely dim columns rather than relying on the source as some business keys no longer exist in the source.

Here's the finished tsql for the above hash:

SELECT 
 CustomerKey
,CustomerAlternateKey
,MD5
,CONVERT(VARCHAR(34), HASHBYTES('md5',
ISNULL(CAST([GeographyKey] AS NVARCHAR(255)),N'')
+ISNULL(CAST([Title] AS NVARCHAR(255)),N'')
+ISNULL(CAST([FirstName] AS NVARCHAR(255)),N'')
+ISNULL(CAST([MiddleName] AS NVARCHAR(255)),N'')
+ISNULL(CAST([LastName] AS NVARCHAR(255)),N'')
+ISNULL(CASE WHEN [NameStyle] = 1 THEN N'True' ELSE N'False' END,N'')
+ISNULL(
CAST(DATEPART(MONTH,[BirthDate]) AS NVARCHAR(2))
+'/'+CAST(DATEPART(DAY,[BirthDate]) AS NVARCHAR(2))
+'/'+CAST(DATEPART(YEAR,[BirthDate]) AS NVARCHAR(4))
+' '+LEFT(RIGHT(CONVERT(NVARCHAR, [BirthDate], 109), 14),8)
+' '+RIGHT(CONVERT(NVARCHAR, [BirthDate], 109), 2)
,N'')
+ISNULL(CAST([MaritalStatus] AS NVARCHAR(255)),N'')
+ISNULL(CAST([Suffix] AS NVARCHAR(255)),N'')
+ISNULL(CAST([Gender] AS NVARCHAR(255)),N'')
+ISNULL(CAST([EmailAddress] AS NVARCHAR(255)),N'')
+ISNULL(CAST(CAST(YearlyIncome AS FLOAT) AS NVARCHAR(255)),N'')
+ISNULL(CAST([TotalChildren] AS NVARCHAR(255)),N'')
+ISNULL(CAST([NumberChildrenAtHome] AS NVARCHAR(255)),N'')
+ISNULL(CAST([EnglishEducation] AS NVARCHAR(255)),N'')
+ISNULL(CAST([SpanishEducation] AS NVARCHAR(255)),N'')
+ISNULL(CAST([FrenchEducation] AS NVARCHAR(255)),N'')
+ISNULL(CAST([EnglishOccupation] AS NVARCHAR(255)),N'')
+ISNULL(CAST([SpanishOccupation] AS NVARCHAR(255)),N'')
+ISNULL(CAST([FrenchOccupation] AS NVARCHAR(255)),N'')
+ISNULL(CAST([HouseOwnerFlag] AS NVARCHAR(255)),N'')
+ISNULL(CAST([NumberCarsOwned] AS NVARCHAR(255)),N'')
+ISNULL(CAST([AddressLine1] AS NVARCHAR(255)),N'')
+ISNULL(CAST([AddressLine2] AS NVARCHAR(255)),N'')
+ISNULL(CAST([Phone] AS NVARCHAR(255)),N'')
+ISNULL(
CAST(DATEPART(MONTH,DateFirstPurchase) AS NVARCHAR(2))
+'/'+CAST(DATEPART(DAY,DateFirstPurchase) AS NVARCHAR(2))
+'/'+CAST(DATEPART(YEAR,DateFirstPurchase) AS NVARCHAR(4))
+' '+LEFT(RIGHT(CONVERT(NVARCHAR, DateFirstPurchase, 109), 14),8)
+' '+RIGHT(CONVERT(NVARCHAR, DateFirstPurchase, 109), 2)
,N'')
+ISNULL(CAST([CommuteDistance] AS NVARCHAR(255)),N'')
),1) AS [Hashbytes]
FROM DimCustomer

And the results:

A few things to check for right away to see if you're having the same issue we were:

• Check to see if the fuel pump runs during cranking - ours didn't
• Check for spark during cranking - we didn't have any
• Check to see if your check engine light is on (ours WASN'T)
• Check your voltage and fuel gauges with the ignition on - ours didn't register anything
• Check to see if your low fuel light is on - our was




Fancy tool time - we hooked up the Genisys EVO to the data link connecter (located under the steering wheel):


We first tried to connect to the PCM computer to view the Datastream (and check codes) - whatever it would tell us:


Aaaaand it said it didn't want to talk to us:


Then we moved on to the BUS monitor to see if the bus was up and what computers we could talk to:


Looks like the Body computer (BCM) is willing to talk to us:


Now, we see the bus is up, the PCM appears to be down - so we replaced the PCM. Unfortunately replacing the PCM did absolutely nothing for us other than lighten our wallets. At this point, we did some digging on AllDataDiy for an appropriate troubleshooting test to figure out what on earth was going on. While I can't re-publish their content due to the ToS agreement, I can tell you how we arrived at our final solution.

We started by testing the Throttle Position Sensor voltages:


Pin 3 should be above 4 volts:


Since it was under 4 volts, we unplugged the Camshaft Position Sensor (connector locations below - this is the passenger side of the engine compartment):


And checked again - still under 4 volts:


Then we unplugged the Crankshaft Position Sensor and checked voltage again:


Finally, a bad component! We replaced the Crankshaft Position Sensor and verified that all was well


Fuel Gauges now work, voltage works, and the low fuel light isn't on anymore


We started it up and checked the ECM datastream again - all systems go


Now, the troubleshooting procedure we started out with had us unplug the ECM at the beginning and then test the TPS pin 3 voltage - but these pictures are from us reproducing it after the fact and we forgot to unplug the ECM first... so we logged a code:


I mention this code just as a side note - we cleared the code with the EVO, but if you just ignore it long enough it'll go away after a few cycles.

]]> http://timlaqua.com/2011/07/troubleshooting-1998-jeep-grand-cherokee-zj-doesnt-start-cranks-no-fuel-no-spark/feed/ 2 http://timlaqua.com/2008/11/blackberry-storm-9530-error-sim-card-rejected/ http://timlaqua.com/2008/11/blackberry-storm-9530-error-sim-card-rejected/#comments Fri, 28 Nov 2008 16:12:45 +0000 Tim http://timlaqua.com/?p=54

This error pops up when you lose CDMA (1XEV) connectivity in the US and the phone attempts to connect to a GSM network (you can duplicate if you force your Storm to GSM network technology) and you have a Global SIM card installed (and most of us do). The kicker is that the message "SIM Card Rejected" doesn't go away until your hard reboot - even after you've reconnected to the CDMA network.

So, if you're not using your Global SIM (if you are, call VZW and ask for Global Support - they can activate your SIM), you can just force CDMA only on the phone, do a battery pull, and you'll never see this again. I assume some future firmware update will handle this error better by making it go away once you're back on CDMA, but for now - this is what I had to do:

1. Select Options from the menu:
   
2. Select Mobile Network Options:
   
3. Change the Network Technology from Global to 1XEV:
   

4. Pull the battery out, put it back in, and once it reboots - the error will be gone and won't reappear.
]]> http://timlaqua.com/2008/11/blackberry-storm-9530-error-sim-card-rejected/feed/ 19 http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/ http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/#comments Mon, 17 Nov 2008 03:12:55 +0000 Tim http://timlaqua.com/?p=51 ASTrace.exe is part of the SQL Server Analysis Services Community Samples on CodePlex. This utility works just fine in a 32-bit environment, however some of the assemblies needed to interact with Analysis Services do not have 64-bit counterparts - thus, you have to use WOW64 to get the service to work properly on a x64 machine.

ASTrace can be downloaded here:
http://www.codeplex.com/SQLSrvAnalysisSrvcs/Release/ProjectReleases.aspx?ReleaseId=13572

32-bit Installation Instructions can be found here:


http://msdn.microsoft.com/en-us/library/bb283156(SQL.90).aspx

And to get it to work on x64, you need to do two things differently:

• Target x86 processors when you build the application - this way, your 64-bit OS will use WOW64 when the service runs (Project > ASTrace Properties... > Build Tab).
  

• Create the following registry key and string value pointing to where you copied the ASTrace files:
  [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASTrace]
"path"="C:\\ASTrace"
]]> http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/feed/ 1 http://timlaqua.com/2008/11/how-to-add-a-calculated-measure-calculated-field-to-an-excel-2007-pivottable-with-a-ssas-data-source/ http://timlaqua.com/2008/11/how-to-add-a-calculated-measure-calculated-field-to-an-excel-2007-pivottable-with-a-ssas-data-source/#comments Wed, 05 Nov 2008 18:28:12 +0000 Tim http://timlaqua.com/?p=50 As it turns out, you can do it programatically as explained by Allan Folting here:
Microsoft Excel: Common Questions Around Excel 2007 OLAP PivotTables:
http://blogs.msdn.com/excel/archive/2008/02/05/common-questions-around-excel-2007-OLAP-PivotTables.aspx

And the parts that I have to keep looking up (I use my blog as a notebook for things I don't want to forget :

Sub AddCalculatedMeasure() 
	Dim pvt As PivotTable
	Dim strName As String
	Dim strFormula As String 
 
	Set pvt = Sheet1.PivotTables("PivotTable1")
	strName = "[Measures].[Internet Sales Amount 25 %]"
	strFormula = "[Measures].[Internet Sales Amount]*1.25"
	pvt.CalculatedMembers.Add Name:=strName, Formula:=strFormula, Type:=xlCalculatedMember 
End Sub 
 
Sub AddCalculatedMember() 
	Dim pvt As PivotTable
	Dim strName As String
	Dim strFormula As String 
 
	Set pvt = Sheet1.PivotTables("PivotTable1")
	strName = "[Product].[Product Categories].[Bikes].[Mountain Bikes].[Mountain-100 Silver, 38 25 %]"
	strFormula = "[Product].[Product Categories].[Bikes].[Mountain Bikes].[Mountain-100 Silver, 38]*1.25"
	pvt.CalculatedMembers.Add Name:=strName, Formula:=strFormula, Type:=xlCalculatedMember
	pvt.ViewCalculatedMembers = True 
End Sub 
 
Sub AddNamedSet() 
	Dim pvt As PivotTable
	Dim strName As String
	Dim strFormula As String
	Dim cbf As CubeField 
 
	Set pvt = Sheet1.PivotTables("PivotTable1")
	strName = "[My Mountain Bikes]"
	strFormula = "[Product].[Product Categories].[Bikes].[Mountain Bikes].children"
	pvt.CalculatedMembers.Add Name:=strName, Formula:=strFormula, Type:=xlCalculatedSet
	Set cbf = pvt.CubeFields.AddSet(Name:="[My Mountain Bikes]", Caption:="Mountain Bikes") 
End Sub

He also mentions that you can expose these members to Excel Services 2007 by creating the new objects and then removing the VBA code - very useful article.

]]> http://timlaqua.com/2008/11/how-to-add-a-calculated-measure-calculated-field-to-an-excel-2007-pivottable-with-a-ssas-data-source/feed/ 0 http://timlaqua.com/2008/09/how-to-replace-the-battery-in-a-polar-f11-heart-rate-monitor-hrm/ http://timlaqua.com/2008/09/how-to-replace-the-battery-in-a-polar-f11-heart-rate-monitor-hrm/#comments Sun, 14 Sep 2008 23:40:58 +0000 Tim http://timlaqua.com/?p=47 Disclaimer: The user manual for the Polar F11 clearly states to take the HRM to a Polar dealer and have them replace the battery - taking the back off could void your warranty. If you wish to be 100% sure that you maintain the water-resistant seal and do not want to void your warranty - or risk breaking your HRM (certainly a possibility when you take it apart...), take the unit to an authorized Polar dealer and have them replace the battery.

Step 1: Remove the back cover (4 little screws - make sure you have the right size screwdriver or you'll strip them out). Also note that the back has a water-resistant seal - keep this clean and remember that there is always a chance that the seal may be damaged if you do this yourself.
Step 2: Remove the internal unit from the watch casing (it just pulls out).
Step 3: Get something to pry the battery latch tab with (I used another small screwdriver)
Step 4: Take whatever you used to pry the latch tab out with and use it to pry the battery up by placing the device (screwdriver in my case) in the notch above the latch (see picture).
Step 5: Go to Wal-Mart and purchase a new CR2032 watch battery (you may want to do this before hand... I didn't know what battery it used so I had to take it out first) - runs about $3.50.
Step 6: Put the battery back in and put everything back together.

]]> http://timlaqua.com/2008/09/how-to-replace-the-battery-in-a-polar-f11-heart-rate-monitor-hrm/feed/ 223