Have tables names changed from CF6/7 to CF 8/9?

[cfsports]

<<Edit>>I might have just answered my question, sort of.  I had already exported the data from the hosted SQL 2000 DB to my local SQL 2000 DB and then backed up and restored it to an empty DB in SQL 2008 Express.  The tables have the dbo. prefix instead of the "xx." prefix in the other DB which went from SQL 2000 to SQL 2008.  The site runs with the dbo. prefix.  Any links to articles/videos/summaries of simple differences between version still appreciated."<</Edit>>

I built a CF6/7 based site about 5 years ago and I'm trying to move it to the current versions of MSSQL (2008R2 Express) and CF9.  I believe the SQL DB is fine, I have setup the site on the local server, and am getting the following error when trying to view a page that access the DB.

[Macromedia][SQLServer JDBC  Driver][SQLServer]Invalid object name 'client_info'.

I exported the DB data from the live DB server into my local SQL 2008 Express and tables now have names like "xx.client_info"  Is it correct to assume that this is a new naming convention so that you can access easily access tables in multiple DBs?  Would I simply need to rename the tables to exclude the "xx." at the begining?  Or would it be advised to export the data into SQL 2000 and then backup/restore the DB to SQL 2008 Express?

Thanks for any help, and if there's a video or link to simple differences/improvements in CF from 6/7 to 8/9 any link would be greatly appreciated.

[Owainnorth · Accepted solution]

It's not CF-related, it's a SQLServer thing. In SQL 2008 they introduced the concept of Schemas, which I think is what you're seeing here. Rather than dbo.tablename, you now have schema.tablename.

I don't know the details to be honest, but that's what you need to be looking at.

O.

[cfsports]

Thanks for the info O.  I'm a rusty, as you point out this is all happening in SQL not CF which is great as it appears my site is unaffected by newer CF versions.

[Owainnorth]

Certainly it's good that it's not the CF side, you can probably find some T-SQL to run which would update all your database objects to be owned by dbo again if that's what you're after.

O.