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
