Painfully slow

[Brian Vallelunga]

I've got a diagram that I'm editing that is painfully slow to add or
edit columns in a table. Typing or most anything will lock up the
computer for several seconds. The table I am editing is fairly large
(200 columns).

Is this a known bug? I hope there's a workaround.

Thanks

 

[chrisb]

I would suggest, that if the table has 200 columns then there is
probably something wrong with your design. However, that doesn't
really solve your problem, although it is likely to be causing a
problem with visio because I imagine that when it was designed it was
thought that users would follow standard database design practices and
conventions. If, howeverm you have an exceptional circumstance which
necessitates 200 columns in a table, I fear you may have to put up with
it.

Have you thought about taking some of the columns out and putting them
into 1 - 1 / category relationships with the primary key?

Chris.

 

[Brian Vallelunga]

I would suggest, that if the table has 200 columns then there is
probably something wrong with your design. However, that doesn't
really solve your problem, although it is likely to be causing a
problem with visio because I imagine that when it was designed it was
thought that users would follow standard database design practices and
conventions. If, howeverm you have an exceptional circumstance which
necessitates 200 columns in a table, I fear you may have to put up with
it.

Have you thought about taking some of the columns out and putting them
into 1 - 1 / category relationships with the primary key?

Chris.

I have about 40 tables in my db in total. The one table with
approximately 250 columns is rather exceptional, but there is no good
reason to separate it into multiple tables (other than Visio's lack of
speed). This is for a mortgage industry application and this happens to
be the "Loan" table. There really are just a ton of columns, even after
normalization. For example, there are 20 columns holding the ids of
third parties that relate to the loan (appraiser, escrow, etc). The
table really is a logical unit of data that shouldn't need to be separated.

So any tips on speeding up Visio would still be appreciated, but thank
you for the concern about the schema.

Brian

 

[David Parker]

It still sounds like schema design issues ... a related table with combined
primary key of loanID and thirdPartyType, with a third column for
thirdPartyID might make good sense...