Sql server 2000 with compatibility 65

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Older Versions of SQL (v6.5, v6.0, v4.2) » Older Versions of SQL (v6.5, v6.0, v4.2) » Sql server 2000 with compatibility 65

Sql server 2000 with compatibility 65

Rate Topic

Display Mode

Topic Options

Author

Message

Vinay Thakur-585143

Posted Wednesday, May 06, 2009 9:47 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, April 16, 2013 4:05 PM
Points: 1,514, Visits: 720

Hi

We have a lagecy system where long back some one migrated from sql server 65 to sql server 2000(80) but they kept comptatibility level to 65.

I could see their are several tables with ansi null off. so I cannot create index on view.

and old dba told me not to change this... can anybody tell me what would be the impact on application if we change it to 80 ie. what precousions I should take todo so.

Appriciate any help.

Thanx
Vinay

Thanx.
Vinay

http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay

Post #711239

Jeremy Brown

Posted Wednesday, May 06, 2009 9:59 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, April 19, 2013 10:07 AM
Points: 190, Visits: 244

ANSI_NULL property identifies how NULL values are evaluated by SQL Server. Basically query behavior changes with this value set.

ANSI SQL-92 standard basically states that when comparing two null values, the result will be FALSE. SQL Server can be configured to evaluate this condition to be TRUE with this setting turned off.

ANSI SQL-92: NULL <> NULL
Non ANSI SQL-92: NULL=NULL

More information on this can be found in SQL Server's books online articles.

http://msdn.microsoft.com/en-us/library/ms188048.aspx

With all that being said, the answer to your question specifically is - setting this database to compatability mode 80 may result in some unexpected query result sets, especially if you're changing the way NULL values are evaulated by the query engine.

Also, be aware with an indexed view, SQL Server Standard Edition handles this somewhat differently than SQL Server Enterprise. Basically the Standard edition - you have to specifiy in the query code (or by use of a view, tbf, or stored proc) to use the indexed view, while in Enterprise, SQL Server automatically uses the indexed view.

http://msdn.microsoft.com/en-us/library/ms181151.aspx

"Indexed views can be created in any edition of SQL Server. In SQL Server Enterprise, the query optimizer automatically considers the indexed view. To use an indexed view in all other editions, the NOEXPAND table hint must be used."

Post #711250

Vinay Thakur-585143

Posted Wednesday, May 06, 2009 10:21 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, April 16, 2013 4:05 PM
Points: 1,514, Visits: 720

I eloborate my question:

1. What would be impact of changing sql server 65 compatibility to 80?
2. All tables are having ansi NULL off, that will not change automatically, Do I have to create new tables and with ansi null on and export data?
3. Application is old and working good, what would be impact? do we have to change the application where "=NULL" with something like isnull() or is null?
4. We are having " in application, (quate identifier on " ) so do we have to change the application with ',

This is all i could think now....add on more if anyone feel so.

Appriciate any help.

Vinay

Thanx.
Vinay

http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay

Post #711268

Vinay Thakur-585143

Posted Wednesday, May 06, 2009 10:23 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, April 16, 2013 4:05 PM
Points: 1,514, Visits: 720

I elaborate my question:

1. What would be impact of changing sql server 65 compatibility to 80?
2. All tables are having ansi NULL off, that will not change automatically, Do I have to create new tables and with ansi null on and export data?
3. Application is old and working good, what would be impact? do we have to change the application where "=NULL" with something like isnull() or is null?
4. We are having " in application, (quote identifier on " ) so do we have to change the application with ',

This is all i could think now....add on more if anyone feel so.

Appreciate any help.

Vinay

Thanx.
Vinay

http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay

Post #711272

tosscrosby

Posted Wednesday, May 13, 2009 12:27 PM

SSCrazy

Group: General Forum Members
Last Login: Tuesday, April 19, 2011 7:31 AM
Points: 2,832, Visits: 5,316

Vinay (5/6/2009)

I elaborate my question:

3. Application is old and working good, what would be impact?

Appreciate any help.

Vinay

Vinay, I can't remember back to 6.5, the first SQL platform I started on. My question is, if it's "working good", what benefit do you think you'll acheive by moving it to SQL2000 compatability? What's the underlying thinking that is driving your quest, simply an indexed view? If it's a canned application, is it certified on a SQL 2000 platform?

-- You can't be late until you show up.

Post #716297

Vinay Thakur-585143

Posted Wednesday, May 13, 2009 2:21 PM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, April 16, 2013 4:05 PM
Points: 1,514, Visits: 720

Thanx Terry for reply.

System is doing good so far, but I feel if we could change the compatibility. It will generate good compile and execition plan and will work better.

Long back old DBA's migrated to 2000, but the tables still has Ansi NULL off (other settings as well). was thinking to improve the performance and efficiency of the system but looks like it will be a BIG task includes application level changes... so I also think its better to go as it is going... and try to handle what all is possible(As business is not ready to invest more on this).

Thanx
Vinay

Thanx.
Vinay

http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay

Post #716420

« Prev Topic | Next Topic »

Permissions