The server had WSUS 2.0 which was never used. The database file is
5.7GB
I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
shrink the db file.

It's been 12 hours now. I am wondering how many more hours i should
expect?

Thanks



j~

Jack wrote:

> The server had WSUS 2.0 which was never used. The database file is
> 5.7GB
> I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> shrink the db file.
>
> It's been 12 hours now. I am wondering how many more hours i should
> expect?
>
> Thanks
>
> j~

The first time I ran it I had to break it up into pieces. If it's still
running, Id' give it another day or so. yes, I said a day or so.

--
/kj

In article <d19ff2c8-88da-4aa7-b632-5386e2c88832
@a5g2000prg.googlegroups.com>, dontaskwhoiam2001@newsgroup says...

>
> The server had WSUS 2.0 which was never used. The database file is
> 5.7GB
> I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> shrink the db file.
>
> It's been 12 hours now. I am wondering how many more hours i should
> expect?
>
> Thanks

Sounds like a *long* time for a smallish d.base. But stay with it.
Should it finish, run an index rebuild - it should dramatically improve
things. (Shoulda probably run this first - but too late now). I run
this sql about once a month.

http://go.microsoft.com/fwlink/?LinkId=87027

That link comes from this page.
http://technet.microsoft.com/en-us/l...94(WS.10).aspx


--
Duncan.

In article <MPG.25e4982d9df5edab989b61@newsgroup>, no-
spam@newsgroup says...

>
> In article <d19ff2c8-88da-4aa7-b632-5386e2c88832
> @a5g2000prg.googlegroups.com>, dontaskwhoiam2001@newsgroup says...

> >
> > The server had WSUS 2.0 which was never used. The database file is
> > 5.7GB
> > I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> > shrink the db file.
> >
> > It's been 12 hours now. I am wondering how many more hours i should
> > expect?
> >
> > Thanks

>
> Sounds like a *long* time for a smallish d.base. But stay with it.
> Should it finish, run an index rebuild - it should dramatically improve
> things. (Shoulda probably run this first - but too late now). I run
> this sql about once a month.
>
> http://go.microsoft.com/fwlink/?LinkId=87027
>
> That link comes from this page.
> http://technet.microsoft.com/en-us/l...94(WS.10).aspx

I should add, that I like to use the SQL Server Management Console to do
this (rather than the oSQL way). If you don't have SBS w' SQL Server,
you can still download and install SQL Server Managment Studio Express
(the free version). Just be sure you get your version (SQL S 2005 or
2008 etc).

To open the WSUS database, a Windows Internal database, put

\\.\pipe\mssql$microsoft##ssee\sql\query

in the Server name field.

Then I'd go, File, New etc - and put paste the code in a save it as say
"re-index WSUS database.sql"

And then in future you can just File, Open it, and run it - or better,
create a Maintenance Schedule for it.

--
Duncan.

On Feb 15, 2:34*pm, "kj [SBS MVP]" <KevinJ....@newsgroup>
wrote:

> Jack wrote:

> > The server had WSUS 2.0 which was never used. The database file is
> > 5.7GB
> > I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> > shrink the db file.

>

> > It's been 12 hours now. I am wondering how many more hours i should
> > expect?

>

> > Thanks

>

> > j~

>
> The first time I ran it I had to break it up into pieces. If it's still
> running, Id' give it another day or so. yes, I said a day or so.
>
> --
> /kj

The process was errored out. I will do the cleanup again in pieces
this time. Thanks KJ for the advice.
jack

On Feb 15, 2:55*pm, Duncan McCormack <no-s...@newsgroup> wrote:

> In article <d19ff2c8-88da-4aa7-b632-5386e2c88832
> @a5g2000prg.googlegroups.com>, dontaskwhoiam2...@newsgroup says...
>
>
>

> > The server had WSUS 2.0 which was never used. The database file is
> > 5.7GB
> > I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> > shrink the db file.

>

> > It's been 12 hours now. I am wondering how many more hours i should
> > expect?

>

> > Thanks

>
> Sounds like a *long* time for a smallish d.base. *But stay with it. *
> Should it finish, run an index rebuild - it should dramatically improve
> things. *(Shoulda probably run this first - but too late now). *I run
> this sql about once a month.
>
> http://go.microsoft.com/fwlink/?LinkId=87027
>
> That link comes from this page.http://technet.microsoft.com/en-us/l...94(WS.10).aspx
>
> --
> Duncan.

Thanks Duncan for the URLs.
I will look into them.
jack

On Feb 15, 3:03*pm, Duncan McCormack <no-s...@newsgroup> wrote:

> In article <MPG.25e4982d9df5edab989...@newsgroup>, no-
> s...@newsgroup says...
>
>
>
>
>

> > In article <d19ff2c8-88da-4aa7-b632-5386e2c88832
> > @a5g2000prg.googlegroups.com>, dontaskwhoiam2...@newsgroup says...

>

> > > The server had WSUS 2.0 which was never used. The database file is
> > > 5.7GB
> > > I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> > > shrink the db file.

>

> > > It's been 12 hours now. I am wondering how many more hours i should
> > > expect?

>

> > > Thanks

>

> > Sounds like a *long* time for a smallish d.base. *But stay with it. *
> > Should it finish, run an index rebuild - it should dramatically improve
> > things. *(Shoulda probably run this first - but too late now). *I run
> > this sql about once a month.

>

> >http://go.microsoft.com/fwlink/?LinkId=87027

>

> > That link comes from this page.
> >http://technet.microsoft.com/en-us/l...94(WS.10).aspx

>
> I should add, that I like to use the SQL Server Management Console to do
> this (rather than the oSQL way). *If you don't have SBS w' SQL Server,
> you can still download and install SQL Server Managment Studio Express
> (the free version). *Just be sure you get your version (SQL S 2005 or
> 2008 etc).
>
> To open the WSUS database, a Windows Internal database, put
>
> \\.\pipe\mssql$microsoft##ssee\sql\query
>
> in the Server name field.
>
> Then I'd go, File, New etc - and put paste the code in a save it as say
> "re-index WSUS database.sql"
>
> And then in future you can just File, Open it, and run it - or better,
> create a Maintenance Schedule for it.
>
> --
> Duncan.

Thanks for your second option - downloading SSMSE. I think it will be
much easier for me.
Which version is better? 2005 or 2008?
jack

In article <7f1460f0-8d3c-4784-b750-
e321f7fa3afd@newsgroup>, dontaskwhoiam2001@newsgroup
says...

>
> On Feb 15, 3:03*pm, Duncan McCormack <no-s...@newsgroup> wrote:

> > In article <MPG.25e4982d9df5edab989...@newsgroup>, no-
> > s...@newsgroup says...
> >
> >
> >
> >
> >

> > > In article <d19ff2c8-88da-4aa7-b632-5386e2c88832
> > > @a5g2000prg.googlegroups.com>, dontaskwhoiam2...@newsgroup says...

> >

> > > > The server had WSUS 2.0 which was never used. The database file is
> > > > 5.7GB
> > > > I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> > > > shrink the db file.

> >

> > > > It's been 12 hours now. I am wondering how many more hours i should
> > > > expect?

> >

> > > > Thanks

> >

> > > Sounds like a *long* time for a smallish d.base. *But stay with it. *
> > > Should it finish, run an index rebuild - it should dramatically improve
> > > things. *(Shoulda probably run this first - but too late now). *I run
> > > this sql about once a month.

> >

> > >http://go.microsoft.com/fwlink/?LinkId=87027

> >

> > > That link comes from this page.
> > >http://technet.microsoft.com/en-us/l...94(WS.10).aspx

> >
> > I should add, that I like to use the SQL Server Management Console to do
> > this (rather than the oSQL way). *If you don't have SBS w' SQL Server,
> > you can still download and install SQL Server Managment Studio Express
> > (the free version). *Just be sure you get your version (SQL S 2005 or
> > 2008 etc).
> >
> > To open the WSUS database, a Windows Internal database, put
> >
> > \\.\pipe\mssql$microsoft##ssee\sql\query
> >
> > in the Server name field.
> >
> > Then I'd go, File, New etc - and put paste the code in a save it as say
> > "re-index WSUS database.sql"
> >
> > And then in future you can just File, Open it, and run it - or better,
> > create a Maintenance Schedule for it.
> >
> > --
> > Duncan.

>
> Thanks for your second option - downloading SSMSE. I think it will be
> much easier for me.
> Which version is better? 2005 or 2008?

I don't know, it's your server!

What SBS are you running?

The 2005 version should do just fine.

SQL Server Managment Studio Express @ SP3 ....
http://www.microsoft.com/downloads/d...5D76230D-580D-
4874-8C7D-93491A29DB15&displaylang=en


--
Duncan.

On Feb 15, 4:59*pm, Duncan McCormack <no-s...@newsgroup> wrote:

> In article <7f1460f0-8d3c-4784-b750-
> e321f7fa3...@newsgroup>, dontaskwhoiam2...@newsgroup
> says...
>
>
>
>
>

> > On Feb 15, 3:03*pm, Duncan McCormack <no-s...@newsgroup> wrote:

> > > In article <MPG.25e4982d9df5edab989...@newsgroup>, no-
> > > s...@newsgroup says...

>

> > > > In article <d19ff2c8-88da-4aa7-b632-5386e2c88832
> > > > @a5g2000prg.googlegroups.com>, dontaskwhoiam2...@newsgroup says...

>

> > > > > The server had WSUS 2.0 which was never used. The database file is
> > > > > 5.7GB
> > > > > I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> > > > > shrink the db file.

>

> > > > > It's been 12 hours now. I am wondering how many more hours i should
> > > > > expect?

>

> > > > > Thanks

>

> > > > Sounds like a *long* time for a smallish d.base. *But stay with it. *
> > > > Should it finish, run an index rebuild - it should dramatically improve
> > > > things. *(Shoulda probably run this first - but too late now). *I run
> > > > this sql about once a month.

>

> > > >http://go.microsoft.com/fwlink/?LinkId=87027

>

> > > > That link comes from this page.
> > > >http://technet.microsoft.com/en-us/l...94(WS.10).aspx

>

> > > I should add, that I like to use the SQL Server Management Console todo
> > > this (rather than the oSQL way). *If you don't have SBS w' SQL Server,
> > > you can still download and install SQL Server Managment Studio Express
> > > (the free version). *Just be sure you get your version (SQL S 2005 or
> > > 2008 etc).

>

> > > To open the WSUS database, a Windows Internal database, put

>

> > > \\.\pipe\mssql$microsoft##ssee\sql\query

>

> > > in the Server name field.

>

> > > Then I'd go, File, New etc - and put paste the code in a save it as say
> > > "re-index WSUS database.sql"

>

> > > And then in future you can just File, Open it, and run it - or better,
> > > create a Maintenance Schedule for it.

>

> > > --
> > > Duncan.

>

> > Thanks for your second option - downloading SSMSE. I think it will be
> > much easier for me.
> > Which version is better? 2005 or 2008?

>
> I don't know, it's your server!
>
> What SBS are you running?
>
> The 2005 version should do just fine.
>
> SQL Server Managment Studio Express @ SP3 ....http://www.microsoft.com/downloads/d...5D76230D-580D-
> 4874-8C7D-93491A29DB15&displaylang=en
>
> --
> Duncan.

The server is SBS2K3 R2.
I will be looking into SSMSE 2008 first

On Feb 15, 2:01*pm, Jack <dontaskwhoiam2...@newsgroup> wrote:

> The server had WSUS 2.0 which was never used. The database file is
> 5.7GB
> I upgraded to WSUS 3.0 and then ran the cleanup wizard to try to
> shrink the db file.
>
> It's been 12 hours now. I am wondering how many more hours i should
> expect?
>
> Thanks
>
> j~

An update on this case
- another 12 hrs finished all.