Fields for Products table

[MikeMCSD]

I have a Products table that I am about to add 5000
products to. But before I do, I want to make sure I
have all fields I might need.
If anyone has any suggestions on what I have now or
can think of anything I should add, please let me know.
Products table:
ProductID
CategoryID
SupplierID
ProductNumber
Name 50
Description 200
Price
ImagePath 50
ThumbImagePath 50
Engraving (bit field)

Some products have engraving available. Should I include
a field that should be checked for this each time the
products are read from the database?

Also, would it be a good idea to add a SalesPrice field
that I could later use as a calculated column for a sale?

My main concern is that I don't want to add too many fields
and hurt the performance of the database.

I don't need inventory data because I don't have inventory!

Thanks

 

[SQLSister]

I would suggest a PriceDate field. It is helpful to be able to identify outdated prices. Also we store both our price and the MSRP. That way we can check to make sure our sales guys don't accidentally price something higher than the list price.

Questions about posting. See faq183-874

 

[MikeMCSD]

thanks sister ...

I also added a search field that will contains more words
for searches. Also added a weight field.

Right now I have about 13 fields.

How many fields can a table like this one handle before
performance is hurt?