Hi,
I have a old VC++ application using DB-Library for connection with sqlserver
6.5. Recently I have migrated the sqlserver from 6.5 to 2000. during
recompilation of the vc++ code, i have a problem with ntwdblib.lib file. I
think it does not match with the SQL 2000 version one.
The SQL 2000 installation CD ships with :-
- ntwdblib.lib | dated:Sunday, August 06, 2000, 8:30:29 AM | 31 kb
- ntwlib.dll | ver:2000.80.194.0 | dated: Sunday, August 06, 2000, 9:51:53
AM | 269kb
Post SQL 2000SP4 installation :-
- ntwlib.dll | ver:2000.80.2039.0 | dated: Wednesday, May 04, 2005, 12:02:26
AM | 284 kb
Currently, I have SQL 2000 SP4 installed.
Please advice me, where can i get the NTWDBLIB.LIB file correponding the
NTWDBLIB.DLL which ships with SP4
Regards,
--ChanduChandu (Chandu@.discussions.microsoft.com) writes:
> I have a old VC++ application using DB-Library for connection with
> sqlserver 6.5. Recently I have migrated the sqlserver from 6.5 to 2000.
> during recompilation of the vc++ code, i have a problem with
> ntwdblib.lib file. I think it does not match with the SQL 2000 version
> one.
> The SQL 2000 installation CD ships with :-
> - ntwdblib.lib | dated:Sunday, August 06, 2000, 8:30:29 AM | 31 kb
> - ntwlib.dll | ver:2000.80.194.0 | dated: Sunday, August 06, 2000, 9:51:53
> AM | 269kb
> Post SQL 2000SP4 installation :-
> - ntwlib.dll | ver:2000.80.2039.0 | dated: Wednesday, May 04, 2005,
> 12:02:26 AM | 284 kb
> Currently, I have SQL 2000 SP4 installed.
> Please advice me, where can i get the NTWDBLIB.LIB file correponding the
> NTWDBLIB.DLL which ships with SP4
What problem do you see? Since Microsofr hardly touches DB-Library at
all these days, I see no reason to assume that the RTM LIB file should
not be OK with the SP4 DLL. I checked on my machine, and I don't have
any newer version of NTWDBLIB.LIB that the one you mention.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks Erland for the reply,
You are right the NTWDBLIB has not changed, the problem is with the linker
of VC++5.0, it needed an upgrade. It works fine now.
thanks,
"Erland Sommarskog" wrote:
> Chandu (Chandu@.discussions.microsoft.com) writes:
> What problem do you see? Since Microsofr hardly touches DB-Library at
> all these days, I see no reason to assume that the RTM LIB file should
> not be OK with the SP4 DLL. I checked on my machine, and I don't have
> any newer version of NTWDBLIB.LIB that the one you mention.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Tuesday, February 14, 2012
Sunday, February 12, 2012
Compatibility between SQL2000 and SQL2005
Will my old applications with standard T-SQL code work againt the new
SQL2005 without modifications ?
KayHi
It depends. Mostly yes, but if you are using any syntax that Microsoft has
been warning will be depricated, or any undocumented functions, no.
You will have to test.
Regards
Mike
"Kay-Christian Hansen" wrote:
> Will my old applications with standard T-SQL code work againt the new
> SQL2005 without modifications ?
> Kay
>
>|||If there is any breaking bits, MS will issue a document before release. Thus
far, I have seen nothing that is not backward compatible in T-SQL. If you
follow good standards, you should not have any problems. There are new
additions to T-SQL in SQL 2005, however, that you might want to move to for
perf, etc.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
****************************************
*******
Think outside the box!
****************************************
*******
"Kay-Christian Hansen" <Kay@.Tempus.no> wrote in message
news:OhbU4zbOFHA.2252@.TK2MSFTNGP15.phx.gbl...
> Will my old applications with standard T-SQL code work againt the new
> SQL2005 without modifications ?
> Kay
>|||There are a few changes, for example with the new schema getup,
INFORMATION_SCHEMA.SCHEMATA doesn't work like it currently does in 2000.
There are also some very forceful changes to non-ansi outer joins (*=, =*).
For the most part, backward compatibility is pristine, but there are several
other things going forward that, while you don't have to deal with it right
away, you should definitely visit before the next version after 2005.
You really should be asking this kind of question in the SQL Server 2005
newsgroups.
http://www.aspfaq.com/sql2005/show.asp?id=1
This is my signature. It is a general reminder.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Kay-Christian Hansen" <Kay@.Tempus.no> wrote in message
news:OhbU4zbOFHA.2252@.TK2MSFTNGP15.phx.gbl...
> Will my old applications with standard T-SQL code work againt the new
> SQL2005 without modifications ?
> Kay
>
SQL2005 without modifications ?
KayHi
It depends. Mostly yes, but if you are using any syntax that Microsoft has
been warning will be depricated, or any undocumented functions, no.
You will have to test.
Regards
Mike
"Kay-Christian Hansen" wrote:
> Will my old applications with standard T-SQL code work againt the new
> SQL2005 without modifications ?
> Kay
>
>|||If there is any breaking bits, MS will issue a document before release. Thus
far, I have seen nothing that is not backward compatible in T-SQL. If you
follow good standards, you should not have any problems. There are new
additions to T-SQL in SQL 2005, however, that you might want to move to for
perf, etc.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
****************************************
*******
Think outside the box!
****************************************
*******
"Kay-Christian Hansen" <Kay@.Tempus.no> wrote in message
news:OhbU4zbOFHA.2252@.TK2MSFTNGP15.phx.gbl...
> Will my old applications with standard T-SQL code work againt the new
> SQL2005 without modifications ?
> Kay
>|||There are a few changes, for example with the new schema getup,
INFORMATION_SCHEMA.SCHEMATA doesn't work like it currently does in 2000.
There are also some very forceful changes to non-ansi outer joins (*=, =*).
For the most part, backward compatibility is pristine, but there are several
other things going forward that, while you don't have to deal with it right
away, you should definitely visit before the next version after 2005.
You really should be asking this kind of question in the SQL Server 2005
newsgroups.
http://www.aspfaq.com/sql2005/show.asp?id=1
This is my signature. It is a general reminder.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Kay-Christian Hansen" <Kay@.Tempus.no> wrote in message
news:OhbU4zbOFHA.2252@.TK2MSFTNGP15.phx.gbl...
> Will my old applications with standard T-SQL code work againt the new
> SQL2005 without modifications ?
> Kay
>
Labels:
againt,
applications,
code,
compatibility,
database,
microsoft,
modifications,
mysql,
newsql2005,
old,
oracle,
server,
sql,
sql2000,
sql2005,
standard,
t-sql
Subscribe to:
Posts (Atom)