September 6, 2001 at 7:38 am
BOL has become harder to use in this last edition. A problem is that the new functions and enhancements are not clearly marked to define which version of SQL Server will allow its use.
A simple header at the beginning of each content page (like Knowledge Base) would show quickly which features will work with which version.
For example, we just picked up a project in SQL 6.5. One of my developers came in looking puzzled because his SET statement didn't work. I changed it to the older SELECT and his T-SQL code worked.
Yesterday I had a discussion with a new developer about @@Identity. The first question I asked was which version of SQL Server. An hour later he came to me and asked why IDENT_CURRENT didn't work for him.
Thanks.
Patrick Birch
MCT, MCDBA, MCSD
Quand on parle du loup, on en voit la queue
September 7, 2001 at 3:10 pm
Im lucky to be able to avoid this, working on SQL2K only. You might try submitting this to MS at sqlwish@microsoft.com.
Andy
September 14, 2001 at 10:22 am
Thanks. I sent off an email.
I have several clients who hold on dearly to their 6.5 servers. I would love to work on only one version.
quote:
Im lucky to be able to avoid this, working on SQL2K only. You might try submitting this to MS at sqlwish@microsoft.com.Andy
Patrick Birch
MCT, MCDBA, MCSD
Quand on parle du loup, on en voit la queue
September 14, 2001 at 4:18 pm
I know it costs $$, but you can run SQL 2000 with a db in 6.5 compatability. Might provide some reasons to upgrade. The query performance will only increase.
Steve Jones
September 17, 2001 at 5:45 pm
Patrick,
Is this you? http://www.microsoft.com/trainingandservices/default.asp?PageID=training&SubSite=success
Andy
September 28, 2001 at 8:31 am
Andy,
Yes, that's me.
Pat
quote:
Patrick,Is this you? http://www.microsoft.com/trainingandservices/default.asp?PageID=training&SubSite=success
Andy
Patrick Birch
MCT, MCDBA, MCSD
Quand on parle du loup, on en voit la queue
September 28, 2001 at 8:34 am
Yes. $$$. My clients seem to have none to spend on upgrading. They will spend $$$ on the tortuous stored procedures though.
The jump from SQL Server 2000 to SQL Server 6.5 is sometimes jarring.
Pat
quote:
I know it costs $$, but you can run SQL 2000 with a db in 6.5 compatability. Might provide some reasons to upgrade. The query performance will only increase.Steve Jones
Patrick Birch
MCT, MCDBA, MCSD
Quand on parle du loup, on en voit la queue
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply