Any recommendation for Windows 2003-ASP .NET hosting?

Hi All,

In the past few months I been hit with so many technical problems running biztalk 24 * 7.com. I’m currently with 1and1 for my hosting, I been with them for past few years now. Everything is well and good until you hit a problem, but once you got some you are in real trouble.

In my past few months experience I never got a single issue solved by their technical team (this is just my experience).

At last I decided to take the plunge and move to a different hosting company. That’s the only way I can come with next version of biztalk 24 * 7 confidently. Now I need your help on making my decision, here are my criteria’s

1. Preferably in UK, since it will help me solve the issue during UK office hours. With 1and1, even though I’m a UK customer their server department is in US and most of the time I simply need to wait until US wakes up.

2. Windows Server 2003 virtual or dedicated sever hosting.

3. Support for ASP.NET 2.0 and SQL Server

I’m sure lot of you out there reading my blog will have experience in this area. Please feel free to drop your comments.

Nandri!

Saravana

Address should be unique for Receive Location – error when creating a Receive Location in BizTalk

Assume you’re using the WCF SQL Adapter (part of the BizTalk Adapter Pack 2.0). You decide to create 2 Receive Locations (RL), in order to poll the database. Each RL polls a different table (e.g., the “PollingStatement” binding property in the first RL is “SELECT * FROM T1”, while the “PollingStatement” binding property in the second RL is “SELECT * FROM T2”).

Since the tables are present in the same database on the same SQL Server instance, the URI which you enter is the same in both RLs (e.g., something like “mssql://servername/instancename/databasename”).

However, BizTalk doesn’t allow you to create multiple RLs in the same BizTalk application with the same URI. From the BizTalk point of view, it’s like having 2 RLs competing in the same BizTalk application for the same incoming messages. Even though in this (the WCF SQL Adapter) case, both RLs are pulling in messages from different sources (the “PollingStatement” controlling the message source).

There is a pretty simple workaround for this. You can use the following (different) URIs in each ReceiveLocation:

“mssql://servername/instancename/databasename?SomeUnusedQueryParameter=1”

“mssql://servername/instancename/databasename?SomeUnusedQueryParameter=2”

“mssql://servername/instancename/databasename?SomeUnusedQueryParameter=etc”

I guess I should be flattered

I guess I should be flattered

That some spammer thought my wiki pages where hit enough to warrant modifying them
on a daily basis with links to various “odd” sites 😉

Thanks to Craig I’ve
upgraded to FlexWiki 2.0 and now those pages
are locked down – I apologize if you’ve visited them and they haven’t been right, 
should be ok from now on.

My
Workflow Sample Page

My
BizTalk Sample Page

 



Check out my BizTalk
R2 Training.