Rocky Smolin
rockysmolin at bchacc.com
Fri Mar 23 13:12:17 CDT 2012
Is there a good design reason to have a table with 430 fields or is this an indication of deficient design? Rocky On Fri, Mar 23, 2012 at 12:39 PM, jwcolby <jwcolby at colbyconsulting.com>wrote: > I received a new "database from hell" today. This one is actually CSV > format. It came with a table specification which in no way matches > the actual file. However it appears to be importing in with just a > few minor changes to the default 50 character default field width that > the SQL Server import wizard uses. > > The file came in a 24 gigabyte zip file. Expanded it is 250 gigs. > Way to large for even UltraEdit (my tried and true champion) to open. > So I was unable to preview the data. However I just used the SQL > Server import wizard to open the file and start looking at it. SQL > Server truly is an amazing piece of work. > > No firm idea yet on the number of rows though I was told well over 100 > million. 430 columns. > > -- > John W. Colby > Colby Consulting > > Reality is what refuses to go away > when you do not believe in it > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/**mailman/listinfo/accessd<http://database > advisors.com/mailman/listinfo/accessd> > Website: > http://www.databaseadvisors.**com<http://www.databaseadvisors.com> > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com