Hosting

[Jason Elliott]

Have there been any hosting companies identified that are suitable for running Team Pulse for a small team? I really want to start using Team Pulse, but I am not sure I have a budget for $500/month some companies are wanting to charge after I show them requirements. (Go Daddy)

Thanks in Advance,
Jason

[Missing User]

Hello Jason Elliott,

There are a wide variety of options to look at. One that I quickly found for you to check out is fasthosts. After a quick glance, their virtual server service might be what you're looking for. I'm sure fasthosts aren't the only ones out there either, you just have to do some digging.

Kind regards,
Jesse Dyck
the Telerik team

[jimi]

Jesse,

Is TeamPulse deploy-able to Windows Azure environment with SQL Azure? 

Thanks,

[Missing User]

Hi jimi,

Currently TeamPulse is not deployable to Window Azure with SQL Azure. This is something that we are working on for a future release however.

Kind regards,
Jesse Dyck
the Telerik team

[Keith Mistry]

Jesse,

That's great to look forward!
 
It seems that the most ideal installations for Teampulse are on dedicated servers.

Are there any successful installations at DiscountASP.net?

Thanks,

 

[Missing User]

Hi Keith Mistry,

None that we have heard of yet. Looking at the features available, you should be able to. I would check with them first of course.

Kind regards,
Jesse Dyck
the Telerik team

[Tevis]

I was wondering if with the newest release of TP (R1 2011) now worked on Azure?

Thanks in advance

[Ryan]

Hello Tevis,

Thanks for the interest. But no, at this time TeamPulse does not work on Azure.

Kind regards,
Ryan
the Telerik team

[kamakaze]

When you are planned to support Azure - this will be very useful for your customers.

[Jordan]

Hi Mikko,

It is possible to deploy manually TeamPulse on the azure environment. Our database is compatible with it and you can use the Sql Azure Migration Wizard to create a script and create the database from it. Next you will need to setup the web role and deploy the integration service there.
We doesn't recommend that because we can't provide a full support in this case because the upgrade process. Also there is a performance issue with SQL Azure in general.

The cloud offering is very important for us and we are constantly invest time in this direction.

Regards,
Jordan
the Telerik team

[Patrick]

Sorry, that is incorrect.  The SQL Database Migration Wizard fails to migrate a TeamPulse database from SqlServer (14) to Azure, just like SqlServer Management Studio does, because of problems like:

 

Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again.
And far from being committed to the cloud, Telerik have stopped maintaining/sales of TeamPulse. A shame.

[Patrick]

Update: I *have* finally managed to migrate our TeamPulse database from SQLServer to Azure as follows:

 

I eventually managed (using  SQL Database Migration Wizard and editing the intermediate script it produced, so that the EntityTypeStatus table has a clustered index, and then getting the wizard to run using that slightly modified script) to migrate the database to Azure.

More details:

I managed to successfully migrate the TeamPulse database to Azure by using the migration tool, but saving the script from the 1st stage to a sql file, and then pasting back in to the migration tool a modified version of the script

In which
CREATE TABLE [dbo].[EntityTypeStatus](
[EntityTypeStatusID] [int] IDENTITY(1,1) NOT NULL,
[ProjectID] [int] NOT NULL,
[EntityType] [nvarchar](16) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[StatusGroup] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Status] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
)
GO
SET ANSI_PADDING ON
GO

Was replaced by:
CREATE TABLE [dbo].[EntityTypeStatus] (
[EntityTypeStatusID] [int] IDENTITY(1,1) NOT NULL,
[ProjectID] [int] NOT NULL,
[EntityType] [nvarchar](16) NOT NULL,
[StatusGroup] [nvarchar](50) NOT NULL,
[Status] [nvarchar](50) NOT NULL,
    CONSTRAINT [PK_EntityTypeStatus] PRIMARY KEY CLUSTERED ([EntityTypeStatusID] ASC)
)

GO
NB the next line starting CREATE NONCLUSTERED INDEX [IX_EntityTypeStatus_StatusGroup] ON [dbo].[EntityTypeStatus] can be left I think because all Azure needs is one clustered index for the table, which it now has in EntityStatusID.

(And then obviously the Web.config files for TeamPulse and for the Feedback and Ideas Portal need in the usual way the connection string to point to the Azure database rather than the local one.)

I hope this helps

[John]

Hello Patrik,

We are happy that you have successfully migrated your instance to Azure. One thing to keep in mind is that if you go to upgrade your instance to the latest version you can have an issue with database update. As a recommendation I will suggest you to remove your changes before upgrade and then execute them again after the upgrade. 

Regards,
John
Telerik

 

[Patrick]

 

Thanks John.

(Yes our version was Team Pulse Q1 2014, other versions may need slightly different treatment, although I think the approach of editing the script to adding a clustered index to any tables that don't have one should still work).

We have no plans to upgrade to a newer version of TeamPulse because I think Telerik has stopped supporting/selling TeamPulse (or will very shortly do so, and we have got used to, and are happy with, the current version we have, Q1 2014).

[John]

Hello Patrick,

Glad to hear that you have successfully migrated your instance.

Thanks for using TeamPulse!

Regards,
John
Telerik