Jim Lawrence
accessd at shaw.ca
Sat Jan 22 00:31:12 CST 2005
Hi John: That of course depends on how must data you are working with.... How many GBs... I do not think there is any faster way but if faced with the problem of a huge DB, I would set them all a once, after checking to see if there was plenty of hard drive space, set them all and go to bed... and everything will be done by the morning, next or some other. I recently heard of some MS fellow who was working on some gargantuan multi-partitioned OLAP SQL farm and adding the indexing took five days. So anything under that is just bonus. My two cents worth Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John W. Colby Sent: Friday, January 21, 2005 9:32 PM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Adding indexes on fields Does anyone know whether it is faster to add many indexes to a table all at once or each index one at a time? I have tables where I need to index every field. I am looking at writing TSQL code to add indexes and just need to know if I can do all the fields simultaneously, and if so is it slower or faster than doing so one at a time. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com