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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2001-05-15 : 09:20:22
|
G writes "Some background. We have 2 NT 2000 servers each with SQL 2000 on them. We plan to replicate the data from one SQLServer (ServerA) to the other server (ServerB). We plan to do this to provide us with a 'hotswap' senario in the event ServerA goes down or stops working.
The mode of replication we are using is transactional replication. ServerB set up as an updatable Subscriber. Done this way as our applications heavily use IDENTITY fields and the functionaility they provide. (When tried without updatable subscriptions structure of the dbase on ServerB contained no IDENTITY type fields)
Modifications on ServerA are replicated to ServerB as expected. The problem comes when we begin to test our 'hotswap' senario (i.e. ServerA is no longer available & ServerB becomes the 'live' database). The applications have no problem reading from the ServerB database.... However when attempt to insert new information onto ServerB, which is now live database, this cannot be done. The application generates the following message:-
'Updatable Subscriptions: The text/ntext/image values inserted at Subscriber will be NULL' state:37000; native 20508;Origin[Microsoft][ODBC SQL Server Driver][SQL Server]
I have simulated the insert command used in application, in the SQL Query Analyzer and get the same error message. Shown below:- Server: Msg 20508, Level 16, State 1, Procedure sp_MSreplraiserror, Line 4 Updatable Subscriptions: The text/ntext/image values inserted at Subscriber will be NULL.
I cannot find any further information on this message - hence this message. Am I expecting replication to do something that it cannot handle? Am I 'barking up the wrong tree'? Is there a way of turning off the updatable subscriber status in this senario?" |
|
|
|
|
|