So, my guess is that it's a compilation thing. However, the server's been running for 2 months, and the problem only began manifesting itself for one of two users today...

Thanks for your help Gail.

I'll look into the msdb rebuild option.

P

Hi Gail,

Yes, msdb was restored from a backup made from a server configured as

SQL Latin1_General_CP1_CI_AS.

(We upgraded the OS on the server, and did a full re-install of SQL. This...

Hi Gail,

Good call, the msdb and tempdb do not have the same collations.

This is the sproc that's getting called every 20 secs.

EXECUTE msdb.dbo.sp_sqlagent_get_perf_counters

Soooo, what are some possible solutions?

P

Yes, I read it.

And you're correct, on the one system, there is a backup log w/ truncate only.

However, the log file kept growing on one of the "twins" over the...

Furthermore, the same source DB is transferred to 2 other servers.

Of these, one is exhibiting the same behaviour as noted above.

The other, SQL 2K sp2 on Win2K, is not:...

Respectfully, that is not borne out by my experience.

We do a single daily full backup of the prod DB, and it has *never* -- in 10 years -- grown...

Yes, destination is set to full recovery. A full backup is done immediately prior to transfers.

No tran. log backups required, since there is no other activity on the server.

It's...

How many users, what are they doing, how is the data accessed?

Some possibilities: SELECT * queries on big tables; stored proc recompilations?

In SQL Server, each new database created is a copy of the model DB.

This applies to tables, stored procedures, and file sizes.

So if you want every new DBs to...

Failed:

VNI-2015 : The Node preferred credentials for the target node are either invalid or do not have sufficient privileges to complete the operation.

On Windows platforms, the Node credentials...

It turns out it was done with the Oracle export utility.

I've initiated an inquiry.

I'll respond when I get an answer.

I hope they're not on holidays...

Thanks for the help so far.

Nice!!! The people who did the backup cleverly named the file h26b_full.Mar04 -- no doubt so we could tell it was done on March 4 -- which we already knew...

Thanks for that.

Now, I have access to a DB I created, Test.

I have placed it in Mounted mode, which should enable recovery.

I right-click on the Test database, Backup Management, Recovery....