You are viewing limited content. For full access, please sign in.

Question

Question

Looking for a method to convert a Sql 2000 standard database to Sql Express

asked on May 23, 2014

 I have a customer who wants to convert the database from an existing repository from SQL Standard 2000 to SQL Express 2012.

 

The migration wizard would not allow source db to be SQL Standard 2000 and destination to be SQL Express 2012.

 

What would be the suggested process? I know their is a script to convert from Express to Standard.

0 0

Answer

SELECTED ANSWER
replied on May 23, 2014

There is no directly supported method for downgrading from a full edition of MSSQL to MSSQL Express through the migration utility. I believe our Professional Services group has worked with this sort of custom migration in the past, although I'm not 100% sure.

0 0

Replies

replied on May 23, 2014

Microsoft has restrictions about going straight to SQL 2012 and with going from the full version to the free Express version.  You should try the SQL Server upgrade advisor but generally speaking you cannot go from the full version to an express version.

0 0
replied on May 23, 2014

I had the customer setup Express 2008 and suggested trying 2005 to avoid the 2012 hurtle. However you are saying that Standard to Express even on 2005 or 2008 will be an issue?

0 0
replied on May 23, 2014

Here is more detail from the customer:

 

Trying to migrate from Laserfiche 7 on SQL Server 2000 to Laserfiche 9.1 on SQL Server 2012 Express.

· First migration failed because a direct path from any
standard SQL Server to an Express SQL Server is not supported.
· Next I did a backup and restored the 2000 database into SQL
Server 2008R2 Express. Then backed up from there and restored into
2012 Express.
· Tried the migration again with both databases on the same
SS2012 Express instance.
· In the migration log (see attached) I get some messages
related to document names with slashes in the name; we’ll have to fix
those in the old database first I think.
· Then at the bottom of the attached log you see the real
problem:
o Table: DOC Unable to read data from Doc table in
source database: Invalid column name 'LocDb'.
· I found this KB article on the laserfiche site:
https://support.laserfiche.com/KB/1011210. The workaround says to
make sure you have the correct edition of SQL Server.

0 0
replied on May 23, 2014

So as it stands the customer can get the db attached but the Schema is not recognized by the Laserfiche Migration Wizard. Is their a method to update the schema, or should I say downgrade the schema, from Standard to Express.

0 0
replied on May 26, 2014

Would it be feasible to detach the database from the full SQL 2000 and first attach it to SQL Express 2000 or 2005.

Then perform the LF migration from SQL Express 2005 to SQL Express 2012

0 0
replied on May 27, 2014

Andy,

As I understand it, the Schema for the Express is a bit different from that of Full SQL.  The problem is not with what DB server type the DB is attached, but rather that the migration utility does not have routines in it to convert from Full SQL schema to the Express Schema.

0 0
replied on May 27, 2014

Thanks, Bert.

I had hoped that by attaching a Full SQL db to SQL Express the schema would configure to match SQL Express.

Looks like that isn't the case and it may need some sort of script to run if there are extra tables, etc.

0 0
replied on July 16, 2015

We just ran into this issue too, wanting to convert a 7.2 database from an existing repository from SQL Standard 2000 to SQL Express 2014. Is it still accurate that there are no conversion scripts to do this?

0 0
replied on July 17, 2015

Hi Brian,

There's no change to my original answer from last year. Could you provide some information as to why you are looking to go from full SQL to SQL Express? Thanks!

0 0
replied on July 17, 2015

Sure; we've had a small implementation on a regular SQL Server for the past 6-7 years (on LF 7.2). We determined that we could get by with SQL Server Express given our size and growth path. But different schemas and no conversion tool is a showstopper. So we bit the bullet and purchased the full version of SQL Server 2014.  Thanks for confirming "you can't get thar from here". -brian

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.