robboll (robboll@hotmail.com) writes:
> This is a very poor designed database which creates tables daily and
> does not archive anything. As a result it has grown in excess of 65+
> Gig in size. It literally has thousands of tables and the user could
> not tell me the approximate date when the missing values were added.
> That's when I thought of the MS Access routine that I have used in the
> past that works great with MS Access (small DBs). I tried linking to
> the SQL database and running it, but the workstation didn't have
> enough horsepower to do anything with it.

As I almost said. "One tends to think that if you need to [do] this, your
database design might [not] be what it ought to be."

(Some words were missing.)

> I will try your routine. Will it work with SQL Server 2000? This
> looks great! Thanks for your .

No, it will not work on SQL 2000 at all, as it uses several features
that were added in SQL 2005. In SQL 2000, you would need to run nested
cursors over the system tables.

You should always state which version of SQL Server you are using.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx