Re: Force sp_post_xpload (DBCC REINDEX) to use more engines?

From	Antony <albion26.eve@gmail.com>
Newsgroups	comp.databases.sybase
Subject	Re: Force sp_post_xpload (DBCC REINDEX) to use more engines?
Date	2011-12-12 14:00 -0800
Organization	http://groups.google.com
Message-ID	<1585141.404.1323727211907.JavaMail.geo-discussion-forums@prmw6> (permalink)
References	<89550cd9-9383-47e4-9f72-00609e388869@u6g2000vbg.googlegroups.com>

Show all headers | View raw

We have done the same migration many times. You can't really use sp_post_xpload on databases over 10-20Gb as it's too slow (I'm not sure why, but it is). As Bret says, best to get a DDL script to drop all indexes except APL clustered and rebuild them on the Linux serer. You can also then make it 3 or 4 scripts to run concurrently.

Remember also you'll need to bcp out/in any tables with TEXT columns as these will likely be corrupted (the documentation isn't really clear on that point - we found out the hard way :)

Back to comp.databases.sybase | Previous | Next — Previous in thread | Find similar

Thread

Force sp_post_xpload (DBCC REINDEX) to use more engines? pow43 <faber_38@yahoo.no> - 2011-12-03 01:58 -0800
  Re: Force sp_post_xpload (DBCC REINDEX) to use more engines? bret_halford@msn.com - 2011-12-06 10:57 -0800
  Re: Force sp_post_xpload (DBCC REINDEX) to use more engines? Antony <albion26.eve@gmail.com> - 2011-12-12 14:00 -0800

csiph-web