New answers tagged

0

We ended up coming up with a solution for this. Basically, we had to manage the partition creation for both the publisher and subscriber databases/tables when we made a change. We were loading data using SSIS and there were mechanics that were built in to create new partitions on the publisher, so we implemented the same logic to do the work on the ...


0

Yes it can be done like normal. 32/64 bit can replicate to each other (you wouldn't think so but they do and Microsoft has documented it on MSDN). Also you can have an AG as a subscriber but you must use the name of the listener when setting it up. There's an MSDN article for this as well.


1

User who runs the package must have access to the folder to which you are writing the file. User also needs access to SQL Server with sysadmin rights. Also, verify you have properly added all libraries. For more, please read my blog article at http://www.dbadrive.in/2013/03/ssis-package-to-backup-replication_25.html. Please share some more details of your ...


0

Don't forget you will need Enterprise Edition licensed for both nodes if you go down AG route with read only secondary, if your client is not going to use it for DR then its massive overkill in my opinion and very expensive. Transactional replication just requires standard edition and its very reliable if you set it up correctly and understand it, if there ...


0

The secondary replica can't be changed inside; and no you can't add indexes. You can do subsets and add indexes on the transactional subscriber of something but you will likely encounter issues if you ever need to modify your source tables (such as upgrading the application) or reload data for any other reason; it's good practice to remove it before any ...


1

So we're working now, I'm not 100% sure which part of this fixed the issue but I'm putting it down for if anyone else has this issue in the future where there doesn't seem a logical reason for the distribution growth. Our distributor is on a windows failover cluster across two machines along with a Reporting Instance (and a MSDTC). The issue occurred ...


0

When you have issues with transactional replication, you have to determine if the issue is with the logreader or with the distribution agent. You can determine this by running a tracer token. If the issue is with the logreader agent, you have to determine if it is the reader or the writer (is the problem with reading the transaction log, or is the problem ...



Top 50 recent answers are included