restore problem

Hi
i started a restore on a little db, it is still running (more than 15 mins),
how can i understand what is it doing?
CarloHow little is the database?
In the future you can use the WITH STATS option to show you the percent
complete.
I am guessing that the SQL Server's disks are busy creating the database
files that will hold the data.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>|||the size of db is around 9 mb, it is a test db, it is still loading, how can
i stop the restore'|||Are you able to see the new data/log files created in OS?
Also check to see if there's blocks.
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore'
>|||9MB. That is darn small. It has not finished yet? 22 minutes have gone by
since your original post and your second post. That is a too long to wait
for a 9MB database.
What did you use to begin the restore? Query Analyzer? Enterprise Manager?
Perhaps you could try closing the app. You could also kill that specific
connection, but that would be harsh.
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> the size of db is around 9 mb, it is a test db, it is still loading, how
can
> i stop the restore'
>|||i stop the service and start it again, the db is alwais loading, i found in
the log this message:
Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
what have i to do'
i'd like to know if i can delete the db from the server, but i cant do it
from the manager because it is loading and i suppose i cant delete it from
the console too. is there a way to delete the "row" in the master db that
let it know that my db exists? i hope you understand what i mean.
Carlo
****************************************
****
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
****************************************
**** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>|||may i use this '
UPDATE sysdatabases
SET status=16
WHERE name='daCancellare'
does it change anything'
****************************************
****
Carlo Marcocci
Istituto Nazionale di Geofisica e Vulcanologia
Via di Vigna Murata 605, 00143 Roma
Tel. +39-6-51860391
Fax. +39-6-51860507
mailto: marcocci@.ingv.it
****************************************
**** L&P
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> 9MB. That is darn small. It has not finished yet? 22 minutes have gone
by
> since your original post and your second post. That is a too long to wait
> for a 9MB database.
> What did you use to begin the restore? Query Analyzer? Enterprise
Manager?
> Perhaps you could try closing the app. You could also kill that specific
> connection, but that would be harsh.
> --
> Keith
>
> "Carlo" <marcocci@.ingv.it> wrote in message
> news:%23KaggZ8fEHA.2984@.tk2msftngp13.phx.gbl...
> can
>|||I would try using DROP DATABASE
Information within Books Online (within the SQL Server program group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:OyzQU09fEHA.3916@.TK2MSFTNGP11.phx.gbl...
> may i use this '
> UPDATE sysdatabases
> SET status=16
> WHERE name='daCancellare'
> does it change anything'
>
> --
>
> ****************************************
****
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ****************************************
**** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how[vbcol=seagreen]
>|||Read up on DROP DATABASE within Books Online (within the SQL Server program
group).
Keith
"Carlo" <marcocci@.ingv.it> wrote in message
news:ex%23jop9fEHA.3932@.TK2MSFTNGP09.phx.gbl...
> i stop the service and start it again, the db is alwais loading, i found
in
> the log this message:
> Bypassing recovery for database 'db_rsnd' because it is marked IN LOAD.
> what have i to do'
> i'd like to know if i can delete the db from the server, but i cant do it
> from the manager because it is loading and i suppose i cant delete it from
> the console too. is there a way to delete the "row" in the master db that
> let it know that my db exists? i hope you understand what i mean.
> Carlo
> --
>
> ****************************************
****
> Carlo Marcocci
> Istituto Nazionale di Geofisica e Vulcanologia
> Via di Vigna Murata 605, 00143 Roma
> Tel. +39-6-51860391
> Fax. +39-6-51860507
> mailto: marcocci@.ingv.it
> ****************************************
**** L&P
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ha scritto nel messaggio
> news:ufwtZL9fEHA.3024@.TK2MSFTNGP10.phx.gbl...
gone[vbcol=seagreen]
> by
wait[vbcol=seagreen]
> Manager?
specific[vbcol=seagreen]
how[vbcol=seagreen]
>|||By now you have fixed your problem. Some added thoughts.
I had a similar issue running SQL Server on a small PC that runs 24x7 (far
too little memory). There were times when a process that normally took 15
minutes ran for more than 3 hours.
1. Sometimes a reboot would speed up the process. Evidently, SQL Server
would grow and grow far beyond the physical memory. The PC spent all its
time paging memory in and out. There is a property to prevent this and set
the maximum memory that SQL Server can use.
2. I also had to set logging to a simple type rather than the full logging.
This is not a production database and we perform daily backups since it is
small. Simple logging is all that is required. With full logging, my tiny
databases (under 50 MB) grew to almost a gigabyte.
3. Wrote a stored procedure that runs in the SQL Server job scheduler every
night that performs a reindex on every table, then gets rid of the log ,
then shrinks the database. Issue has pretty much gone away.
"Carlo" <marcocci@.ingv.it> wrote in message
news:utG3YN8fEHA.704@.TK2MSFTNGP09.phx.gbl...
> Hi
> i started a restore on a little db, it is still running (more than 15
mins),
> how can i understand what is it doing?
> Carlo
> --
>
>