Database growing unexpectedly

Hi all,
Running sql2000 ee SP4 on win2003.
I have a small database which havent been inserted/updated since it was
created 6 months ago. No DDL changes. This database was about 1,5 Mb for
the first months, but have started to grow. The size is now 30 Mb and it
is growing with about 2 Mb a month. It is set to autogrow with 10%.
Can someone explain this growth?
name rows reserved
form_lang 1 56 KB
grid_expr 0 0 KB
GridViewCategory 0 0 KB
GridViewDefinition 0 0 KB
hierarchy_tables 0 0 KB
invitation 0 0 KB
iteration 1 24 KB
lookup 0 0 KB
lookup_lang 0 0 KB
PanelistCredit 0 0 KB
quota 1 56 KB
response_control 2 104 KB
response1 0 0 KB
SampleLog 0 0 KB
weightmodel 0 0 KB
weightmodelform 0 0 KBTry running DBCC UPDATEUSAGE(0) and report back the space used.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns977AEC59B7F29gurbaohotmailcom@.12
9.250.171.65...
Hi all,
Running sql2000 ee SP4 on win2003.
I have a small database which havent been inserted/updated since it was
created 6 months ago. No DDL changes. This database was about 1,5 Mb for
the first months, but have started to grow. The size is now 30 Mb and it
is growing with about 2 Mb a month. It is set to autogrow with 10%.
Can someone explain this growth?
name rows reserved
form_lang 1 56 KB
grid_expr 0 0 KB
GridViewCategory 0 0 KB
GridViewDefinition 0 0 KB
hierarchy_tables 0 0 KB
invitation 0 0 KB
iteration 1 24 KB
lookup 0 0 KB
lookup_lang 0 0 KB
PanelistCredit 0 0 KB
quota 1 56 KB
response_control 2 104 KB
response1 0 0 KB
SampleLog 0 0 KB
weightmodel 0 0 KB
weightmodelform 0 0 KB|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in news:#noh#6kPGHA.1532
@.TK2MSFTNGP12.phx.gbl:

> Try running DBCC UPDATEUSAGE(0) and report back the space used.
>
Hi,
seems the first output from
USE MyDb; EXEC sp_MSforeachtable 'EXEC sp_spaceused [?]'
was missing some tables...
I ran UpdateUsage and the sp_spaceused again and found the reason for the
growth.
Case closed :-)
Thanks,

Database growing unexpectedly

Hi all,
Running sql2000 ee SP4 on win2003.
I have a small database which havent been inserted/updated since it was
created 6 months ago. No DDL changes. This database was about 1,5 Mb for
the first months, but have started to grow. The size is now 30 Mb and it
is growing with about 2 Mb a month. It is set to autogrow with 10%.
Can someone explain this growth?
name rows reserved
form_lang 1 56 KB
grid_expr 0 0 KB
GridViewCategory 0 0 KB
GridViewDefinition 0 0 KB
hierarchy_tables 0 0 KB
invitation 0 0 KB
iteration 1 24 KB
lookup 0 0 KB
lookup_lang 0 0 KB
PanelistCredit 0 0 KB
quota 1 56 KB
response_control 2 104 KB
response1 0 0 KB
SampleLog 0 0 KB
weightmodel 0 0 KB
weightmodelform 0 0 KB
Try running DBCC UPDATEUSAGE(0) and report back the space used.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns977AEC59B7F29gurbaohotmailcom@.129.250.171. 65...
Hi all,
Running sql2000 ee SP4 on win2003.
I have a small database which havent been inserted/updated since it was
created 6 months ago. No DDL changes. This database was about 1,5 Mb for
the first months, but have started to grow. The size is now 30 Mb and it
is growing with about 2 Mb a month. It is set to autogrow with 10%.
Can someone explain this growth?
name rows reserved
form_lang 1 56 KB
grid_expr 0 0 KB
GridViewCategory 0 0 KB
GridViewDefinition 0 0 KB
hierarchy_tables 0 0 KB
invitation 0 0 KB
iteration 1 24 KB
lookup 0 0 KB
lookup_lang 0 0 KB
PanelistCredit 0 0 KB
quota 1 56 KB
response_control 2 104 KB
response1 0 0 KB
SampleLog 0 0 KB
weightmodel 0 0 KB
weightmodelform 0 0 KB
|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in news:#noh#6kPGHA.1532
@.TK2MSFTNGP12.phx.gbl:

> Try running DBCC UPDATEUSAGE(0) and report back the space used.
>
Hi,
seems the first output from
USE MyDb; EXEC sp_MSforeachtable 'EXEC sp_spaceused [?]'
was missing some tables...
I ran UpdateUsage and the sp_spaceused again and found the reason for the
growth.
Case closed :-)
Thanks,

Database growing unexpectedly

Hi all,
Running sql2000 ee SP4 on win2003.
I have a small database which havent been inserted/updated since it was
created 6 months ago. No DDL changes. This database was about 1,5 Mb for
the first months, but have started to grow. The size is now 30 Mb and it
is growing with about 2 Mb a month. It is set to autogrow with 10%.
Can someone explain this growth?
name rows reserved
form_lang 1 56 KB
grid_expr 0 0 KB
GridViewCategory 0 0 KB
GridViewDefinition 0 0 KB
hierarchy_tables 0 0 KB
invitation 0 0 KB
iteration 1 24 KB
lookup 0 0 KB
lookup_lang 0 0 KB
PanelistCredit 0 0 KB
quota 1 56 KB
response_control 2 104 KB
response1 0 0 KB
SampleLog 0 0 KB
weightmodel 0 0 KB
weightmodelform 0 0 KBTry running DBCC UPDATEUSAGE(0) and report back the space used.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns977AEC59B7F29gurbaohotmailcom@.129.250.171.65...
Hi all,
Running sql2000 ee SP4 on win2003.
I have a small database which havent been inserted/updated since it was
created 6 months ago. No DDL changes. This database was about 1,5 Mb for
the first months, but have started to grow. The size is now 30 Mb and it
is growing with about 2 Mb a month. It is set to autogrow with 10%.
Can someone explain this growth?
name rows reserved
form_lang 1 56 KB
grid_expr 0 0 KB
GridViewCategory 0 0 KB
GridViewDefinition 0 0 KB
hierarchy_tables 0 0 KB
invitation 0 0 KB
iteration 1 24 KB
lookup 0 0 KB
lookup_lang 0 0 KB
PanelistCredit 0 0 KB
quota 1 56 KB
response_control 2 104 KB
response1 0 0 KB
SampleLog 0 0 KB
weightmodel 0 0 KB
weightmodelform 0 0 KB|||"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in news:#noh#6kPGHA.1532
@.TK2MSFTNGP12.phx.gbl:
> Try running DBCC UPDATEUSAGE(0) and report back the space used.
>
Hi,
seems the first output from
USE MyDb; EXEC sp_MSforeachtable 'EXEC sp_spaceused [?]'
was missing some tables...
I ran UpdateUsage and the sp_spaceused again and found the reason for the
growth.
Case closed :-)
Thanks,sql

Database files compatible with Win2K & Win2003

SQL Server 2000/SP3 runs on Win2K.
I've failover clustering server run on Win2003. Are the system database
files compatible on both Win2K & Win003 ? That I can switch the databases on
Win2k to Win2003.
JT
Hi
SQL Server 2000 data files and backups, on 32 or 64 bit, are compatible on
any platform. The base OS does not matter. OS does not play a role here.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny" wrote:

> SQL Server 2000/SP3 runs on Win2K.
> I've failover clustering server run on Win2003. Are the system database
> files compatible on both Win2K & Win003 ? That I can switch the databases on
> Win2k to Win2003.
> JT

Database files compatible with Win2K & Win2003

SQL Server 2000/SP3 runs on Win2K.
I've failover clustering server run on Win2003. Are the system database
files compatible on both Win2K & Win003 ? That I can switch the databases on
Win2k to Win2003.
JTHi
SQL Server 2000 data files and backups, on 32 or 64 bit, are compatible on
any platform. The base OS does not matter. OS does not play a role here.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny" wrote:
> SQL Server 2000/SP3 runs on Win2K.
> I've failover clustering server run on Win2003. Are the system database
> files compatible on both Win2K & Win003 ? That I can switch the databases on
> Win2k to Win2003.
> JT

Database files compatible with Win2K & Win2003

SQL Server 2000/SP3 runs on Win2K.
I've failover clustering server run on Win2003. Are the system database
files compatible on both Win2K & Win003 ? That I can switch the databases on
Win2k to Win2003.
JTHi
SQL Server 2000 data files and backups, on 32 or 64 bit, are compatible on
any platform. The base OS does not matter. OS does not play a role here.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny" wrote:

> SQL Server 2000/SP3 runs on Win2K.
> I've failover clustering server run on Win2003. Are the system database
> files compatible on both Win2K & Win003 ? That I can switch the databases
on
> Win2k to Win2003.
> JTsql

Database diagram support objects cannot be installed...

I can't make a diagram on our server(Win2003 x64,SQL 2005 Enterprise x64 sp2 3054).

I have tried to login as an admin and create a new db, but get the same message -

'Database diagram support objects cannot be installed because this database does not have a valid owner. To..'

Also tried to make a diagram from the ReportServer db.

Any suggestions?

Two things to check.

1. please make sure that db has a owner (as the error suggests).

2. please check your compatibility level.

|||

Thanks Meher for your reply.

1. Both of the databases I tried has a owner.

2. I'm pretty sure the compatibility level is 90 (SQL 2005) since one is created during installation(ReportServer) and the other is created as a new db in SQL Management Studio. (To be sure I will check next week)

Any other suggestions?

|||

Are you still getting the error message?. As you have mentioned check the compatibility level once again and if you are still getting the message we can look a bit further.

|||

The compatibility level is 90(SQL Server 2005).

|||

what role do you belong to?. pls check

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uirfsql9/html/6fdecefb-7bd3-4203-a58c-36d46ee628bf.htm

|||db_owner |||

Hi olof,

can you please go through the steps outlined in section 4.8.1 in http://support.microsoft.com/?id=910228

As per the section in the article, looks like you might have to install the diagram support.

To create database diagrams, change the database compatibility level to 2005, install database diagram support, and then return the database to the desired database compatibility level.

MVPs, please correct me if I am missing something.

Thanks

Meher

|||

one other thing I forgot to mention is that the installation of support objects can fail if the database

has been attached or restored from another instance of SQL Server. In such a case there is a

possibility that the database owner name stored in the database may not be a valid logon for the

instance of the SQL Server on to which the database is restored to (or attached to).

I would suggest if thats the case then you can use the Alter statement to change the owner to a valid logon.

ALTER AUTHORIZATION ON DATABASE::your dbname TO yourdesiredlogin

(please see BOL for more details on ALTER AUTHORIZATION).

I would suggest doing through T-SQL than UI and see if it solves your issue.

Thanks

Meher