
MS SQL 7.0 vs. MS SQL 2000
Quote:
> There must be more to it than that, surely?
Nope. Install SQL 2000 on the server. That's it. Well... you might have
to update the Data Access Components on the workstations. But that's
provided on the SQL 2000 CD. Beyond that no mods to the Clarion app are
needed.
Quote:
> I have a client who is having problems with his MSSQL 6.5 and his 'MSSQL
> experts' are advising a move to '7'.
> Perhaps 2000 would be a better option?
I would say his "SQL experts" don't know what they're talking about. SQL
7.0 was a HUGE improvement over 6.5. We had 3 offices on 7.0 when we found
out 2000 was coming out. We tested 2000 and found a few things which we
worked with out Microsoft. (Support was pretty good actually. But then we
were talking about 40+ licenses of SQL Server 2000.<g>) We moved those
offices to SQL 2000 and never looked back. The other 37, (soon to be 38),
were never on 7.0 but went right to 2000. I would say your client can
confidently skip version 7.0. Our 40 offices have been on SQL 2000 for
varying amounts of time; some since Dec. 2000 or Jan. 2001. Others have
been on it since Feb. 2001. Other than a few minor glitches with timing to
get 40 offices and a home office all replicating properly and getting our
batch processes timed correctly, we haven't had much trouble with SQL at
all. The databases themselves seem to be rock solid.
The only thing I can think of that might be an issue is whether or not SQL
2000 can convert a SQL 6.5. It didn't even sneeze when going from SQL 7.0
to SQL 2000.
Quote:
> As a matter of interest do present Clarion templates (cowboy etc) work
fine
> on 2000?
We don't have Cowboy's stuff so I can't speak to that.
Rick Smith
Nationwide Advertising Service