Just in time for St. Valentine’s Day, RWallace Consulting released its initial version of Love Petals for Windows Phone 7.

The age old question of affection can now be answered on your Windows phone. Love Petals allows users to choose from 3 different flowers where they can pick off the petals to determine if he/she loves me or loves me not. Also, enter in the name of your choice, your spouse, girlfriend, dog, or even your ex-wife’s name!

Download Love Petals Today:

http://social.zune.net/redirect?type=phoneApp&id=e3f9cc60-cc29-e011-854c-00237de2db9e

RWallace Consulting is pleased to announce the release of Ye Olde Rotary version 1.1 to the Windows Phone Marketplace.

Ye Olde Rotary now utilizes the app bar for its navigational and user input controls. This update aligns Ye Olde Rotary with a industrial standard for usability with the Windows Phone.

You can download Ye Olde Rotary, by following this link:

http://social.zune.net/redirect?type=phoneApp&id=765c9c49-c219-e011-9264-00237de2db9e

The full article: http://blogs.msdn.com/b/maximelamure/archive/2007/01/24/create-your-own-pfx-file-for-clickonce.aspx

===my cut/paste

A Personal Information Exchange (pfx file) contains a public key and a private key. You can use it to hash your files (binary, assembly …) and even signed your manifest file for ClickOnce.

If you want to create your own PFX file with your personal information, you have to complete these two steps:

Create your public & private Keys (You will be prompt to define the private key’s password):
makecert.exe -sv MyKey.pvk -n “CN=.NET Ready!!!” MyKey.cer

Create your PFX file from the public and private key
pvk2pfx.exe -pvk MyKey.pvk -spc MyKey.cer -pfx MyPFX.pfx -po toto

Robert Wallace
No Slogans, Just Results

This is a very deceptive error and spent a few hours working it out. Hopefully this will save some of you some pain.

While maintaining and improving performance on some stored procedures, I came across this weird FK issue. I never actually changed the code of the failed statement itself. The proc was using a #temp table to which I added a primary key for performance reasons.

However, when it came time to insert the #temp table data into the real table, I received and error that looked like this:

The INSERT statement conflicted with the FOREIGN KEY constraint “FK_XXX_YYY”. The conflict occurred in database “MyDatabase”, table “dbo.MyTable”, column ‘MyColumn’.

However, the original procedure did not have this error. I went through the normal debugging steps. I checked to make sure the primary table data was there. I checked for nulls. I got a distinct list of key values. I saved the data off and then ran the same insert statement outside of the proc…and it worked!!! Now I was very confused. The data failed in the proc and but did not outside the proc.  No one was touching any data nor was any data getting loaded in between runs/tests.

So I googled it and found this link.

http://www.sqlservercentral.com/Forums/Topic771369-149-1.aspx

To cut to the chase, here is the important part:

Update: There is a bug in microsoft sql server’s Hash Map join plan when it comes to # based temp tables.
To suppress this error(workaround given by Microsoft team): Include order by 1 clause – this will change the join plan.

For eg.
INSERT INTO MAIN_TABLE (DOC_ID_FK_TO_SOME_OTHER_TABLE, ANY_COLUMN)
SELECT DOC_ID_FK_TO_SOME_OTHER_TABLE, ANY_COLUMN
FROM #TEMP_TABLE — This will sometimes throw FK violation which is not a –valid violation
ORDER BY 1 — This suppresses the error

I put the “ORDER BY 1” on my insert statement and it worked.  Thanks for the original poster who gave us this great nugget of info.

Robert Wallace
No Slogans, Just Results

Back to Basics Service Broker Message Types

Robert Wallace
No Slogans, Just Results

http://lennilobel.wordpress.com/2009/07/29/sql-server-2008-table-valued-parameters-and-c-custom-iterators-a-match-made-in-heaven/

http://blogs.msdn.com/windchillonsql/archive/2010/04/09/more-about-how-to-size-fill-factor-on-an-index.aspx

Read more: http://www.bradmcgehee.com/2010/04/how-to-avoid-some-common-developer-and-dba-mistakes/#ixzz0lYUIKydM

However, with VSTS 2008 (and on I am assuming), the setup package only UPDATES the dlls that have NEWER versions.

This may not be a big deal for many because of the version numbering of 1.0.*.*. For those that do use a version number, this did have an impact.

Yes, I know about builds and it should have been incremented anyhow, but sometimes I am human

Robert Wallace
No Slogans, Just Results

Spent a good part of the day trying to track down why an event log could not be created. The installation was NOT executing as administrator, even though I am an administrator on the box. I had to explicitly start Command Prompt with “run as”.

Robert Wallace
No Slogans, Just Results