Hello all,I’m working in company that sells a SQL based products. I was asked to solve a bug in one of the products which has a transactional replication. When our QA team tried to setup the replication, they got an error massage that the working directory for one of the snapshots is too long. When I checked, I found out that the working directory was indeed 251 characters long, while the maximum length possible is 248 characters. I’ve explained it to the QA team, but they did not accept my answer, because it did work in previous versions, and neither the publications’ name and the computer’s name changed. I’ve looked again, and this time I used an old script to remove and rebuild the replication. It worked. I received no error messages and the replication monitor showed that all publications are published. The difference was that when I used the scripts, the working directory did not include the FQDN name of the computer, but only its own name. At first, my guess was that it worked because both the secondary and the primary are in the same domain. Then I realized that according to the documentation the FQDN can be longer then the working directory, so clearly, at least in some cases I do not have to use the FQDN as part of the path of the working directory. My question is, if the replication is between 2 different domains, can I avoid using FQDN in the working directory for the publication? And if I can, can I simply use the host name of the server?I would have tried it myself, but I do not have a testing environment, and the QA team does not work on Sundays.TIA,Shmulik
↧