| Author |
 Topic  |
|
|
the agony booth
Starting Member
19 Posts |
 Posted - 30 January 2007 : 18:24:50
|
Hi,
I'm upgrading a v 3.4.04 forum from Access 2000 to MS SQL 2005. I'm running into an issue when trying to DTS in the data for the FORUM_SUBSCRIPTIONS table.
It's complaining that SUBSCRIPTION_ID can't be null. When I go back and look at the original data in Access, this field is indeed null for all records in FORUM_SUBSCRIPTIONS. So there must be a bug in 3.4.04, or I just messed up the last time I upgraded the code.
Does anyone have any ideas of how I can get around this?
I know I could just import the subscription data to a temporary (work) table and then insert those records into FORUM_SUBSCRIPTIONS. However, I won't be the one doing the DTS, and I want to keep the process as simple as possible.
I also considered creating the table with SUBSCRIPTION_ID being nullable, then doing an Alter Table to change it back to an identity, but at the moment I don't know how well that will work.
The only other option I can think of is just not importing subscription data, and making people resubscribe. I might do that unless there's a better option.
|
http://www.agonybooth.com/ |
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 30 January 2007 : 18:34:45
|
| I would just not bother importing the subscription data, and post a topic telling users there was a problem and could they resubscribe (will have the positive effect of probably reducing the number of subscriptions you have too ) |
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
the agony booth
Starting Member
19 Posts |
Posted - 30 January 2007 : 21:12:21
|
I tried unchecking the "enable identity insert" for just the FORUM_SUBSCRIPTIONS table, but no luck. Same error message about inserting nulls into that column. I'll probably just tell all my users that subscriptions were *cough*lost*cough*.
Thanks guys!
|
http://www.agonybooth.com/ |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 31 January 2007 : 06:16:36
|
| Was the column created as an identity column? It should have been... Check whether it was, and if it wasn't, make it an identity column and then transfer the data for the table again, with enable identity insert unchecked. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
| |
Topic |
|
Topic Locked
