Viewing 10 posts - 61 through 70 (of 70 total)
Yes, I am executing from Principal database.
March 19, 2009 at 4:13 am
I had added the ports to exceptional list and by using the script posted by eng_mgomaa, I can able to setup the principal and mirror. The failover is also...
March 18, 2009 at 4:29 pm
Sorry guys for replying late. I am on leave.
I am using the below T-SQL Statment,
ALTER DATABASE Mirroring_DB1
SET Partner='TCP://MirrorServer:5022'
Now I am chasing my IT team to add the port 5022...
March 18, 2009 at 8:27 am
I tried using TSQL and Wizard both are giving the same error. My mirroring endpoints are referring to 5022 port only. Only my sql server on Mirror server is...
March 10, 2009 at 5:39 am
Here is the error --> The server network address "TCP://Mirror,1434:5022" can not be reached or does not exist. Check the network address name and that the ports for the local...
March 9, 2009 at 9:12 am
And Stored Proc's are schema authenticated and I had provide only execute permission on the schema.
February 17, 2009 at 8:54 am
Thanks.
February 11, 2009 at 3:00 am
Even I am facing this issue. We were in the testing phase to implement Database Mirroring. I had built mirroring with a witness to make the fail over automatically. ...
February 11, 2009 at 2:56 am
Thanks Paresh Prajapati. I checked only in sys.sysobjects before posting :rolleyes:.
Thanks GSquared, I will consider using DDL Triggers. Can you help me with best practice documents?
Thanks for everyone.
February 10, 2009 at 11:08 am
Viewing 10 posts - 61 through 70 (of 70 total)