Maxim's right, unless...

Maxim's code will work, and would obviously only run for the tables that exist in your counting table...

but if you compare it to the set based solution, it'll be a...

simply run the script. it counts the table rows,even for tables with no indexes or primary keys (heap tables).

so you could potentially do something like this:

UPDATE MyDBCount

SET PrevRowCount...

Michael (3/19/2009)

---

There are a few hundred tables and I only need info on about 50.

Looping through an extra 150 tables (some of which are quite large) would take too long.

Also,...

SELECT INTO syntax is designed to create a table on the fly.

i believe a linked server only allows you to add/insert/update into existing objects....not CREATE objects on the fly like...

very easy, just plan it out.

1. take any of the scripts that count rows from sysindexes. no need to filter which tables at this point.

2. put the results in a...

Keep at it Krishna;

I'd like to see a default Data Manipulation Language (DML) trace automatically running all the time as well as the Data Definition Language(DDL) trace;

just to be...

default trace keeps track of when database objects, like tables/views/procs where created/modified or deleted.

it does not keep track of when they were executed or accessed.

you must create your own trace...

unfortunately you can't call SET PARSENAME inside a procedure...

so you can't wrap noeld's code and put it inside a proc; maight work as dynamic SQL, but I'd have to test...

it depends on the application they are connecting to;

i think if i connect in SSMS, since i can "read" from sysdatabases, i can see all the db's ont he server...but...

i noticed if i add an 800 line block, it'll show all 800 lines; i'd rather have a scrollbar for the code in question, if possible.

seems to hate less-than and greater-than symbols:

this line has the ampersand-LT-semicolon:

salesMonth <=@month and YTD = 0 OR salesMonth = @month and YTD <> 0

this is as you'd type it

...

testing regular text vs the {code} blocks:

with ampersand LT semicolon escapes:

salesMonth <= @month and YTD = 0 OR salesMonth = @month and YTD <> 0

as typed

salesMonth 0

salesMonth ...

you are suffering from "parameter sniffing"; you can search here on SSC for the suggested solutions;

the issue is the default values for your parameters...

since they are assigned NULL, the compiler...

cool, glad you found it; it's probably nothing more than updating the ArcServe program to have your new sa password, or even better, create a login just for that process.