New answers tagged transactional-replication
You need to look at the actual catalog/metadata table(s) and clean them up. The GUI and stored procedures often don't cleanup the underlying tables properly. So, after you have run the sp_dropsubscription SP run a select from MSsubscriptions and MSsubscriptions to see if there is any data referring to your unwanted subscriptions. See: ...
You can update the registry of the Subcriber here you will see the actual status select * from [Publish_Database]..syssubscriptions here the update for all articles subscribes update [Publish_Database]..syssubscriptions set status=2 where srvname='server' After that the snapshot should become effective again
Use the built-in bitwise operators to examine the column. For example select schema_option & 0x01 AS GeneratesObjectCreation, schema_option & 0x02 AS GenerateCustomSP, ... etc.
This can be done. But as far as i know, it will break the replication.You'll have to enable the option and re-initialize the subscriber with a new snapshot. Also, if you have non-clustered indexes with INCLUDED, you'll have to modify the definitions (.IDX files) manually to add INCLUDED to them. You can enable the option where you can replicate the non ...
The schema on the left is your own DDL statement. The schema on the right is a DDL statement generated by your schema comparison tool. The statement on the right shows constraint names for your DEFAULT constraints. Yours does not have them but that does not mean SQL Server allows you to create a nameless constraint. When you do not provide a name ...
Top 50 recent answers are included