Grouper Users - Open Discussion List

[Chris Hyzer <>]

I think Shilen said his went a lot quicker on Oracle (~1 hour?), but somehow 
Duke's oracle is very quick (when he and I run the same data generation 
script, his oracle runs faster then mine).  Anyways, to answer your 
question... the generated DDL script can have indexes moved around wherever 
you want.  It might help a lot for the data massaging.  It will spit out the 
code to do incremental changes, but it might not be the most efficient thing. 
 If there are easy solutions with temporary indexes (e.g. on memberships 
table), let me know and we could perhaps add to the generated DDL, or at 
least let people know so they can save some time by manually changing it.

Btw, regarding the db drivers thing, I believe they should go into lib/custom 
(if that exists in the quick start) not lib/grouper, though I need to work 
more with the quick start to be sure.  If that is the case, I agree with TomZ 
where it would be a quicker start to put all the DB drivers into lib/custom 
(they would be the only jars there), and it wouldn't confuse the user as much 
as the jars hidden in the lib/grouper dir where all the other jars are...

Thanks,
Chris

> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Tom
> Zeller
> Sent: Friday, December 05, 2008 12:51 PM
> To: 
> 
> Subject: [grouper-users] upgrade time from 1.3 to 1.4 ?
>
> For anyone upgrading from grouper 1.3 to 1.4, I'm curious how long the
> upgrade takes.
>
> Whether upgrading in-place using the generated ddl script or creating
> a new database using xml-export/xml-import, we're looking at 6 to 7
> hours; we have approximately 1 million rows in grouper_memberships and
> use postgres.
>
> I wonder if I can speed up the upgrade process when using the ddl
> script by changing the order of operations, e.g. create indexes after
> copying tables. Or perhaps postgres is just slow.
>
> Thanks,
> TomZ