its not good for us to loose the 15mts worth of data because once's the Dallas DB server becomes the primary, it starts its record from where the last replication...

Please send the error message.

Seems to me it is an OS issue.

http://support.microsoft.com/kb/972797

Better test before changing.

Is your problem got resolved?

Read more on filestream

http://www.sqlskills.com/blogs/paul/category/filestream/

Yes it does effect logshipping. To avoid this add both ip's in dns entry to point at sql server and run the ipconfig /flushdns after adding them in dns....

Thanks for the article. This problem is new to me.

Regards,

Ram

Please post the error message.

Regards,

Ram,

MCTS,MCITP

Assign db_executor, db_datareader, db_datawriter roles to user.

Please provide the results for the below query.

SELECT DB_NAME(DATABASE_ID) 'DBNAME',mirroring_state,

mirroring_state_desc,mirroring_role,

mirroring_redo_queue,mirroring_redo_queue_type,*

FROM sys.database_mirroring

WHERE mirroring_guid IS NOT NULL

Regards,

Ram,

MCTS,MCITP

This might be helpful you.

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/3bf06a9b-6689-4c74-87ee-3f070862ad1d/

Do you have any HA/DR experience?

Yes it is possible but why you want to do that when the logshipping already been configured on the same databases?

There is no default threshold for datbase mirroring send queue or redo queue..

Please share the link you read.

http://msdn.microsoft.com/en-us/library/ms408393.aspx#PerfMetricsAndWarningThresholds

Regards,

RamaSankar

MCTS,MCITP

Thanks for the link..