New answers tagged transactional-replication
To make a table into a wide table, you must create sparse columns and also add a column set. If you don't create a column set your table will still be limited to 1024 columns. This is why you can't use replication for wide tables.
I have found a solution to my problem. Beware though, the steps outlined below broke regular replication (or so it seems). Nevertheless, I was able to get replication running, and now there are no undelivered commands building up in the distribution database: I Command You To Deliver Those Commands The solution provided there is to run: exec ...
Try looking into the SQL shipped view in the distribution database, MSdistribution_status. It lists the agent_id, article_id, as well as UndelivCmdsInDistDB (The number of commands pending delivery to Subscribers.). You should be able to join against msDistribution_agents and msArticles to match the pending commands to the exact table/subscription. You can ...
If you change a user's permissions to a particular table BEFORE a Subscriber has been initialized or reinitialized, if the article property Copy permissions is set to true, the permissions will be copied to the Subscriber when the snapshot is applied. If you change a user's permissions to a particular table AFTER a Subscriber has been initialized, the ...
First of all, you need to setup connectivity between these two servers on different domain with the help of the network administrator and update DNS entry as well. Create SQL login with same password on both server Make sure to connect SQL Server from one server to other server and vice versa using SQL login. Create publication on source server using agent ...
The "source" database is being referred to when the "publisher" database is discussed. Take a look at the below diagram from this reference, it shows it pretty well:
Yes, your publication database is your source database. There are some considerations when backing up the publication database, as well as other replicated databases, such as the distribution and subscription databases. This is covered in Strategies for Backing Up and Restoring Snapshot and Transactional Replication.
The good thing is that you offline the database and then dropped it. So the files will be around. Just attach them and you will be good to go. Always backup your database before doing anything like modifying, dropping, etc. Also, How to Rebuild the Distribution Database KB describes the steps if you dont have the files as well.
I Googled it -- http://www.sqlrepl.com/sql-server/accidentally-dropped-distribution-database/ -- try to follow his advice!
Top 50 recent answers are included