Any problems with SQL Server 7 on Win 2003 server?

Are there any known problems with running SQL Server 7 on Win 2003
Server?
Thanks,
--
BillI don't believe it is supported on Win2003. You can certainly run SQL 2000
though.
--
Andrew J. Kelly SQL MVP
"Bill Todd" <no@.no.com> wrote in message
news:rkutc05gvq269u7h3ajlvhqgo15ovuvu9f@.4ax.com...
> Are there any known problems with running SQL Server 7 on Win 2003
> Server?
> Thanks,
> --
> Bill|||As Andrew stated, it is an unsupported configuration. Plus, SQL Server 7.0
is a bit long in the tooth.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Bill Todd" <no@.no.com> wrote in message
news:rkutc05gvq269u7h3ajlvhqgo15ovuvu9f@.4ax.com...
> Are there any known problems with running SQL Server 7 on Win 2003
> Server?
> Thanks,
> --
> Bill|||What is the estimated ship date for SQL Server 2005?
Unfortunately upgrading everything at once is not always possible for
small businesses. The goal is to get current without getting
bankrupt.<g>
Thanks for you help and insight.
--
Bill|||I would go the other way first, if you can. Update the things that run your
apps (SQL Server) and then the OS. It's easier, imho, to get the bugs out
of the app migration first, THEN test an OS upgrade. If you go the other
way it's very difficult to backtrack.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Bill Todd" <no@.no.com> wrote in message
news:ft6uc0d7aluvok902gu3j8hjo7eeuqf37o@.4ax.com...
> What is the estimated ship date for SQL Server 2005?
> Unfortunately upgrading everything at once is not always possible for
> small businesses. The goal is to get current without getting
> bankrupt.<g>
> Thanks for you help and insight.
> --
> Bill|||(Plus, you'll never be in unsupported territory.)
> I would go the other way first, if you can. Update the things that run
your
> apps (SQL Server) and then the OS. It's easier, imho, to get the bugs out
> of the app migration first, THEN test an OS upgrade. If you go the other
> way it's very difficult to backtrack.|||No one explains what the problem is between the two. Why is is not compatible would have been a good question. Does it run? Yes it can be loaded. I have client apps that can not use SQL 2000 (they aren't rewritting the code). I was in an emergency situation that I had to load SQL 7 to get the system back on line ASAP with the new server they replaced (didn't have time to line MS pockets, yet). All the service packs loaded OK and the serices ran. I connected my clients with named pipes, and the data flowed. It has worked flawlessly for weeks, but I'm not doing alot of processing with it, just data collecting. Sooner than later I will have to get the gurus to rewrite the code on their app, but I was in a situation to where I had to use SQL 7 like it or not. Do I recommend using it, no. but it works in a bind.
"Bill Todd" wrote:
> Are there any known problems with running SQL Server 7 on Win 2003
> Server?
> Thanks,
> --
> Bill
>|||I don't think it is a problem with compatibility per say. SQL Server 7.0
came out before Win2003 and they will not add new functionality to 7.0 since
2000 is the current product. I am sure there are aspects of Win2003 that
7.0 knows nothing about and never will. I have never seen anything that
stated you can not get 7.0 to run but as was stated it is unsupported. So
if you have any problems at all your on your own<g>.
--
Andrew J. Kelly SQL MVP
"lesman" <lesman@.discussions.microsoft.com> wrote in message
news:E4841986-2E66-41F7-B79D-659B1DC1FE0E@.microsoft.com...
> No one explains what the problem is between the two. Why is is not
compatible would have been a good question. Does it run? Yes it can be
loaded. I have client apps that can not use SQL 2000 (they aren't rewritting
the code). I was in an emergency situation that I had to load SQL 7 to get
the system back on line ASAP with the new server they replaced (didn't have
time to line MS pockets, yet). All the service packs loaded OK and the
serices ran. I connected my clients with named pipes, and the data flowed.
It has worked flawlessly for weeks, but I'm not doing alot of processing
with it, just data collecting. Sooner than later I will have to get the
gurus to rewrite the code on their app, but I was in a situation to where I
had to use SQL 7 like it or not. Do I recommend using it, no. but it works
in a bind.
> "Bill Todd" wrote:
> > Are there any known problems with running SQL Server 7 on Win 2003
> > Server?
> >
> > Thanks,
> > --
> > Bill
> >|||> No one explains what the problem is between the two. Why is is not
> compatible would have been a good question.
Nobody said it wasn't compatible. They said it wasn't supported.
> I have client apps that can not use SQL 2000 (they aren't rewritting the
> code).
Can you give an example of something that works in 7.0 and not in 2000? How
about 2000 with the db in 7.0 compat mode?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Hi Bill,
Based on my testing, the codes like
Provider=SQLOLEDB; Data Source=Server, 6500; Initial Catalog=pubs; User
ID=sa; Password=;
could run well on my machine. So would you please follow my suggestions in
the previous post to configure port and then try it in Access again?
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I agree. That is the safe way and I do not want to run an unsupported
combination, just in case... :). Thanks for your help.
--
Bill