﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Perry Whittle  / Using Disparate File Paths in SQL Server Database Mirroring  / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 18 Jun 2013 20:01:02 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Thank you, please don't forget to rate the article</description><pubDate>Wed, 27 Apr 2011 14:13:36 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Nice tip. Thanks for the post.</description><pubDate>Wed, 27 Apr 2011 11:08:00 GMT</pubDate><dc:creator>SQLKnight</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Location:	 recovery.cpp:3080Expression:	 m_recType != REPLICASPID:		 54Process ID:	 1748Msg 1823, Level 16, State 1, Line 1A database snapshot cannot be created because it failed to start.Msg 1823, Level 16, State 2, Line 1A database snapshot cannot be created because it failed to start.Msg 3624, Level 20, State 1, Line 1A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. Msg 9003, Level 20, State 5, Line 1The log scan number (45:1518:0) passed to log scan in database 'Mirror_Test' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. I also attached SQLdump file.--SQL Server Version --  Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)   Dec 10 2010 10:56:29   Copyright (c) 1988-2005 Microsoft Corporation  Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)</description><pubDate>Fri, 04 Mar 2011 05:55:13 GMT</pubDate><dc:creator>tuntun</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>[quote][b]tuntun.oo (3/3/2011)[/b][hr]Excellent article.It gave me new trick.After testing with new File Group and File at principal, mirroring works.But, I cannot create database snapshot at mirror.Before adding File, the following one worked.    CREATE DATABASE Mirror_Test_snapshot ON     ( NAME = N'Mirror_Test_Data',      FILENAME =  N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Mirror_Test_Data_snapshot.snap')     AS SNAPSHOT OF Mirror_Test; After adding File at Node1\Mirror_Test_FG_IDX_1.Mirror_Test_FG_IDX_1.ndf  at principalRestoring at Node2\Mirror_Test_FG_IDX_1.ndf  at mirror, this one doesn't work.    CREATE DATABASE Mirror_Test_snapshot ON     ( NAME = N'Mirror_Test_Data',      FILENAME =  N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Mirror_Test_Data_snapshot.snap'),     (NAME = N'Mirror_Test_FG_IDX_1',      FILENAME =  N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Node2\Mirror_Test_FG_IDX_1_snapshot.snap')     AS SNAPSHOT OF Mirror_Test;[/quote]do you get an error message, if so what is it?</description><pubDate>Thu, 03 Mar 2011 15:03:24 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Excellent article.It gave me new trick.After testing with new File Group and File at principal, mirroring works.But, I cannot create database snapshot at mirror.Before adding File, the following one worked.    CREATE DATABASE Mirror_Test_snapshot ON     ( NAME = N'Mirror_Test_Data',      FILENAME =  N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Mirror_Test_Data_snapshot.snap')     AS SNAPSHOT OF Mirror_Test; After adding File at Node1\Mirror_Test_FG_IDX_1.Mirror_Test_FG_IDX_1.ndf  at principalRestoring at Node2\Mirror_Test_FG_IDX_1.ndf  at mirror, this one doesn't work.    CREATE DATABASE Mirror_Test_snapshot ON     ( NAME = N'Mirror_Test_Data',      FILENAME =  N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Mirror_Test_Data_snapshot.snap'),     (NAME = N'Mirror_Test_FG_IDX_1',      FILENAME =  N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Node2\Mirror_Test_FG_IDX_1_snapshot.snap')     AS SNAPSHOT OF Mirror_Test;</description><pubDate>Thu, 03 Mar 2011 12:53:16 GMT</pubDate><dc:creator>tuntun</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>GuysThank you very much for all your kind replies I'm glad you find it useful[quote][b]george sibbald (3/1/2011)[/b][hr]I think the lesson to take away though is to set your live and failover servers up with exactly the same drive\directory structures in the first place. :-)[/quote]George I couldn't agree more, although sometimes you may inherit a system and will have to roll with it. This is especially for these types of systems</description><pubDate>Tue, 01 Mar 2011 19:44:51 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Nice article Perry.  Thanks</description><pubDate>Tue, 01 Mar 2011 14:02:22 GMT</pubDate><dc:creator>SQLRNNR</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Thank you very much for the article, it is good to learn about the pitfalls before actually falling into them.</description><pubDate>Tue, 01 Mar 2011 13:17:04 GMT</pubDate><dc:creator>UMG Developer</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>nice article Perry and very useful info.I think the lesson to take away though is to set your live and failover servers up with exactly the same drive\directory structures in the first place. :-)</description><pubDate>Tue, 01 Mar 2011 11:06:58 GMT</pubDate><dc:creator>george sibbald</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Hi Perry,Another good article, thanks for the tip!CheersJohn</description><pubDate>Tue, 01 Mar 2011 02:40:06 GMT</pubDate><dc:creator>john.knight-557608</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>good article and good tip for addining files without the need to do a full backup and restore.</description><pubDate>Tue, 01 Mar 2011 02:32:42 GMT</pubDate><dc:creator>dave-dj</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>[quote][b]dibbydibby (3/1/2011)[/b][hr]nice article. one question?in your backup TLog statement did you mean to say.... [code="sql"]BACKUP [b]DATABASE[/b] AdventureWorks TO DISK = '\\hanode1\backup\AdventureWorks_createnewfile.trn' WITH INIT[/code]?[/quote]Hiwell spotted, no the backup and the restore statement should readBACKUP LOGRESTORE LOGRegardsPerry</description><pubDate>Tue, 01 Mar 2011 02:16:41 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>nice article. one question?in your backup TLog statement did you mean to say.... [code="sql"]BACKUP [b]DATABASE[/b] AdventureWorks TO DISK = '\\hanode1\backup\AdventureWorks_createnewfile.trn' WITH INIT[/code]?</description><pubDate>Tue, 01 Mar 2011 02:13:25 GMT</pubDate><dc:creator>dibbydibby</dc:creator></item><item><title>RE: Using Disparate File Paths in SQL Server Database Mirroring</title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Excellent tip to "trick" SQL into thinking we did a full backup/restore of the DB to be able to move the new database file.Cheers,Steve</description><pubDate>Mon, 28 Feb 2011 22:30:18 GMT</pubDate><dc:creator>S. Kusen</dc:creator></item><item><title>Using Disparate File Paths in SQL Server Database Mirroring </title><link>http://www.sqlservercentral.com/Forums/Topic1070983-1452-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Database+Mirroring/72294/"&gt;Using Disparate File Paths in SQL Server Database Mirroring &lt;/A&gt;[/B]</description><pubDate>Mon, 28 Feb 2011 22:29:17 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item></channel></rss>