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?
>>

Force to close existing connections when restoring existing database

Hi All,

I would like to restore database using RESTORE DATABASE ... REPLACE command.

If database exists already and has any open connections this command will fail.

I would like to close all existing connections to specific database before running RESTORE DATABASE ... REPLACE command.

I can do closing from Management Studio using checkbox "Close Existing Connection" when deleting database. Actually I need to do the same but from script.

Please advice me how to do it.

Thanks in advance,

Roman

use the following query...

Code Snippet

use master;

alter database <data base>

set offline with rollback immediate

alter database <data base>

set online with rollback immediate

|||

Thanks a lot,

Roman

force process termination on restore

Sorry if this is a dumb question, but we have several production databases
that get automatically backed up, Rar'd, FTP'd internally and then restored.
Problem is, if someone has a process open against the restored database (IE:
a report is being run or something) the restore fails.
There must be a way of making the restore wait until a process is finsihed
or to force a termination of any process (altho probably not a good practice)
that is running.
Basically, I'm just looking for a better backup/restore process. Any ideas?
Hi,
There are 2 approaches...
1. If you are restoring in non production then you could disconnect all the
users using below command
ALTER database <dbname> set single_user with rollback immediate
go
Restore database
go
ALTER database <dbname> set multi_user
2. Write a loop sort to check the sysprocesses table for this particular
database for any running process . If there
is any running processes
start1:
if (select status from master..sysprocesses where status='runnable' and
db_name(dbid)='pubs')>1
waitfor delay(......) -- set 1 minutedelay
goto start1
else
kill all the users connected
restore the database
I recommend the first method for development and test server databases.
Thanks
Hari
MCDBA
"Jason" <Jason@.discussions.microsoft.com> wrote in message
news:03CD2B22-81B6-4EB1-B782-A86E2C6EF9A1@.microsoft.com...
> Sorry if this is a dumb question, but we have several production databases
> that get automatically backed up, Rar'd, FTP'd internally and then
restored.
> Problem is, if someone has a process open against the restored database
(IE:
> a report is being run or something) the restore fails.
> There must be a way of making the restore wait until a process is finsihed
> or to force a termination of any process (altho probably not a good
practice)
> that is running.
> Basically, I'm just looking for a better backup/restore process. Any
ideas?
|||Jason,
I had the same problem and wrote the following code to kill the users
connected to the database when I wanted to do to restore. Would this help
you?
***************************************
use master
go
select p.spid, d.name
into #temp_who
from sysprocesses p
join sysdatabases d on
p.dbid = d.dbid
where d.name = 'PUBS'
DECLARE @.objName int, @.sql NVARCHAR(50)
SET @.objName = 0
WHILE @.objName IS NOT NULL
BEGIN
SELECT @.objName = MIN(spid)
FROM #temp_who
WHERE spid > @.objName
IF @.objName IS NOT NULL
BEGIN
--Insert code to do stuff here.
set @.sql = 'kill ' + cast(@.objName as nvarchar)
exec sp_executesql @.sql
END
END
Good luck.
"Jason" <Jason@.discussions.microsoft.com> wrote in message
news:03CD2B22-81B6-4EB1-B782-A86E2C6EF9A1@.microsoft.com...
> Sorry if this is a dumb question, but we have several production databases
> that get automatically backed up, Rar'd, FTP'd internally and then
restored.
> Problem is, if someone has a process open against the restored database
(IE:
> a report is being run or something) the restore fails.
> There must be a way of making the restore wait until a process is finsihed
> or to force a termination of any process (altho probably not a good
practice)
> that is running.
> Basically, I'm just looking for a better backup/restore process. Any
ideas?
sql

force process termination on restore

Sorry if this is a dumb question, but we have several production databases
that get automatically backed up, Rar'd, FTP'd internally and then restored.
Problem is, if someone has a process open against the restored database (IE:
a report is being run or something) the restore fails.
There must be a way of making the restore wait until a process is finsihed
or to force a termination of any process (altho probably not a good practice
)
that is running.
Basically, I'm just looking for a better backup/restore process. Any ideas
?Hi,
There are 2 approaches...
1. If you are restoring in non production then you could disconnect all the
users using below command
ALTER database <dbname> set single_user with rollback immediate
go
Restore database
go
ALTER database <dbname> set multi_user
2. Write a loop sort to check the sysprocesses table for this particular
database for any running process . If there
is any running processes
start1:
if (select status from master..sysprocesses where status='runnable' and
db_name(dbid)='pubs')>1
waitfor delay(......) -- set 1 minutedelay
goto start1
else
kill all the users connected
restore the database
I recommend the first method for development and test server databases.
Thanks
Hari
MCDBA
"Jason" <Jason@.discussions.microsoft.com> wrote in message
news:03CD2B22-81B6-4EB1-B782-A86E2C6EF9A1@.microsoft.com...
> Sorry if this is a dumb question, but we have several production databases
> that get automatically backed up, Rar'd, FTP'd internally and then
restored.
> Problem is, if someone has a process open against the restored database
(IE:
> a report is being run or something) the restore fails.
> There must be a way of making the restore wait until a process is finsihed
> or to force a termination of any process (altho probably not a good
practice)
> that is running.
> Basically, I'm just looking for a better backup/restore process. Any
ideas?|||Jason,
I had the same problem and wrote the following code to kill the users
connected to the database when I wanted to do to restore. Would this help
you?
***************************************
use master
go
select p.spid, d.name
into #temp_who
from sysprocesses p
join sysdatabases d on
p.dbid = d.dbid
where d.name = 'PUBS'
DECLARE @.objName int, @.sql NVARCHAR(50)
SET @.objName = 0
WHILE @.objName IS NOT NULL
BEGIN
SELECT @.objName = MIN(spid)
FROM #temp_who
WHERE spid > @.objName
IF @.objName IS NOT NULL
BEGIN
--Insert code to do stuff here.
set @.sql = 'kill ' + cast(@.objName as nvarchar)
exec sp_executesql @.sql
END
END
Good luck.
"Jason" <Jason@.discussions.microsoft.com> wrote in message
news:03CD2B22-81B6-4EB1-B782-A86E2C6EF9A1@.microsoft.com...
> Sorry if this is a dumb question, but we have several production databases
> that get automatically backed up, Rar'd, FTP'd internally and then
restored.
> Problem is, if someone has a process open against the restored database
(IE:
> a report is being run or something) the restore fails.
> There must be a way of making the restore wait until a process is finsihed
> or to force a termination of any process (altho probably not a good
practice)
> that is running.
> Basically, I'm just looking for a better backup/restore process. Any
ideas?

For Restore Operation

Hello Experts,
How can I find using T-SQL, if my database has changed
since tha last backup?
Thanks in advance!Hi
Just before Backup the database insert into table (File_Growth)
SELECT * FROM SYSFILES and compare it with last backup values to look how
big your database is.
"Konstantinos Michas" <anonymous@.discussions.microsoft.com> wrote in message
news:2114101c459d3$0085b270$a001280a@.phx.gbl...
> Hello Experts,
> How can I find using T-SQL, if my database has changed
> since tha last backup?
> Thanks in advance!|||Ok, thank you Uri.
>--Original Message--
>Hi
>Just before Backup the database insert into table
(File_Growth)
>SELECT * FROM SYSFILES and compare it with last backup
values to look how
>big your database is.
>"Konstantinos Michas"
<anonymous@.discussions.microsoft.com> wrote in message
>news:2114101c459d3$0085b270$a001280a@.phx.gbl...
>> Hello Experts,
>> How can I find using T-SQL, if my database has changed
>> since tha last backup?
>> Thanks in advance!
>
>.
>

For Restore Operation

Hello Experts,
How can I find using T-SQL, if my database has changed
since tha last backup?
Thanks in advance!
Hi
Just before Backup the database insert into table (File_Growth)
SELECT * FROM SYSFILES and compare it with last backup values to look how
big your database is.
"Konstantinos Michas" <anonymous@.discussions.microsoft.com> wrote in message
news:2114101c459d3$0085b270$a001280a@.phx.gbl...
> Hello Experts,
> How can I find using T-SQL, if my database has changed
> since tha last backup?
> Thanks in advance!
|||Ok, thank you Uri.

>--Original Message--
>Hi
>Just before Backup the database insert into table
(File_Growth)
>SELECT * FROM SYSFILES and compare it with last backup
values to look how
>big your database is.
>"Konstantinos Michas"
<anonymous@.discussions.microsoft.com> wrote in message
>news:2114101c459d3$0085b270$a001280a@.phx.gbl...
>
>.
>

For Restore Operation

Hello Experts,
How can I find using T-SQL, if my database has changed
since tha last backup?
Thanks in advance!Hi
Just before Backup the database insert into table (File_Growth)
SELECT * FROM SYSFILES and compare it with last backup values to look how
big your database is.
"Konstantinos Michas" <anonymous@.discussions.microsoft.com> wrote in message
news:2114101c459d3$0085b270$a001280a@.phx
.gbl...
> Hello Experts,
> How can I find using T-SQL, if my database has changed
> since tha last backup?
> Thanks in advance!|||Ok, thank you Uri.

>--Original Message--
>Hi
>Just before Backup the database insert into table
(File_Growth)
>SELECT * FROM SYSFILES and compare it with last backup
values to look how
>big your database is.
>"Konstantinos Michas"
<anonymous@.discussions.microsoft.com> wrote in message
> news:2114101c459d3$0085b270$a001280a@.phx
.gbl...
>
>.
>