如果字段名称很长，ASP查询会很慢吗？ [英] Will ASP query be slow if field names are lengthy?
问题描述
我在一个表中有一个包含58个字段的Access数据库。我写了很多
的字段名称，以便它们具有描述性，以便其他人可以在未来弄明白。例如，一个字段名称被称为
MissingPart14990aDescribe。
我应该担心字段名称的长度吗？我期待每年将大约20,000条记录输入数据库。那么，从现在起5年b $ b年，这将是大约100,000条记录，由于字段名称大小，
query.asp对于记录列表会变慢吗？ BTW，
query.asp只会显示最近3个月的价值
记录的列表，只显示58个字段中约6个的快照。
TIA
ynott，
这是一个非常糟糕的主意为了描述添加额外的列，只需创建一个
readme.txt而不是描述你的表。否则你最终会得到一个带有不必要信息的大型数据库。
列，而不是字段.....
从不在页面中列出超过100个......如果需要，请使用分页......如果
你的数据库将会那么大你可能会考虑使用SQL Server
。
/ Lasse
" ynott" <炔*** @ hotmail.com>在消息中写道
news：77 ******************************** @ 4ax.com ...我有一个Access数据库，在一个表中有58个字段。我写了许多字段名称，以便它们具有描述性，以便其他人可以在将来弄清楚它。例如，一个字段名称被称为
MissingPart14990aDescribe。
我是否应该担心字段名称的长度？我期待每年大约有20,000条记录进入数据库。那么，从现在开始的五年，这将是大约100,000条记录，由于字段名称大小，
query.asp的记录列表会变慢吗？顺便说一下，query.asp只显示过去3个月的
记录列表，只显示58个字段中约6个的快照。
TIA
Lasse Edsvik于2004年12月7日在
microsoft.public.inetserver.asp.general写道：
为了描述添加额外的列是一个非常糟糕的主意，只需创建一个readme.txt而不是描述你的表。否则你会得到一个非常大的数据库，里面有不必要的信息。
列，不是字段......
从不列出超过100个在页面中......如果需要，使用分页......
如果你的数据库很大，你可能会考虑使用SQL Server代替。
ynott <炔*** @ hotmail.com>在消息中写道
新闻：77 ******************************** @ 4ax.com ... < blockquote class =post_quotes>我有一个Access数据库，在一个表中有58个字段。我写了许多字段名称，以便它们具有描述性，以便其他人可以在将来弄清楚它。例如，一个字段名称被称为
MissingPart14990aDescribe。
我是否应该担心字段名称的长度？我希望每年大约有20,000条记录进入
数据库。因此，从现在开始的五年（大约10万条记录），由于字段名称大小的原因，记录列表的query.asp会变慢吗？顺便说一下，query.asp只会显示最近3个月的记录列表，而且只显示大约6个
58个字段的快照。
[这就是topposting会发生的事情：
不可理解的答案，因为你必须向下滚动
个别问题一次又一次。
请在usenet上使用interposting。]
记录有字段，HTMLtables有行和列，数据库表
是随机的记录集合，由于随机性，
记录不应该被称为行。
-
Evertjan。
荷兰。
（用我的电子邮件地址替换所有带点的十字架）
Evertjan。写道：
记录有字段，HTMLtables有行和列，数据库表
是随机的记录集合，并且由于随机性，
记录不应该'不要被称为行。
LOL
尝试运行Joe Celko的声明，看看会发生什么。
Bob Barrows
PS。你已经向后退了Evertjan。
-
Microsoft MVP - ASP / ASP.NET
请回复新闻组。这个电子邮件帐户是我的垃圾邮件陷阱所以我
不经常检查它。如果您必须离线回复，请删除
无垃圾邮件
I have an Access database with 58 fields in one table. I wrote many
of the field names so that they were descriptive so that others could
figure it out in the future. As an example, one field name is called
MissingPart14990aDescribe.
Should I be worried about the length of the field name? I''m expecting
about 20,000 records a year to be entered into the database. So, five
years from now, which would be about 100,000 records, will the
query.asp for a list of records be slow due to field name size? BTW,
the query.asp would just show a list of the last 3 months worth of
records and only a snapshot of about 6 of the 58 fields.
TIA
ynott,
Its a very bad idea to add extra columns just for description, Just create a
readme.txt instead were you describe your tables. Else you''ll end up with a
really big database with unnecessary information.
columns, not fields.....
Never list more than 100 in a page...... use paging if needed...... and if
your database is going to be that large you might consider using SQL Server
instead.
/Lasse
"ynott" <yn***@hotmail.com> wrote in message
news:77********************************@4ax.com...I have an Access database with 58 fields in one table. I wrote many
of the field names so that they were descriptive so that others could
figure it out in the future. As an example, one field name is called
MissingPart14990aDescribe.
Should I be worried about the length of the field name? I''m expecting
about 20,000 records a year to be entered into the database. So, five
years from now, which would be about 100,000 records, will the
query.asp for a list of records be slow due to field name size? BTW,
the query.asp would just show a list of the last 3 months worth of
records and only a snapshot of about 6 of the 58 fields.
TIA
Lasse Edsvik wrote on 07 dec 2004 in
microsoft.public.inetserver.asp.general:
Its a very bad idea to add extra columns just for description, Just
create a readme.txt instead were you describe your tables. Else you''ll
end up with a really big database with unnecessary information.
columns, not fields.....
Never list more than 100 in a page...... use paging if needed......
and if your database is going to be that large you might consider
using SQL Server instead.
"ynott" <yn***@hotmail.com> wrote in message
news:77********************************@4ax.com...I have an Access database with 58 fields in one table. I wrote many
of the field names so that they were descriptive so that others could
figure it out in the future. As an example, one field name is called
MissingPart14990aDescribe.
Should I be worried about the length of the field name? I''m
expecting about 20,000 records a year to be entered into the
database. So, five years from now, which would be about 100,000
records, will the query.asp for a list of records be slow due to
field name size? BTW, the query.asp would just show a list of the
last 3 months worth of records and only a snapshot of about 6 of the
58 fields.
[This is what happens with topposting:
ununderstandable answers, because you have to scroll down for the
individual questions again and again.
Please use interposting on usenet.]
Records have fields, HTMLtables have rows and columns, Database tables
are a random collection of records, and because of the randomness the
records shouldn''t be called rows.
--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)
Evertjan. wrote:
Records have fields, HTMLtables have rows and columns, Database tables
are a random collection of records, and because of the randomness the
records shouldn''t be called rows.
LOL
Try running that statement by Joe Celko and see what happens.
Bob Barrows
PS. You''ve got it backwards Evertjan.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don''t check it very often. If you must reply off-line, then remove the
"NO SPAM"
这篇关于如果字段名称很长，ASP查询会很慢吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
