forced restore

What does the field "Logical File Name" mean in the Restore Database Screen?
If I use Forced Restore, does this not place the database INTO the database I
am restoring to including the current physical file paths?
A logical file name is a user-defined name used to represent a physical
database file or transaction log. Forcing a restore of a database
overwrites (replaces) the current database using the file paths recorded in
the backup.
HTH
J
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
> What does the field "Logical File Name" mean in the Restore Database
> Screen?
> If I use Forced Restore, does this not place the database INTO the
> database I
> am restoring to including the current physical file paths?
|||That is what I thought. I could call the logical file name "Snoopy" but it
would not effect the physical file name. As long as the database is hooked
to the physical file name/location I would be good to go.
"Jerry Spivey" wrote:

> A logical file name is a user-defined name used to represent a physical
> database file or transaction log. Forcing a restore of a database
> overwrites (replaces) the current database using the file paths recorded in
> the backup.
> HTH
> J
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
>
>
|||BOL says that the Logical file Name is used to refer to file in TSQL. Does
this mean my stored procedures will break?
"Jerry Spivey" wrote:

> A logical file name is a user-defined name used to represent a physical
> database file or transaction log. Forcing a restore of a database
> overwrites (replaces) the current database using the file paths recorded in
> the backup.
> HTH
> J
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
>
>
|||Hi,
No, it is not going to break any thing. A Logical name is a name used by SQL
Server to identify a file.
Thanks
Hari
SQL Server MVP
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:EF107FA3-5C4E-4340-B90D-D7E497C10913@.microsoft.com...[vbcol=seagreen]
> BOL says that the Logical file Name is used to refer to file in TSQL.
> Does
> this mean my stored procedures will break?
> "Jerry Spivey" wrote:
sql

forced restore

What does the field "Logical File Name" mean in the Restore Database Screen?
If I use Forced Restore, does this not place the database INTO the database
I
am restoring to including the current physical file paths?A logical file name is a user-defined name used to represent a physical
database file or transaction log. Forcing a restore of a database
overwrites (replaces) the current database using the file paths recorded in
the backup.
HTH
J
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
> What does the field "Logical File Name" mean in the Restore Database
> Screen?
> If I use Forced Restore, does this not place the database INTO the
> database I
> am restoring to including the current physical file paths?|||That is what I thought. I could call the logical file name "Snoopy" but it
would not effect the physical file name. As long as the database is hooked
to the physical file name/location I would be good to go.
"Jerry Spivey" wrote:

> A logical file name is a user-defined name used to represent a physical
> database file or transaction log. Forcing a restore of a database
> overwrites (replaces) the current database using the file paths recorded i
n
> the backup.
> HTH
> J
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
>
>|||BOL says that the Logical file Name is used to refer to file in TSQL. Does
this mean my stored procedures will break?
"Jerry Spivey" wrote:

> A logical file name is a user-defined name used to represent a physical
> database file or transaction log. Forcing a restore of a database
> overwrites (replaces) the current database using the file paths recorded i
n
> the backup.
> HTH
> J
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
>
>|||Hi,
No, it is not going to break any thing. A Logical name is a name used by SQL
Server to identify a file.
Thanks
Hari
SQL Server MVP
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:EF107FA3-5C4E-4340-B90D-D7E497C10913@.microsoft.com...[vbcol=seagreen]
> BOL says that the Logical file Name is used to refer to file in TSQL.
> Does
> this mean my stored procedures will break?
> "Jerry Spivey" wrote:
>

forced restore

What does the field "Logical File Name" mean in the Restore Database Screen?
If I use Forced Restore, does this not place the database INTO the database I
am restoring to including the current physical file paths?A logical file name is a user-defined name used to represent a physical
database file or transaction log. Forcing a restore of a database
overwrites (replaces) the current database using the file paths recorded in
the backup.
HTH
J
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
> What does the field "Logical File Name" mean in the Restore Database
> Screen?
> If I use Forced Restore, does this not place the database INTO the
> database I
> am restoring to including the current physical file paths?|||That is what I thought. I could call the logical file name "Snoopy" but it
would not effect the physical file name. As long as the database is hooked
to the physical file name/location I would be good to go.
"Jerry Spivey" wrote:
> A logical file name is a user-defined name used to represent a physical
> database file or transaction log. Forcing a restore of a database
> overwrites (replaces) the current database using the file paths recorded in
> the backup.
> HTH
> J
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
> > What does the field "Logical File Name" mean in the Restore Database
> > Screen?
> > If I use Forced Restore, does this not place the database INTO the
> > database I
> > am restoring to including the current physical file paths?
>
>|||BOL says that the Logical file Name is used to refer to file in TSQL. Does
this mean my stored procedures will break?
"Jerry Spivey" wrote:
> A logical file name is a user-defined name used to represent a physical
> database file or transaction log. Forcing a restore of a database
> overwrites (replaces) the current database using the file paths recorded in
> the backup.
> HTH
> J
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
> > What does the field "Logical File Name" mean in the Restore Database
> > Screen?
> > If I use Forced Restore, does this not place the database INTO the
> > database I
> > am restoring to including the current physical file paths?
>
>|||Hi,
No, it is not going to break any thing. A Logical name is a name used by SQL
Server to identify a file.
Thanks
Hari
SQL Server MVP
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:EF107FA3-5C4E-4340-B90D-D7E497C10913@.microsoft.com...
> BOL says that the Logical file Name is used to refer to file in TSQL.
> Does
> this mean my stored procedures will break?
> "Jerry Spivey" wrote:
>> A logical file name is a user-defined name used to represent a physical
>> database file or transaction log. Forcing a restore of a database
>> overwrites (replaces) the current database using the file paths recorded
>> in
>> the backup.
>> HTH
>> J
>>
>> "Rich" <Rich@.discussions.microsoft.com> wrote in message
>> news:88903866-D597-4693-A0AC-207DDA17A90F@.microsoft.com...
>> > What does the field "Logical File Name" mean in the Restore Database
>> > Screen?
>> > If I use Forced Restore, does this not place the database INTO the
>> > database I
>> > am restoring to including the current physical file paths?
>>