Compatibility Level Question

I am a little confused on the importance of the Compatability Level setting.
I have a database originally created in SQL Server 2000 that I backed up and
then restored to SQL Server 2005. The compatibility level is currently set
at 80 (SQL 2000). I would like to change this to 90 (SQL 2005) but am not
sure of the ramifications of doing this. Can someone tell me of any negative
issues I should be aware of by doing this? I would like to treat this
database as if it were created as a SQL 2005 database (IOW, I don't need any
2000 support or compatibility).
Amos.Check out the description of sp_dbcmptlevel in the SQL 2005 Books Online for
a description of the behavior differences between 80 and 90. If you see not
changes that affect your app, you are probably ok but it's always a good
idea to test.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Amos Soma" <amos_j_soma@.yahoo.com> wrote in message
news:up7T4sgEGHA.2648@.TK2MSFTNGP11.phx.gbl...
>I am a little confused on the importance of the Compatability Level
>setting. I have a database originally created in SQL Server 2000 that I
>backed up and then restored to SQL Server 2005. The compatibility level is
>currently set at 80 (SQL 2000). I would like to change this to 90 (SQL
>2005) but am not sure of the ramifications of doing this. Can someone tell
>me of any negative issues I should be aware of by doing this? I would like
>to treat this database as if it were created as a SQL 2005 database (IOW, I
>don't need any 2000 support or compatibility).
> Amos.
>

Compatibility Level Question

I am a little confused on the importance of the Compatability Level setting.
I have a database originally created in SQL Server 2000 that I backed up and
then restored to SQL Server 2005. The compatibility level is currently set
at 80 (SQL 2000). I would like to change this to 90 (SQL 2005) but am not
sure of the ramifications of doing this. Can someone tell me of any negative
issues I should be aware of by doing this? I would like to treat this
database as if it were created as a SQL 2005 database (IOW, I don't need any
2000 support or compatibility).
Amos.
Check out the description of sp_dbcmptlevel in the SQL 2005 Books Online for
a description of the behavior differences between 80 and 90. If you see not
changes that affect your app, you are probably ok but it's always a good
idea to test.
Hope this helps.
Dan Guzman
SQL Server MVP
"Amos Soma" <amos_j_soma@.yahoo.com> wrote in message
news:up7T4sgEGHA.2648@.TK2MSFTNGP11.phx.gbl...
>I am a little confused on the importance of the Compatability Level
>setting. I have a database originally created in SQL Server 2000 that I
>backed up and then restored to SQL Server 2005. The compatibility level is
>currently set at 80 (SQL 2000). I would like to change this to 90 (SQL
>2005) but am not sure of the ramifications of doing this. Can someone tell
>me of any negative issues I should be aware of by doing this? I would like
>to treat this database as if it were created as a SQL 2005 database (IOW, I
>don't need any 2000 support or compatibility).
> Amos.
>

Compatibility Level Question

I am a little confused on the importance of the Compatability Level setting.
I have a database originally created in SQL Server 2000 that I backed up and
then restored to SQL Server 2005. The compatibility level is currently set
at 80 (SQL 2000). I would like to change this to 90 (SQL 2005) but am not
sure of the ramifications of doing this. Can someone tell me of any negative
issues I should be aware of by doing this? I would like to treat this
database as if it were created as a SQL 2005 database (IOW, I don't need any
2000 support or compatibility).
Amos.Check out the description of sp_dbcmptlevel in the SQL 2005 Books Online for
a description of the behavior differences between 80 and 90. If you see not
changes that affect your app, you are probably ok but it's always a good
idea to test.
Hope this helps.
Dan Guzman
SQL Server MVP
"Amos Soma" <amos_j_soma@.yahoo.com> wrote in message
news:up7T4sgEGHA.2648@.TK2MSFTNGP11.phx.gbl...
>I am a little confused on the importance of the Compatability Level
>setting. I have a database originally created in SQL Server 2000 that I
>backed up and then restored to SQL Server 2005. The compatibility level is
>currently set at 80 (SQL 2000). I would like to change this to 90 (SQL
>2005) but am not sure of the ramifications of doing this. Can someone tell
>me of any negative issues I should be aware of by doing this? I would like
>to treat this database as if it were created as a SQL 2005 database (IOW, I
>don't need any 2000 support or compatibility).
> Amos.
>

compatability question

We have a Win 2000 Server running MS SQL Server 7.0.
The application using the SQL database is not compatible with SQL 2000.
We want to upgrade the OS on the server to Win 2003.
Is Win 2003 compatible with SQL 7.0?
Thanks
ccoatesI am pretty sure SQL 7.0 is not supported on Win2003. SQL 2000 is pretty
much backward compatible so you might want to just fix what the issue is
with 2000.
Andrew J. Kelly
SQL Server MVP
"Chris Coates" <ccoates@.gfs.com> wrote in message
news:OAd4jEc6DHA.3860@.tk2msftngp13.phx.gbl...

quote:

---

> We have a Win 2000 Server running MS SQL Server 7.0.
> The application using the SQL database is not compatible with SQL 2000.
> We want to upgrade the OS on the server to Win 2003.
> Is Win 2003 compatible with SQL 7.0?
> Thanks
> ccoates
>

---

compatability question

We have a Win 2000 Server running MS SQL Server 7.0.
The application using the SQL database is not compatible with SQL 2000.
We want to upgrade the OS on the server to Win 2003.
Is Win 2003 compatible with SQL 7.0?
Thanks
ccoatesI am pretty sure SQL 7.0 is not supported on Win2003. SQL 2000 is pretty
much backward compatible so you might want to just fix what the issue is
with 2000.
--
Andrew J. Kelly
SQL Server MVP
"Chris Coates" <ccoates@.gfs.com> wrote in message
news:OAd4jEc6DHA.3860@.tk2msftngp13.phx.gbl...
> We have a Win 2000 Server running MS SQL Server 7.0.
> The application using the SQL database is not compatible with SQL 2000.
> We want to upgrade the OS on the server to Win 2003.
> Is Win 2003 compatible with SQL 7.0?
> Thanks
> ccoates
>

compatability level

i restored couple of databases from 2000 onto 2005.

Should i change the compatability level of these databases to 90?

Would it help/harm?

If your application has no issues with working against a SQL Server 2005 database I would definitely change the compatibility level to 90. This enables you to fully use the benefits of SQL Server 2005. Make sure you run the databases through the Upgrade Advisor first.|||upgrade advisor?|||Check out this link

Compatability between MSSQL server and MSDE??

Can we install both MSSQL and MSDE in the same server? And can they operate
at the same time? Just in case when the CAL is exceeded in the SQL server I
can use MSDE as alternative for other applications.
Yes, you can run them at the same time. Only one can be a default instance, the other(s) need to be
named instances.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AdrianY" <AdrianY@.discussions.microsoft.com> wrote in message
news:8B83C9E8-0449-4ECA-85D2-7556D5121F5E@.microsoft.com...
> Can we install both MSSQL and MSDE in the same server? And can they operate
> at the same time? Just in case when the CAL is exceeded in the SQL server I
> can use MSDE as alternative for other applications.

Compatability between MSSQL server and MSDE??

Can we install both MSSQL and MSDE in the same server? And can they operate
at the same time? Just in case when the CAL is exceeded in the SQL server I
can use MSDE as alternative for other applications.Yes, you can run them at the same time. Only one can be a default instance, the other(s) need to be
named instances.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AdrianY" <AdrianY@.discussions.microsoft.com> wrote in message
news:8B83C9E8-0449-4ECA-85D2-7556D5121F5E@.microsoft.com...
> Can we install both MSSQL and MSDE in the same server? And can they operate
> at the same time? Just in case when the CAL is exceeded in the SQL server I
> can use MSDE as alternative for other applications.

Compatability : SQL Server 2005 Management Studio

Hello Everyone,

I have a Web Host which uses SQL Server 2000. I can use their interface and make tables and procedures, but I wanted to use some sort of graphical tool...Is it possible to use SQL Server 2005 Studio with SQL 2000.

I'm really new to SQL Server as my past experience is largely with Oracle....and there for the same purpose I can use SQL Navigator or TOAD....

IF SQL Server 2005 Studio wont work can someone please suggest a tool I can use to create tables and procedures on the remote server..

Thanks,

Harsimrat

Hi,

yes you can use SQL Server 2005 Management Studio for administring SQL2k databases, I do that also with my host databases in the web. If you don′t have SQL Server 2005 Management Studio you can also use one of the tools mentioned here:

http://www.aspfaq.com/2442

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Awesome,

Thanks

Harsimrat