Same also applies for LS in case of Recovery model is full, it can hold transactions till log file grows. Only +ve point of LS over log size is that...

Hi,

If I understand your problem correctly, are you trying to delete publication or article, please clarify.

Meanwhile, below table you can query which will give you all details about articles, publications...

I agree each method has it's advantage and disadvantage but I prefer attach/deattach as it is faster compared to backup/restore.

Hi All,

I did this in my Production Environment and it seems to be working fine....

Guys,

I have resolved this issue by doing following things

1) There was a trigger on AlertArchive table which was not set for not for replication, once I modified that trigger with...

Guys,

here is what I have tried out and it worked for me in my senario.

1) Delete publication and subscriptions.

2) Disable publication and distribution.

3) Reset replication and this time move distribution...

I would suggest you to work on bringing principal and mirroring in sync state and your replication will work fine.

I would say that when this happens best option is to first add additional log file size at the diff drive which has quite free space. Than take all remedy...

I would say that when this happens best option is to first add additional log file size at the diff drive which has quite free space. Than take all remedy...

Which 3rd party tool are you using to take backups ?

Could you tell us in detail about windows firewall and which tcp port sql server was listening in past. Did you check event logs for more info.

One simple way I think of is to make is easy.

Script out all sps together in one .sql file. Search for tablename in that .sql file where you have done...

One thing I would suggest is that while testing in DR, ensure that you script out everything and use the scripts in production by few changes.

Ensure that you take backups...

Also as mentioned above use of sqlcmd, you can run the above test.sql file across multiple servers by using batch mode. List down all servernames in text file and read...

you can also verify using job history.