By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,644 Members | 1,824 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,644 IT Pros & Developers. It's quick & easy.

From MSDE to SQL Server 2005 Express Ed...

P: n/a
Howdy,

My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string, will
any syntax in my existing ASP.NET script/stored procs have to change to
support SQL 2005? Is the migration process painless?

I've searched MSDN but really can't find what I'm looking for.

Thanks,

--
David Lozzi
Web Applications Developer
dlozzi@(remove-this)delphi-ts.com


Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
should be painless.

the most common issue is some quirk in query optimization, but if you were
use msde, this should not be a case. the other is default security changes.

-- bruce (sqlwork.com)

"David Lozzi" <Da********@nospam.nospam> wrote in message
news:Ol*************@TK2MSFTNGP15.phx.gbl...
Howdy,

My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string,
will any syntax in my existing ASP.NET script/stored procs have to change
to support SQL 2005? Is the migration process painless?

I've searched MSDN but really can't find what I'm looking for.

Thanks,

--
David Lozzi
Web Applications Developer
dlozzi@(remove-this)delphi-ts.com

Nov 21 '05 #2

P: n/a
Hi David,

Welcome to use MSDN Managed Newsgroup!

I have also noticed you post a duplicated post in
microsoft.public.sqlserver.programming. To keep the integrity of newsgroup,
I will reply here for your question and follow-up question.

Generally speaking, it would be painless when you are using SQL Server 2005
Express.

However, I would like to inform you the new security feature of SQL Server
2005 - User-Schema Separation. A schema is a collection of database
entities that form a single namespace in SQL Server 2005. A namespace is a
set in which every element has a unique name.

For example, to avoid name collisions, no two tables in the same schema can
have the same name. Two tables can have the same name only if they are in
separate schemas. For more information, check the topic below

User-Schema Separation
http://msdn2.microsoft.com/en-us/library/ms190387.aspx

For example, if you specifying the object accounting.ap.user.reconciliation
in the application, you may need to change it as
accounting.ap.schema.reconciliation accordingly.

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.