Posted by Erland Sommarskog on 08/31/06 21:07

RS200Phil (philsowden@dataservicesltd.co.uk) writes:
> I have managed to create a second copy of my "live" database, for
> software testing purposes.
>
> Inspecting the properties of the new database, everything seems in
> order. The logical file name is the same, which I believe is fine, and
> the physical database (and log file name) is different.
>
> However, despite the fact that there is no application currently
> accessing the "testing" copy, both databases are seemingly being
> updated simultanously. I can tell this from the physical file sizes on
> the server, which are identical, and growing at the same rate.
>
> Does anyone have any suggestions why this might be happening - and how
> I can stop it?

It sounds funny to me that you can see the files grow. Autogrow events
on live databases should be rare events and not happen frequently. You
create them with a reasonable initial size, and then you preferrably
increase then while you have a maintenance window. Autogrow during
production should be avoided, as it could cause the database to be
inaccessible while autogrow is in progress.

To tell why your databases grow in parallel would require more knowledge
about your server. Here we are left to wild guesses. Maybe you set up
replication between the databases?

sp_who can tell you if there are any processes in the database at all.
You can use SQL Server Profiler to see if there is any action in the
server.

Which version of SQL Server are you using?

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

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]