Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bkscott
Starting Member
2 Posts |
 Posted - 2011-07-06 : 13:06:13
|
| Hello,I apologize if this has been posted before, I'm not even sure what to search for to try and find out what's going on. Basically, I have an SQL 2005 express database. This database is for my order processing software, called stoneedge. Stoneedge is a ms access based program that uses linked tables to connect to the sql database. One of the tables is for managing products, its called "inventory". This table has a "localsku" column, which is the primary key. the data type is varchar(200). For years the table worked fine, i could add as many skus as i wanted. then one day it started giving me issues with skus that start with the number 1. If a sku starts with a 1 then i cannot add it unless i kick everyone else out of our order managing software. I cannot even add the item directly into the database with an insert statement. Recently it started to get worse. now i cannot add any skus that start with an 8 or a 1, but if the sku starts with any other number or letter then it works fine. does anyone have any idea about what could be going on? the stoneedge tech support was unable to figure out the issue. They said it was related to the table indexing, hence the thread title. if you need more info from me then let me know. thanks |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-07-06 : 14:03:23
|
| are you applying table partitioning ?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
bkscott
Starting Member
2 Posts |
Posted - 2011-07-06 : 14:30:35
|
| I am not sure, but i will look into it. Thanks for the tip. |
|
|
|
|
|
|
weird issue, i think its index related