Be sure to double check your stored procedures. SQL Server 7 was tolerant
of the create procedure name being different from the actual stored
procedure name, but 2000 isn't. Or at least the import routine isn't. It
will just fail, but if it does, then that's probably the problem.
When we ported our largest database over, I ended up doing one bit at a time
with the Enterprise Manager. Trying to do it all at once was an exercise it
futility ... It would get 70% done, and then fail on a view or a stored
proc. Do your data last, that way the time consuming stuff, which should be
fine, won't cause you long delays to find these stupid little problems.
As far as CF goes - I didn't think we've had to do anything different at all
in our code, and it's humming along quite nicely for us.
-Bill
www.brainbox.tv
----- Original Message -----
From: "Derek Hamilton" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Monday, May 14, 2001 5:23 PM
Subject: SQL Server 2000
> Hello!
>
> I am in the process of planning my upgrade to SQL Server 2000 from SQL
Server 7.0. I was wondering if anyone has noticed anything odd or difficult
in respect to ColdFusion (4.5 and 5.0RC)?
>
> Any advice or even things you've noticed would be extremely helpful.
>
> Thanks,
>
> Derek Hamilton
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
