Without knowing more about what constitutes a StockItem, it's hard to say. However this:
[Description1] [varchar](255) NOT NULL,
[Description2] [varchar](255) NULL,[Description2] [varchar](255) NULL,
[Description3] [varchar](255) NULL,
Absolutely freaks me out. That's very much an indication of a place where we can do some normalization to arrive at a better database design.
It's possible that you need to have another table (or probably tables) that let's you define the attributes of distinct types of StockItems, but it's hard to say without knowing more about the requirements.
+100
😎
What is the data used for?
BTW: Suggest you profile the data and if you have a repetition of non-numerical values, then you should start by popping those into a separate table(s).