Find Invalid Objects - Bug When Used On MSSQL 2000 Database

jk3000

I didn't see this posted any where else - so please forgive if this is a known issue.
The "Find Invalid Objects" command says "Invalid object name" on any table valued function -- at least it seems to only be an issue when feature is used on MSSQL 2000 databases (btw, Table-Valued Functions are supported on SQL Server 2000 as of SP3) - http://msdn.microsoft.com/en-us/library ... 5(v=SQL.80).aspx.
Example-- Type: Table-valued Function, Object Name: dbo.Split, Reason Invalid: Invalid object name 'dbo.Split'.
Not sure if it matters or not - but I'm using MS SQL Server Management Studio (Sql Server 2008 R2) - to connection to a SQL Server 2000 database that is on a legacy system. And, also, the table value function 'dbo.Split' does not come back as an invalid object on a 2008 database. Also, the function works without error on SQL 2000 - been in production use for a long time without issue. And besides, all table value fucntions are labeled as invalid on 2000 databases not just the split function.

John

Anu D

Apologies for the delay in getting back to you.

I have emailed you for few more details.