Database is running slow after running DBCC Shrinkdatabase command

We have SQL 2000 Enterprise Edition running on Windows 2000 Server. I ran
the DBCC Shrinkdatabase command last week. Now, the database is slow when I
open one of the work orders. Do you have any recommendation on how to fix
the slowness? Am I doing something incorrectly? I ran the following
commands under Query Analyzer. Thank you.
BACKUP LOG Support_DATA WITH TRUNCATE_ONLY
GO
DBCC SHRINKDATABASE (Support_DATA, TRUNCATEONLY)Diane,
Just a guess...perhaps there is very little free space in the database and
the growth interval is small (i.e., 1MB) so the database continually grows
as new data is inserted. If this is the case, increase the size of the
database and the the growth setting. Degrading performance can also be
attributed to index fragmentation and out-of-date statistics.
HTH
Jerr
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:ek4k5hgxFHA.1132@.TK2MSFTNGP10.phx.gbl...
> We have SQL 2000 Enterprise Edition running on Windows 2000 Server. I ran
> the DBCC Shrinkdatabase command last week. Now, the database is slow when
> I open one of the work orders. Do you have any recommendation on how to
> fix the slowness? Am I doing something incorrectly? I ran the following
> commands under Query Analyzer. Thank you.
> BACKUP LOG Support_DATA WITH TRUNCATE_ONLY
> GO
> DBCC SHRINKDATABASE (Support_DATA, TRUNCATEONLY)
>|||The shrinkdatabase command isn't very useful in my opinion.
You don't have much control over which files are being
shrunk to what size. Shrinking is typically something that
you would do ad hoc and for a specific file using shrinkfile
- after a run away transaction filled up the log, a database
where the log wasn't being backed up and the size became too
large, etc. The goal should be to size the files
appropriately, do regular log back ups to keep the log size
reasonable and avoid shrinking activities.
The slowness may or may not be related to having shrunk the
database last week. When you query the table, you would want
to monitor what is going on - checking for other activity
and locking/blocking by executing sp_who2 and querying the
sysprocesses table in the master database. And you'd want to
use something other than Enterprise Manager to view data in
tables - especially if it has a lot of data. Enterprise
Manager isn't necessarily a good tool to use for viewing or
manipulating data. Use Query Analyzer instead.
-Sue
On Fri, 30 Sep 2005 14:46:53 -0700, "Diane Walker"
<ett9300@.yahoo.com> wrote:
>We have SQL 2000 Enterprise Edition running on Windows 2000 Server. I ran
>the DBCC Shrinkdatabase command last week. Now, the database is slow when I
>open one of the work orders. Do you have any recommendation on how to fix
>the slowness? Am I doing something incorrectly? I ran the following
>commands under Query Analyzer. Thank you.
>BACKUP LOG Support_DATA WITH TRUNCATE_ONLY
>GO
>DBCC SHRINKDATABASE (Support_DATA, TRUNCATEONLY)
>|||Possibly autogrow as suggested or that indexes became fragmented due to the shrink:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:ek4k5hgxFHA.1132@.TK2MSFTNGP10.phx.gbl...
> We have SQL 2000 Enterprise Edition running on Windows 2000 Server. I ran the DBCC Shrinkdatabase
> command last week. Now, the database is slow when I open one of the work orders. Do you have any
> recommendation on how to fix the slowness? Am I doing something incorrectly? I ran the following
> commands under Query Analyzer. Thank you.
> BACKUP LOG Support_DATA WITH TRUNCATE_ONLY
> GO
> DBCC SHRINKDATABASE (Support_DATA, TRUNCATEONLY)
>sql

Database in recovery

Our server ran out of disk space during a stored procedure process. We were able to free up some space, stopped all SQL services, restarted all SQL services and now SQL Management Studio shows the database to be in recovery. Is there a way to monitor this to ensure progress is being made and to estimate when it might complete?

I don't know it can be checked programatically but you can sql error log where you recovery progress will be recorded.

Looks like you guys shutdown the servers in the middle of big transaction....

There will no other option than waiting to recover...

|||

There is a way, via T-SQL to view process progress but apparently not via GUI. The database did eventually recover and we have submitted for a new server as it ran out of disk space during a stored procedure run.

Thanks!

Database Design for Mere Mortals

I ran into "Database Design for Mere Mortals"
what's the meaning of "mere mortals"?
Thanks.First use: http://dictionary.reference.com/
It is the title of Mike Hernandez's popular book on relational database
design that is purportedly easier to understand.
Anith|||mere mortals can be interpreted as "only human"
Regards,
Greg Linwood
SQL Server MVP
"haode" <haode@.hao.com> wrote in message
news:OwbQj2YAEHA.2800@.tk2msftngp13.phx.gbl...
> I ran into "Database Design for Mere Mortals"
> what's the meaning of "mere mortals"?
> Thanks.
>|||RE/
>what's the meaning of "mere mortals"?
In that context, people who are just average - not extremely smart or
knowledgable.
--
PeteCresswell

Database Design for Mere Mortals

I ran into "Database Design for Mere Mortals"
what's the meaning of "mere mortals"?
Thanks.First use: http://dictionary.reference.com/
It is the title of Mike Hernandez's popular book on relational database
design that is purportedly easier to understand.
--
Anith|||mere mortals can be interpreted as "only human"
Regards,
Greg Linwood
SQL Server MVP
"haode" <haode@.hao.com> wrote in message
news:OwbQj2YAEHA.2800@.tk2msftngp13.phx.gbl...
> I ran into "Database Design for Mere Mortals"
> what's the meaning of "mere mortals"?
> Thanks.
>|||RE/
>what's the meaning of "mere mortals"?
In that context, people who are just average - not extremely smart or
knowledgable.
--
PeteCresswell

database corruption

Hi,
I just ran into a big trouble with sqlserver 2005 Express and Visual Basic
2005.
I have a database, wich is an upsize of an AccessXp database, worked until
now perfect with Vb net 2003
I upgraded to Vb2005 for learning purposes an ran into the following
trouble.
1. Opening a database connection in the server explorer and viewing the
tablestructure etc. works ok BUT...
2. Closing the connection corrupts the db!!
Reopening is impssible and the mdf and ldf files are doubled in size!
The only sollution is then complelety removing both files from the HD and
restoring a backup
All the above is also true for the db's like Pubs or Northwind. After making
a connection in server explorer and closing the IDE, the db's are corrupt
and inaccesible by whatever program.
The connection provider is the one suggested by VB2005 for sqlserver Express
: slqlient for local database
With another sqlprovider it even refuse to find the server
This all happens exclusiveli in the "server explorer", a compiled prog or
debugging from within the IDE works perfect.
If i do the same in VB2003 to the same database and server then everything
stays ok
Any suggestion will be appreciated
Thanks in advance
JeromeWhen connecting to a msde server or even the local sqlexpress via the normal
sqlconnection all runs ok.
Only when connecting via the native provider for sqlexpress the database
becomes corrupt
Just wanted to add that the software runs on a dutch version of wndows XP
regards
Jerome
"Jerome" <Jommeke@.fake.com> schreef in bericht
news:xp%hf.57683$tB5.3726394@.phobos.telenet-ops.be...
> Hi,
> I just ran into a big trouble with sqlserver 2005 Express and Visual Basic
> 2005.
> I have a database, wich is an upsize of an AccessXp database, worked until
> now perfect with Vb net 2003
> I upgraded to Vb2005 for learning purposes an ran into the following
> trouble.
> 1. Opening a database connection in the server explorer and viewing the
> tablestructure etc. works ok BUT...
> 2. Closing the connection corrupts the db!!
> Reopening is impssible and the mdf and ldf files are doubled in size!
> The only sollution is then complelety removing both files from the HD and
> restoring a backup
> All the above is also true for the db's like Pubs or Northwind. After
> making a connection in server explorer and closing the IDE, the db's are
> corrupt and inaccesible by whatever program.
> The connection provider is the one suggested by VB2005 for sqlserver
> Express : slqlient for local database
> With another sqlprovider it even refuse to find the server
> This all happens exclusiveli in the "server explorer", a compiled prog or
> debugging from within the IDE works perfect.
> If i do the same in VB2003 to the same database and server then everything
> stays ok
> Any suggestion will be appreciated
> Thanks in advance
> Jerome
>
>

database corruption

Hi,
I just ran into a big trouble with sqlserver 2005 Express and Visual Basic
2005.
I have a database, wich is an upsize of an AccessXp database, worked until
now perfect with Vb net 2003
I upgraded to Vb2005 for learning purposes an ran into the following
trouble.
1. Opening a database connection in the server explorer and viewing the
tablestructure etc. works ok BUT...
2. Closing the connection corrupts the db!!
Reopening is impssible and the mdf and ldf files are doubled in size!
The only sollution is then complelety removing both files from the HD and
restoring a backup
All the above is also true for the db's like Pubs or Northwind. After making
a connection in server explorer and closing the IDE, the db's are corrupt
and inaccesible by whatever program.
The connection provider is the one suggested by VB2005 for sqlserver Express
: slqlient for local database
With another sqlprovider it even refuse to find the server
This all happens exclusiveli in the "server explorer", a compiled prog or
debugging from within the IDE works perfect.
If i do the same in VB2003 to the same database and server then everything
stays ok
Any suggestion will be appreciated
Thanks in advance
Jerome
When connecting to a msde server or even the local sqlexpress via the normal
sqlconnection all runs ok.
Only when connecting via the native provider for sqlexpress the database
becomes corrupt
Just wanted to add that the software runs on a dutch version of wndows XP
regards
Jerome
"Jerome" <Jommeke@.fake.com> schreef in bericht
news:xp%hf.57683$tB5.3726394@.phobos.telenet-ops.be...
> Hi,
> I just ran into a big trouble with sqlserver 2005 Express and Visual Basic
> 2005.
> I have a database, wich is an upsize of an AccessXp database, worked until
> now perfect with Vb net 2003
> I upgraded to Vb2005 for learning purposes an ran into the following
> trouble.
> 1. Opening a database connection in the server explorer and viewing the
> tablestructure etc. works ok BUT...
> 2. Closing the connection corrupts the db!!
> Reopening is impssible and the mdf and ldf files are doubled in size!
> The only sollution is then complelety removing both files from the HD and
> restoring a backup
> All the above is also true for the db's like Pubs or Northwind. After
> making a connection in server explorer and closing the IDE, the db's are
> corrupt and inaccesible by whatever program.
> The connection provider is the one suggested by VB2005 for sqlserver
> Express : slqlient for local database
> With another sqlprovider it even refuse to find the server
> This all happens exclusiveli in the "server explorer", a compiled prog or
> debugging from within the IDE works perfect.
> If i do the same in VB2003 to the same database and server then everything
> stays ok
> Any suggestion will be appreciated
> Thanks in advance
> Jerome
>
>

database corruption

Hi,
I just ran into a big trouble with sqlserver 2005 Express and Visual Basic
2005.
I have a database, wich is an upsize of an AccessXp database, worked until
now perfect with Vb net 2003
I upgraded to Vb2005 for learning purposes an ran into the following
trouble.
1. Opening a database connection in the server explorer and viewing the
tablestructure etc. works ok BUT...
2. Closing the connection corrupts the db!!
Reopening is impssible and the mdf and ldf files are doubled in size!
The only sollution is then complelety removing both files from the HD and
restoring a backup
All the above is also true for the db's like Pubs or Northwind. After making
a connection in server explorer and closing the IDE, the db's are corrupt
and inaccesible by whatever program.
The connection provider is the one suggested by VB2005 for sqlserver Express
: slqlient for local database
With another sqlprovider it even refuse to find the server
This all happens exclusiveli in the "server explorer", a compiled prog or
debugging from within the IDE works perfect.
If i do the same in VB2003 to the same database and server then everything
stays ok
Any suggestion will be appreciated
Thanks in advance
JeromeWhen connecting to a msde server or even the local sqlexpress via the normal
sqlconnection all runs ok.
Only when connecting via the native provider for sqlexpress the database
becomes corrupt
Just wanted to add that the software runs on a dutch version of wndows XP
regards
Jerome
"Jerome" <Jommeke@.fake.com> schreef in bericht
news:xp%hf.57683$tB5.3726394@.phobos.telenet-ops.be...
> Hi,
> I just ran into a big trouble with sqlserver 2005 Express and Visual Basic
> 2005.
> I have a database, wich is an upsize of an AccessXp database, worked until
> now perfect with Vb net 2003
> I upgraded to Vb2005 for learning purposes an ran into the following
> trouble.
> 1. Opening a database connection in the server explorer and viewing the
> tablestructure etc. works ok BUT...
> 2. Closing the connection corrupts the db!!
> Reopening is impssible and the mdf and ldf files are doubled in size!
> The only sollution is then complelety removing both files from the HD and
> restoring a backup
> All the above is also true for the db's like Pubs or Northwind. After
> making a connection in server explorer and closing the IDE, the db's are
> corrupt and inaccesible by whatever program.
> The connection provider is the one suggested by VB2005 for sqlserver
> Express : slqlient for local database
> With another sqlprovider it even refuse to find the server
> This all happens exclusiveli in the "server explorer", a compiled prog or
> debugging from within the IDE works perfect.
> If i do the same in VB2003 to the same database and server then everything
> stays ok
> Any suggestion will be appreciated
> Thanks in advance
> Jerome
>
>