Change default Organization in CRM 4.0

Here's a pretty useful script to set the default organization for a certain user. It will take the org that's configured as the default one in the deployment manager. Just replace "domain/username" with the desired user.

update mscrm_config.dbo.systemuser set mscrm_config.dbo.systemuser.defaultorganizationid =

(select sub.organizationid from systemuserbase sub,

mscrm_config.dbo.systemuserorganizations csuo

where sub.systemuserid = csuo.crmuserid and

csuo.userid = mscrm_config.dbo.systemuser.id)

where 1 =

(select count(*) from systemuserbase sub,

mscrm_config.dbo.systemuserorganizations csuo

where sub.systemuserid = csuo.crmuserid and

csuo.userid = mscrm_config.dbo.systemuser.id and
sub.domainname = 'domain\username')

C360 and IFD

I spend hours (or even days) to find out why c360's record editor does not work in our client's CRM environment. What i found out by contacting the c360 support, is that most of the c360 tools do not support internet facing deployment (IFD). So please do not promise your client to get these tools running, when IFD is being used.

System.OutOfMemoryException in VS

If you're working with really large SSIS packages, visual studio might start throwing System.OutOfMemoryExceptions, that even prevent you from saving. Since this is really annoying, you should try to increase the amount of virtual memory - it worked fine for me.

SSIS: chaching options versus network traffic

So, i'm still worrying about the different caching options (full, partial, none) of SSIS. With my current configuration (full caching), i am facing out of memory exceptions (at least sometimes, when things are going really bad).
But changing the settings to "partial" creates another problem: since SSIS and SQL are not running on the same machine, the new settings will increase network traffic (singleton queries).
Mh, i am really curious about which way to go. I will let you know when the time has come. Any kind of help is welcome :).

Thougts on SSIS Lookups

Yesterday i came across SSIS out of memory exceptions that could possibly caused by lookups in my packages. I guess i will have to play around with the caching options of the lookup. Results will follow if i dont forget to post them :)