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 |
|
admin001
Posting Yak Master
166 Posts |
 Posted - 2002-07-31 : 04:30:03
|
| Hello ,I want to drop a table from a publication , so that i can copy some data from another server . After the copy , i want to add the article or the table back again to the publication without making any changes to the subscribers configuration .Is it really possible on SQL 7.0 ? Right now it does not allow me to copy the data to the published table or even drop the article (table) and it says that the article is published for replication and cannot be dropped or modified .The table is configured for transactional replication . I will have to drop the entire publication and create all the subcribers again . Any help in this regard please . Sameer |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-07-31 : 08:44:58
|
| I'd love to do things like that to.You have exactly the same setup as one of our SQL Servers.Although you could remove individual tables with SQL Server 6.5 they removed the option in SQL7 ?? Unfortunately as you say you'll have to stop it all - make changes - and start it all again.One of the hassles with SQL7 i'm afraid. I even took this up with a guy from Microsoft in an on-line conference and he sort of skirted around the issue saying you can do it in SQL2K. I got no explanation as to why it was removed for the SQL7 release ??Paul |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-07-31 : 09:09:46
|
| There were a lot of fundamental architecture changes from 6.5 to 7.0 that required a lot of features to change radically or be removed outright. I haven't seen anything specific regarding replication, maybe Chadmat has some inside skinny on this, but in all likelihood it probably fell by the wayside for the sake of getting replication up and running. Replication was also greatly enhanced from 6.5, so that probably helped lose this feature in the shuffle. And SQL 7.0 was delayed...and delayed...My favorite missing feature from 6.5? LOAD TABLE. You could restore a single table from a backup. Now you have to go through all kinds of gymnastics to do the same thing. To be fair there are very good reasons NOT to allow loading an individual table, but these reasons were all spelled out in the documentation at the time. If you had problems resulting from LOAD TABLE, well, you were warned at least.And I have a sneaking suspicion that LOAD TABLE and dropping individual articles ended up causing a lot of complaints from people who did it incorrectly and corrupted their databases, so MS might've decided "people are too stupid to do this correctly, let's get rid of it" on the assumption that if you were smart enough to do it correctly you were very likely smart enough to work around it. |
|
|
|
|
|
|
|
|
Modifying publication in SQL 7.0 . Help required .