Can I work with abril ctp and migrate later to an express version?

Hello

The final customers of my application should have sql server express. Can I work with sql abril ctp and then when the final version of sql express has been released install it and migrate the database?

You should use June CTP (build 1187), not April CTP.

June CTP to RTM (Release) migration is a supported scenario. However, since you will be downgrading the SKU (e.g. Developer SKU to Express SKU) certain features may/will be unavailable. Some of this is transparent to the app (e.g. you won't get AWE support), but some may impact functionality (e.g. feature functionality is limited). It depends on what your application uses.

If you are concerned about databases only, upgrade should work fine from June CTP.

Regards,
Boris.

|||The only thing I need to create is tables, views, triggers and CLR stored procedures. So If I create these objects with sql 2005 june ctp and visual studio 2005 june ctp.

And when the final version of sql express and vs 2005 had been released it should work? I guess i only have to make a backup of the sql june ctp database, uninstall june ctp, uninstall vs 2005 june ctp, and then install vs 2005 profesional or team system , and then install final version of sql express and restore the database and it should work?

Am I missing something?|||

Yes, what you describe should work.

There are two parts to your question:

1. Going from June CTP to RTM – this should be just fine
2. Going from Developer SKU to Express SKU – this has caveats as outlined below

Caveat: if you use a feature that is available only on Dev/Enterprise SKU, once you migrate to Express you may run into problems. Most notable features that may create problems are database mirroring, database snapshot, failover clustering and table partitioning.

At release time there will be a document describing upgrade/downgrade process.

HTH,
Boris.

Can I use Merge Replication via Developer Edition to Cluster?

I am a DBA in one IT group and we do our development work on the developer
edition of SQL Server 2005 and migrate everything to our SQL Server 2005
cluster for production.
We want to use merge replication between the Developer Edition and the
Cluster but I am being told by the DBA on the cluster that:
1. The developer edition of SQL Server does not have the same features as
the enterprise edition; that the enterprise edition is required for
implementing the SQL Cluster as this is not featured in the developers
edition.
This statement seems to conflict with what Microsoft has posted online at ...
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
"SQL Server 2005 Developer Edition and Evaluation Edition are not listed in
the tables. These editions have the same feature set as the Enterprise
Edition; the only difference between these editions is the licensing
policies."
2. That reporting services in the developers edition has limitations which
requires you to upgrade to the standard or enterprise edition in order to
take advantage of all the bells and whistles for this product. Our DBA sats
the developer edition is just that, a developers editio,n and which is
normally used for testing before implementing to standard or enterprise
editions of SQL Server.
3. That replicating data from a developers edition to the enterprise edition
of SQL Server Cluster is not supported by Microsoft, thus if issues arise
Micorsoft will not support this setup.
So does anyone if there's any truth to our inability to do merge replication
from the Developer Edition to the Cluster?
Thanks!
You need a new dba.
1) The developer edition supports all of the features of the Enterprise
Edition. There may be a limitation on the number of subscribers you can have
to a publication, but if there is it is not documented.
2) I am not sure about this one, but I don't think it is correct. You would
need to post to the reporting services group for more information.
3) This might be a licensing issue. The developer edition is intended for
development only. You will be able to replicate to a cluster running SQL
Server 2005 EE. When it comes to licensing issues you may have to
demonstrate licensing for auditors, but CSS will help you with problems you
may encounter while running this.
Keep in mind the developer edition is for development, not production.
Should you be replicating to production it should be a one time or
occasional occurrence as part of your development process, and not part of a
production topology.
That been said I have set up replication to development environments from a
production environment many times. I did not configure the licensing but I
am confident it was legit.
HTH
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Robert Reist" <RobertReist@.discussions.microsoft.com> wrote in message
news:0D620D0B-4432-4377-A2CD-C92C62C29EDE@.microsoft.com...
>I am a DBA in one IT group and we do our development work on the developer
> edition of SQL Server 2005 and migrate everything to our SQL Server 2005
> cluster for production.
> We want to use merge replication between the Developer Edition and the
> Cluster but I am being told by the DBA on the cluster that:
> 1. The developer edition of SQL Server does not have the same features as
> the enterprise edition; that the enterprise edition is required for
> implementing the SQL Cluster as this is not featured in the developers
> edition.
> This statement seems to conflict with what Microsoft has posted online at
> ...
> http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
> "SQL Server 2005 Developer Edition and Evaluation Edition are not listed
> in
> the tables. These editions have the same feature set as the Enterprise
> Edition; the only difference between these editions is the licensing
> policies."
> 2. That reporting services in the developers edition has limitations which
> requires you to upgrade to the standard or enterprise edition in order to
> take advantage of all the bells and whistles for this product. Our DBA
> sats
> the developer edition is just that, a developers editio,n and which is
> normally used for testing before implementing to standard or enterprise
> editions of SQL Server.
> 3. That replicating data from a developers edition to the enterprise
> edition
> of SQL Server Cluster is not supported by Microsoft, thus if issues arise
> Micorsoft will not support this setup.
> So does anyone if there's any truth to our inability to do merge
> replication
> from the Developer Edition to the Cluster?
> Thanks!
>