I have been migrating Databases from a SQL Server 7.0 Instance to a 2000 Instance. Basically the method I use is as follows:
a)Create a new Database on the Destination Server (same name as the Source) When I create the new Database on my destination server, the compatibility mode is '80' and the source is always '70'
b) do a 'revlogin' on the Source Server and use the output from that query to recreate the logins on the destination server
c) make sure that the default DB for the newly creates logins are correct and change them if necessary
d) Backup the DB on the Source Server and Restore it to the Destination Server.
e) Check login permissions and fix any orphaned users - usually I don't find any that need to be fixed, but I always check.
I've read BOL on Changing the compatibility mode on the Database... but I'm still unsure when I would have to do this and why?????? SHOULD I be changing the compatiblity mode from 80 to 70 when migrating Databases from 7.0 to 2000?? Any advice on moving DBs in this manner would be appreciated.sounds like you're doing it correctly. I always changed the compatability mode as the very last step...I know I've had an issue when I didn't change it - at one point, but it happened a very long time ago, and I can't remember the specifics - I think it had something to do with Quoted Identifiers...if you have procs that use double quotes instead of single quotes to identify text fields...it was pretty bizarre.|||Thanks much for the reply!
Showing posts with label compatibility. Show all posts
Showing posts with label compatibility. Show all posts
Thursday, March 29, 2012
Database Compatibility Level
Hi,
I don't know if anyone can help but I'm trying to understand exactly how
setting database compatibility works. Has anyone seen a good explanation of
this (I've spent ages using google/msdn etc trying to find a detailed
description)?
I want to attach a couple of SQK 2K databases to a SQL Server 2005 cluster.
These databases are not supported by third parties on 2005. Would setting the
database compatibility to 80 (S2K) make sure they are run as a 2K database on
2005?
This would save me maintaining two installation of SQl server (2K and 2005).
I'm not sure I totally understand this functionality.
Thanks,
Jason.
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
That is a legal question that you should ask of your 3rd party. Even when
emulating a prior version, there is no guarantee that a particular query
will return the same results in the same way using the enhancements /
changes in the database engine. The compatibility setting will not affect
the system stored procedures - on which your 3rd party system may depend.
Even MS carefully constrains the compability claims. InBOL, MS says, "Sets
certain database behaviors to be compatible with the specified earlier
version of Microsoft SQL ServerT. "
|||Hi Jason
All databases available through a SQL 2005 server are SQL 2005 databases.
Setting a compatibility level just makes the database more compatible with
earlier versions, but they are still SQL 2005 databases.
The differences allows with the compatibility level are mainly how certain
keywords are used, and what object names are allowed. The architecture of
the database is a SQL 2005 architecture and is a 3rd party can't deal with
the architectural changes in SQL 2005, they won't be able to deal with a SQL
2005 database in a lower compatibility level.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"JayMG" <JayMG@.discussions.microsoft.com> wrote in message
news:E2D65A62-9F3D-454F-90CE-75A9C3E21F1B@.microsoft.com...
> Hi,
> I don't know if anyone can help but I'm trying to understand exactly how
> setting database compatibility works. Has anyone seen a good explanation
> of
> this (I've spent ages using google/msdn etc trying to find a detailed
> description)?
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
> This would save me maintaining two installation of SQl server (2K and
> 2005).
> I'm not sure I totally understand this functionality.
> Thanks,
> Jason.
>
I don't know if anyone can help but I'm trying to understand exactly how
setting database compatibility works. Has anyone seen a good explanation of
this (I've spent ages using google/msdn etc trying to find a detailed
description)?
I want to attach a couple of SQK 2K databases to a SQL Server 2005 cluster.
These databases are not supported by third parties on 2005. Would setting the
database compatibility to 80 (S2K) make sure they are run as a 2K database on
2005?
This would save me maintaining two installation of SQl server (2K and 2005).
I'm not sure I totally understand this functionality.
Thanks,
Jason.
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
That is a legal question that you should ask of your 3rd party. Even when
emulating a prior version, there is no guarantee that a particular query
will return the same results in the same way using the enhancements /
changes in the database engine. The compatibility setting will not affect
the system stored procedures - on which your 3rd party system may depend.
Even MS carefully constrains the compability claims. InBOL, MS says, "Sets
certain database behaviors to be compatible with the specified earlier
version of Microsoft SQL ServerT. "
|||Hi Jason
All databases available through a SQL 2005 server are SQL 2005 databases.
Setting a compatibility level just makes the database more compatible with
earlier versions, but they are still SQL 2005 databases.
The differences allows with the compatibility level are mainly how certain
keywords are used, and what object names are allowed. The architecture of
the database is a SQL 2005 architecture and is a 3rd party can't deal with
the architectural changes in SQL 2005, they won't be able to deal with a SQL
2005 database in a lower compatibility level.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"JayMG" <JayMG@.discussions.microsoft.com> wrote in message
news:E2D65A62-9F3D-454F-90CE-75A9C3E21F1B@.microsoft.com...
> Hi,
> I don't know if anyone can help but I'm trying to understand exactly how
> setting database compatibility works. Has anyone seen a good explanation
> of
> this (I've spent ages using google/msdn etc trying to find a detailed
> description)?
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
> This would save me maintaining two installation of SQl server (2K and
> 2005).
> I'm not sure I totally understand this functionality.
> Thanks,
> Jason.
>
Database Compatibility Level
Hi,
I don't know if anyone can help but I'm trying to understand exactly how
setting database compatibility works. Has anyone seen a good explanation of
this (I've spent ages using google/msdn etc trying to find a detailed
description)?
I want to attach a couple of SQK 2K databases to a SQL Server 2005 cluster.
These databases are not supported by third parties on 2005. Would setting th
e
database compatibility to 80 (S2K) make sure they are run as a 2K database o
n
2005?
This would save me maintaining two installation of SQl server (2K and 2005).
I'm not sure I totally understand this functionality.
Thanks,
Jason.> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
That is a legal question that you should ask of your 3rd party. Even when
emulating a prior version, there is no guarantee that a particular query
will return the same results in the same way using the enhancements /
changes in the database engine. The compatibility setting will not affect
the system stored procedures - on which your 3rd party system may depend.
Even MS carefully constrains the compability claims. InBOL, MS says, "Sets
certain database behaviors to be compatible with the specified earlier
version of Microsoft SQL ServerT. "|||Hi Jason
All databases available through a SQL 2005 server are SQL 2005 databases.
Setting a compatibility level just makes the database more compatible with
earlier versions, but they are still SQL 2005 databases.
The differences allows with the compatibility level are mainly how certain
keywords are used, and what object names are allowed. The architecture of
the database is a SQL 2005 architecture and is a 3rd party can't deal with
the architectural changes in SQL 2005, they won't be able to deal with a SQL
2005 database in a lower compatibility level.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"JayMG" <JayMG@.discussions.microsoft.com> wrote in message
news:E2D65A62-9F3D-454F-90CE-75A9C3E21F1B@.microsoft.com...
> Hi,
> I don't know if anyone can help but I'm trying to understand exactly how
> setting database compatibility works. Has anyone seen a good explanation
> of
> this (I've spent ages using google/msdn etc trying to find a detailed
> description)?
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
> This would save me maintaining two installation of SQl server (2K and
> 2005).
> I'm not sure I totally understand this functionality.
> Thanks,
> Jason.
>sql
I don't know if anyone can help but I'm trying to understand exactly how
setting database compatibility works. Has anyone seen a good explanation of
this (I've spent ages using google/msdn etc trying to find a detailed
description)?
I want to attach a couple of SQK 2K databases to a SQL Server 2005 cluster.
These databases are not supported by third parties on 2005. Would setting th
e
database compatibility to 80 (S2K) make sure they are run as a 2K database o
n
2005?
This would save me maintaining two installation of SQl server (2K and 2005).
I'm not sure I totally understand this functionality.
Thanks,
Jason.> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
That is a legal question that you should ask of your 3rd party. Even when
emulating a prior version, there is no guarantee that a particular query
will return the same results in the same way using the enhancements /
changes in the database engine. The compatibility setting will not affect
the system stored procedures - on which your 3rd party system may depend.
Even MS carefully constrains the compability claims. InBOL, MS says, "Sets
certain database behaviors to be compatible with the specified earlier
version of Microsoft SQL ServerT. "|||Hi Jason
All databases available through a SQL 2005 server are SQL 2005 databases.
Setting a compatibility level just makes the database more compatible with
earlier versions, but they are still SQL 2005 databases.
The differences allows with the compatibility level are mainly how certain
keywords are used, and what object names are allowed. The architecture of
the database is a SQL 2005 architecture and is a 3rd party can't deal with
the architectural changes in SQL 2005, they won't be able to deal with a SQL
2005 database in a lower compatibility level.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"JayMG" <JayMG@.discussions.microsoft.com> wrote in message
news:E2D65A62-9F3D-454F-90CE-75A9C3E21F1B@.microsoft.com...
> Hi,
> I don't know if anyone can help but I'm trying to understand exactly how
> setting database compatibility works. Has anyone seen a good explanation
> of
> this (I've spent ages using google/msdn etc trying to find a detailed
> description)?
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
> This would save me maintaining two installation of SQl server (2K and
> 2005).
> I'm not sure I totally understand this functionality.
> Thanks,
> Jason.
>sql
database compatibility level
A couple of weeks ago we had upgraded our SQL Server 6.5
to ver. 7.0. We've just observed that for all of our
databases, the database compatibility level remains at 65.
My concern here is... can we change this compatibility
level to 70 on the fly? Would this incur an outage of any
sort? Are there any precautions that I should be aware of
before set the database compatibility level to 70?
Thanks in advance for your help and suggestions.You can certainly change on the fly, but there will be some semantic =changes to the SQL that may catch out your application. BOL has a =summary of the differences, but it is things like:
SELECT 'a' + '' + 'b' -- Nothe there is no space between the middle pair =of single quotes -
At 65 will give 'a b' - ie the zerolength string is interpreted as a =single space.
At 7 will give 'ab' - which I would say is right.
Others such as =3D NULL behaving non-standard at 65 but fixed at 7 can =catch you if the app uses it.
BOL has a description of all the differences.
Mike John
"Rob" <rhchin@.hotmail.com> wrote in message =news:01fc01c3425c$c76bc8a0$a301280a@.phx.gbl...
> A couple of weeks ago we had upgraded our SQL Server 6.5 > to ver. 7.0. We've just observed that for all of our > databases, the database compatibility level remains at 65.
> > My concern here is... can we change this compatibility > level to 70 on the fly? Would this incur an outage of any > sort? Are there any precautions that I should be aware of > before set the database compatibility level to 70?
> > Thanks in advance for your help and suggestions.
to ver. 7.0. We've just observed that for all of our
databases, the database compatibility level remains at 65.
My concern here is... can we change this compatibility
level to 70 on the fly? Would this incur an outage of any
sort? Are there any precautions that I should be aware of
before set the database compatibility level to 70?
Thanks in advance for your help and suggestions.You can certainly change on the fly, but there will be some semantic =changes to the SQL that may catch out your application. BOL has a =summary of the differences, but it is things like:
SELECT 'a' + '' + 'b' -- Nothe there is no space between the middle pair =of single quotes -
At 65 will give 'a b' - ie the zerolength string is interpreted as a =single space.
At 7 will give 'ab' - which I would say is right.
Others such as =3D NULL behaving non-standard at 65 but fixed at 7 can =catch you if the app uses it.
BOL has a description of all the differences.
Mike John
"Rob" <rhchin@.hotmail.com> wrote in message =news:01fc01c3425c$c76bc8a0$a301280a@.phx.gbl...
> A couple of weeks ago we had upgraded our SQL Server 6.5 > to ver. 7.0. We've just observed that for all of our > databases, the database compatibility level remains at 65.
> > My concern here is... can we change this compatibility > level to 70 on the fly? Would this incur an outage of any > sort? Are there any precautions that I should be aware of > before set the database compatibility level to 70?
> > Thanks in advance for your help and suggestions.
Database Compatibility Level
Hi,
I don't know if anyone can help but I'm trying to understand exactly how
setting database compatibility works. Has anyone seen a good explanation of
this (I've spent ages using google/msdn etc trying to find a detailed
description)?
I want to attach a couple of SQK 2K databases to a SQL Server 2005 cluster.
These databases are not supported by third parties on 2005. Would setting the
database compatibility to 80 (S2K) make sure they are run as a 2K database on
2005?
This would save me maintaining two installation of SQl server (2K and 2005).
I'm not sure I totally understand this functionality.
Thanks,
Jason.> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
That is a legal question that you should ask of your 3rd party. Even when
emulating a prior version, there is no guarantee that a particular query
will return the same results in the same way using the enhancements /
changes in the database engine. The compatibility setting will not affect
the system stored procedures - on which your 3rd party system may depend.
Even MS carefully constrains the compability claims. InBOL, MS says, "Sets
certain database behaviors to be compatible with the specified earlier
version of Microsoft® SQL ServerT. "|||Hi Jason
All databases available through a SQL 2005 server are SQL 2005 databases.
Setting a compatibility level just makes the database more compatible with
earlier versions, but they are still SQL 2005 databases.
The differences allows with the compatibility level are mainly how certain
keywords are used, and what object names are allowed. The architecture of
the database is a SQL 2005 architecture and is a 3rd party can't deal with
the architectural changes in SQL 2005, they won't be able to deal with a SQL
2005 database in a lower compatibility level.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"JayMG" <JayMG@.discussions.microsoft.com> wrote in message
news:E2D65A62-9F3D-454F-90CE-75A9C3E21F1B@.microsoft.com...
> Hi,
> I don't know if anyone can help but I'm trying to understand exactly how
> setting database compatibility works. Has anyone seen a good explanation
> of
> this (I've spent ages using google/msdn etc trying to find a detailed
> description)?
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
> This would save me maintaining two installation of SQl server (2K and
> 2005).
> I'm not sure I totally understand this functionality.
> Thanks,
> Jason.
>
I don't know if anyone can help but I'm trying to understand exactly how
setting database compatibility works. Has anyone seen a good explanation of
this (I've spent ages using google/msdn etc trying to find a detailed
description)?
I want to attach a couple of SQK 2K databases to a SQL Server 2005 cluster.
These databases are not supported by third parties on 2005. Would setting the
database compatibility to 80 (S2K) make sure they are run as a 2K database on
2005?
This would save me maintaining two installation of SQl server (2K and 2005).
I'm not sure I totally understand this functionality.
Thanks,
Jason.> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
That is a legal question that you should ask of your 3rd party. Even when
emulating a prior version, there is no guarantee that a particular query
will return the same results in the same way using the enhancements /
changes in the database engine. The compatibility setting will not affect
the system stored procedures - on which your 3rd party system may depend.
Even MS carefully constrains the compability claims. InBOL, MS says, "Sets
certain database behaviors to be compatible with the specified earlier
version of Microsoft® SQL ServerT. "|||Hi Jason
All databases available through a SQL 2005 server are SQL 2005 databases.
Setting a compatibility level just makes the database more compatible with
earlier versions, but they are still SQL 2005 databases.
The differences allows with the compatibility level are mainly how certain
keywords are used, and what object names are allowed. The architecture of
the database is a SQL 2005 architecture and is a 3rd party can't deal with
the architectural changes in SQL 2005, they won't be able to deal with a SQL
2005 database in a lower compatibility level.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"JayMG" <JayMG@.discussions.microsoft.com> wrote in message
news:E2D65A62-9F3D-454F-90CE-75A9C3E21F1B@.microsoft.com...
> Hi,
> I don't know if anyone can help but I'm trying to understand exactly how
> setting database compatibility works. Has anyone seen a good explanation
> of
> this (I've spent ages using google/msdn etc trying to find a detailed
> description)?
> I want to attach a couple of SQK 2K databases to a SQL Server 2005
> cluster.
> These databases are not supported by third parties on 2005. Would setting
> the
> database compatibility to 80 (S2K) make sure they are run as a 2K database
> on
> 2005?
> This would save me maintaining two installation of SQl server (2K and
> 2005).
> I'm not sure I totally understand this functionality.
> Thanks,
> Jason.
>
database compatibility between sql 2005 standard v/s sql 2005 64 bit
I am a newbie developing a web site. My local machine has sql 2005 standard edition on it. The host that I am trying to use only has sql 2005 64 bit version.
would I be able to do the use the same database between the two ( i.e. once my site is running at host, would I be able to download the database on my local machine, make changes to my site and then upload again on the hose without any glitches?). In addition, how about sql express doing the same with sql 2005 64 bit.
Thanks a lot for taking time to read the post.
get a new host lol...come to my employeer, www.hosting.com. we offer express & std 32BIT lol who only offers 64bit.Database compatibility between MSDE and SQL Server 2000
I have a database that was created in SQL Server 2000. Would there be any
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!
hi Anushree,
"Anushree Laturkar" <anushree.laturkar@.bindview.com> ha scritto nel
messaggio news:%23WE5kkx7EHA.3504@.TK2MSFTNGP12.phx.gbl
> I have a database that was created in SQL Server 2000. Would there be
> any issues if I used this database in MSDE? Does anyone know of any
> document regarding this? All the articles I have read talk about MSDE
> databases being compatible with SQL Server 2000. None of them
> discussed the reverse case.
> Thanks in advance!
MSDE 2000 and SQL Server 2000 databases are compatible as the engine is the
same.. MSDE only has "added" features in the Storage Engine regarding checks
for datab files not exceeding 2gb upper limit
but the core architechture is the same, so you can move users SQL Server
2000 databases to MSDE 2000 and vice versa..
the same applied service pack level is appreciated
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!
hi Anushree,
"Anushree Laturkar" <anushree.laturkar@.bindview.com> ha scritto nel
messaggio news:%23WE5kkx7EHA.3504@.TK2MSFTNGP12.phx.gbl
> I have a database that was created in SQL Server 2000. Would there be
> any issues if I used this database in MSDE? Does anyone know of any
> document regarding this? All the articles I have read talk about MSDE
> databases being compatible with SQL Server 2000. None of them
> discussed the reverse case.
> Thanks in advance!
MSDE 2000 and SQL Server 2000 databases are compatible as the engine is the
same.. MSDE only has "added" features in the Storage Engine regarding checks
for datab files not exceeding 2gb upper limit
but the core architechture is the same, so you can move users SQL Server
2000 databases to MSDE 2000 and vice versa..
the same applied service pack level is appreciated
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Database compatibility between MSDE and SQL Server 2000
I have a database that was created in SQL Server 2000. Would there be any
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!MSDE and SQL Server is the same. There are some features not available on MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_1cdv.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_1cdv.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>sql
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!MSDE and SQL Server is the same. There are some features not available on MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_1cdv.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_1cdv.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>sql
Database compatibility between MSDE and SQL Server 2000
I have a database that was created in SQL Server 2000. Would there be any
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!
MSDE and SQL Server is the same. There are some features not available on MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en...ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>
|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en...ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!
MSDE and SQL Server is the same. There are some features not available on MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en...ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>
|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en...ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>
Database compatibility between MSDE and SQL Server 2000
I have a database that was created in SQL Server 2000. Would there be any
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!MSDE and SQL Server is the same. There are some features not available on MS
DE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/e..._ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases bei
ng
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/e..._ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!MSDE and SQL Server is the same. There are some features not available on MS
DE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/e..._ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases bei
ng
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/e..._ar_ts_1cdv.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>
Tuesday, March 27, 2012
Database Comatability level after Replication set up
Hello
We moved SQL Server 2000 Databases to SQL Server 2005 Instance. If we change the Database compatibility level from 80 to 90, shall Replication will Fail? or any consequencies will arise? please advice. Thanks,
refer link for the features ,
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/508c686d-2bd4-41ba-8602-48ebca266659.htm
have you already configured your db in sql 2000 for replication and then moved to 2k5? if you are going to newly set it in sql 2005 it shudnt be a problem.........if uyou change the compatability to 90 many features provided in link will be supported also few 2k features will be depreciated i believe....further performance dashboard is supported only in 90.......
Subscribe to:
Posts (Atom)