Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Perfomance problems after restoring database as new database

Status
Not open for further replies.

2Fuzzy4U

Programmer
Dec 2, 2002
26
NL
Hi,

Hope someone can help. I'm not even sure if this is the right topic. But at the moment, all tips, hint and pointers are welcome.

We wanted to seperate one project from an existing database. My collegue restored a backup of that database as a new database via sql server management Studio Express (2005), and all database connections for the one project where switched to the new database. (Both databases run at the same server.) But now all database trafic to both databases has slowed down. I've been looking at possible problems, missing settings or conflicting file use or whatever, but I'm do not know a lot about things like that.

Both use the same database user to log on to the database.

Thanks in advance
Coretta (NL)


__________________
Greetzzz
Coretta (NL)
 
As a first step, I encourage you make sure that all your statistics are up to date.

I would suggest you run the 3 following queries on your database.

Code:
Exec sp_msforeachtable 'SET ARITHABORT ON DBCC DBREINDEX([?]) WITH NO_INFOMSGS'
Exec sp_updatestats
DBCC updateUsage(0)

Also, check the configuration for the database.

In management studio, right click the database, then click properties.

In the upper left corner, click Options. Then, make sure
Auto Close = False
Auto Create Statistics = True
Auto Shrink = False
Auto Update Statistics = True


-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom
 
Thanks, but it doesn't seem to help. We checked and we run the queries, but still the databases are slow.
It feels like the two databases are in "eachothers hair" somehow.

__________________
Greetzzz
Coretta (NL)
 
As a starter, try running a Profiler trace with the basic metrics and see if there are connections, queries, jobs that are running in each DB.

Maybe with those pieces of info you may see that indeed "somtheing" is running or taxing the DB in a manner you did not expect.

Thanks

J. Kusch
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top