MSSQL 2000 Server vulnerability using SQL Server Management Studio

When using SQL 2005 Management Studio Express, you can backup your database to anywhere on the local MSSQL 2000 server, which includes possibly overwriting critical system files. Users do not have this privilege when using Enterprise Manager to backup MSSQL 2000 databases. It appears that SQL 2005 Management Studio is allowing users to execute the extended stored procedure 'xp_availablemedia', but on MSSQL 2000 server only?

This vulnerability appears to allow any user logged into to the MSSQL 2000 server using SQL 2005 Management Studio Express, permission to overwrite any critical system file, when attempting to backup a database. This would be duplicated by logging into the server as a public user, right clicking on database -> tasks -> Back Up -> then 'Add' a new destination directory.

We would like to find out what is the cause of this, as it does not make sense since Enterprise Manger does not show this vulnerability when backing up. How can security be tightened to disallow this access?

Thank you

Have you checked the privilege for that user who has performed this action?

I believe the NetworkService account used by SQLExpress service and if builtin\admin has privileges on SQL Server 2000 instance then it is by default.

|||

Note that NT Authority\Network Service is an ordinary, low-privileged account that by default does not have Administrative privileges in the operating system. Running SQL Server as NT Authority\Network Service is a security best practice precisely because it is a low privileged account that can't take over the host operating system even if a user manages to elevate privileges to run as the service. If you set SQL Server 2005 to run as Network Service during setup, setup.exe grants (on behalf of the administrator performing setup) read and write privileges to the %ProgramFiles%\Microsoft SQL Server directory and its subdirectories to Network Service.

Management Studio doesn't perform impersonation, so operations run as the logged in user on the server. File system operations are not allowed by the operating system if the user does not have privileges to perform the operation in the directory, so to see a directory for backup the logged in user has to have permission in Windows to see the directory. If you log in as SA, you are running as the service account and anything the service account can do, you can do as well. This isn't an elevation of privileges in the classic sense, it is just exposing the power that sysadmins already have in the server (that is, you are not elevating your privileges to be SA if you log in as SA in the first place). For this reason, it is a good idea to perform most maintenance with a lower privilege account, in this case perhaps one that is a member of just the db_backupoperator role in the database.

To tighten up security, run your server as a low-privileged account, grant that account read and write privileges only in a restricted set of directories (that must include the SQL Server binaries and data files), create special logins for common maintenance tasks that only have sufficient privileges to perform those tasks, and avoid logging in as a member of the Administrators group in Windows or as SA in SQL Server.

Hope this helps,
Steve

MSSQL 2000 Restore - can I roll back Transaction Logs

Not sure if this is possible, but a client wants to now if we can use a
backup we made on 2/24
and then pull transaction out of the database using the daily
transaction log backups to get the database to be an effective copy of
what it looked like on 2/13/06.
We have all the daily transaction logs up to today and the 2/24/06 is
the latest backup we have.
Any help would be greatly appreciated.
RegardsNo. You need a full backup as a starting point BEFORE the desired target
date. Transaction logs are write-ahead, I.E. they log new data, not old.
Logs can thus be rolled forward but not backwards.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>|||Technical correction for the fussy. The logs do contain roll-back
information, but the restore/recovery process is a forward-only one.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:upWIc03UGHA.1572@.tk2msftngp13.phx.gbl...
> No. You need a full backup as a starting point BEFORE the desired target
> date. Transaction logs are write-ahead, I.E. they log new data, not old.
> Logs can thus be rolled forward but not backwards.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> <raekwon2112@.gmail.com> wrote in message
> news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
>> Not sure if this is possible, but a client wants to now if we can use a
>> backup we made on 2/24
>> and then pull transaction out of the database using the daily
>> transaction log backups to get the database to be an effective copy of
>> what it looked like on 2/13/06.
>> We have all the daily transaction logs up to today and the 2/24/06 is
>> the latest backup we have.
>> Any help would be greatly appreciated.
>> Regards
>|||<raekwon2112@.gmail.com> wrote in message
news:1143669384.250415.233980@.z34g2000cwc.googlegroups.com...
> Not sure if this is possible, but a client wants to now if we can use a
> backup we made on 2/24
> and then pull transaction out of the database using the daily
> transaction log backups to get the database to be an effective copy of
> what it looked like on 2/13/06.
> We have all the daily transaction logs up to today and the 2/24/06 is
> the latest backup we have.
> Any help would be greatly appreciated.
> Regards
>
See the topic "How to Restore to a Point In Time" in Books Online.
You need to restore the latest full backup dated BEFORE 2/13/06 with NO
RECOVERY option, followed by the sequence of transaction log backups
covering that date.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

MSSQL 2000- Backup Activity on a Network Machine

Hi,
I am using an Enterprise Manager and i have created a Database Maintainance Plan, can anybody guide me as to how to create backup on a remote machine.

I also mapped that device(say M/c B) onto my server box(M/c A) but i am not able to see that particular location in my backup activity screen.

Can this be done in the first place ?

Regards,
Tahirwe need some clarification.

do you want to backup databases on machine A to machine B or do you want to manage backups of databases that are on machine B from machine A?|||Yes i want to backup databases on machine A to machine B through Enterprize manager.|||While doing the backup on a networked remote machine which has been given full rights the job fails giving this error

BACKUP failed to complete the command BACKUP DATABASE [qa_tm_bdr_fix2] TO DISK = N'\\192.168.156.7\DBBackup\MUMSV075\qa_tm_bdr_fix2 _db_200612262300.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT|||Is your SQL Instance on A running under the system-account? The system account had no rights on B.

But there should be a more useful messge somewhere about why the job fails. Maybe in the errorlog? Have looked at the details in the jobhistory?|||Lexiflex is right. Make sure that the service account running the SQL server on B has enough permissions on the share (on A) where it should write the backup file. So in your case the account under which SQL Server B is running should have the permissions on the \\192.168.156.7\DBBackup share. I assume you allready shared the folder ... The problem Lexiflex is referring to is that the 'local system account' from machine A is not the same as the 'local system account' on machine B ... although it looks like it's the same one, it's definitely not ! You shouldn't run SQL Server under the local system account ... ever.

Been there, done that, worked fine.

Gr,
Yveau|||I am betting this is the problem as well. You will need to change the sql server and sql agent accounts to run under a domain account that has rights to your backup location.|||Thanks a lot for all ur help......it works......

Regards,
Tahir

MSSQL 2000 -> 2005 - Schema stuff?

Hi All,

I imported a database backup with no problems.
I can view the data using the Studio.
However, I noticed that all the tables are now pre-appended with a Schema name.
This also applies to Views.

How do I get 'rid' of this as my application doesn't know about the Schema and claims that it can't find the Tables and Objects I'm referenceing in the web.config.

Thanks,

-Alon

Hi,

schemas were introduced in SQL Server 2005. if the object is no in the default schema of the user, SQL Server will search for it in the dbo namespace. So, there are several options for you to make it work:

-Change default schema of the user which accesses the database to the schema the tables were imported.
-Directly import the tables to the dbo schema / or move them to the appropiate schema.
-Prefix your object in the queries with the schema name
-Schema are quite useful, you should get familiar with them, a lot to read is in the BOL. You should also consider using prefixes in your queries per se.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

While schemas are new in SQL 2005, SQL 2000 had the same basic idea (at least as far as calling the objects). In SQL 2000 objects had owners, and these were prefixed infront of the table name. In most cases dbo was the owner.

Take the application account that is logging into the database. Change it's default schema to the schema that the objects are in (probably the dbo schema) this will fix the problem. By default when you upgrade a database all users are setup with there own schema as there default schema.

You may want to remove any unneeded schemas from the database so that objects don't get created in the wrong schema.

MSQLSERVER service will not start

I have just been through the restoring of all the data on
my using a Third party backup software.
I cannot get my MSSQLService to start. Error comes up
cannot find the path specified.
An error 3 - (the system cannot find the path specified)
occured while performing this operation on the
MSSQLService service.
Can anyone help or point me in the direction of some
article so that I can get the local DB running on my
computer without reinstalling SQLserver.
Thanks| I cannot get my MSSQLService to start. Error comes up
| cannot find the path specified.
|
| An error 3 - (the system cannot find the path specified)
| occured while performing this operation on the
| MSSQLService service.
|
| Can anyone help or point me in the direction of some
| article so that I can get the local DB running on my
| computer without reinstalling SQLserver.
--
Hi Peter,
Try to start the SQL Server service from the command line in minimum
configuration and single user modes and post the output here for us to look
at.
--
Eric Cárdenas
SQL Server support

msmsql.exe is eating my resources during backup.

I had the task manager open on Windows Small Business Server 2000 during the
last half of the backup and I took a peek every so often. In the last 15
minutes the backup started copying the sql databases on the Small Business
Server. The free memory went from 68% to 10% and stays at 10% after the
backup has finished. The CPU usage also soared to 100% during the backup of
these databases (which took maybe 5 to 7 minutes).
When I switched over to the processes tab sure enough sqlservr.exe was the
one eating up all the resources. After the databases were finished the cpu
usage went back to normal as it finished the rest of the backup but the mem
usage is still the same, even well after the backup finished.
The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
server box. I have the SQL backup portion of the backup job configured as
follows:
Backup Method: Full - Back up entire database or filegroup
Consistency Check before Backup: Full check, including indexes
Continue with backup if consistency check fails: checked
Consistency Check after Backup: Full check, including indexes
The backups are succeeding though, and several backups without any reboots
doesn't seem to lower my resources much more. The SBS server currently has 7
%
virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15% to
20%. After the backups. My sqlserv.exe on the SBS server is currently using
1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This is
all after I think two succesful 5-hour full backups with no reboots.
My concern here is that the sql service is eating up more memory than it
needs to because it’s not releasing it when its done the backup. I've trie
d
running a ram defragmenter/washer but the most effective solution is a reboo
t
after each backup. Is there anything I can do to either in Backup Exec, or o
n
the SBS SQL server so that the resources are released when the backup is
complete, or is there a way to stop sql from eating all the resources in the
first place?
Both servers have sql sp3a and the symantec sasser identification tool I ran
claims both servers are secure so I've already elininated that obvious
suggestion for you.
I'm looking for some sort of tweak solution, not necessarily reboot, or
start and stop mssql services before and after the reboot, so If you can
help, I'd greatly appreciate the assistance, because Veritas is doing little
to help me.
And yes, I'm inquiring about this because this is creating performance
issues that sometimes causes the servers to hang or network connectivity to
be lost.Hi
Have a look at this
http://support.microsoft.com/defaul...kb;en-us;321363
It is by design. Once other applications ask for memory, SQL Server gives it
back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:20F4D8B6-EC0B-455B-94B7-38EBFADDC892@.microsoft.com...
>I had the task manager open on Windows Small Business Server 2000 during
>the
> last half of the backup and I took a peek every so often. In the last 15
> minutes the backup started copying the sql databases on the Small Business
> Server. The free memory went from 68% to 10% and stays at 10% after the
> backup has finished. The CPU usage also soared to 100% during the backup
> of
> these databases (which took maybe 5 to 7 minutes).
> When I switched over to the processes tab sure enough sqlservr.exe was the
> one eating up all the resources. After the databases were finished the cpu
> usage went back to normal as it finished the rest of the backup but the
> mem
> usage is still the same, even well after the backup finished.
> The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
> server box. I have the SQL backup portion of the backup job configured as
> follows:
> Backup Method: Full - Back up entire database or filegroup
> Consistency Check before Backup: Full check, including indexes
> Continue with backup if consistency check fails: checked
> Consistency Check after Backup: Full check, including indexes
> The backups are succeeding though, and several backups without any reboots
> doesn't seem to lower my resources much more. The SBS server currently has
> 7%
> virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15%
> to
> 20%. After the backups. My sqlserv.exe on the SBS server is currently
> using
> 1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This
> is
> all after I think two succesful 5-hour full backups with no reboots.
> My concern here is that the sql service is eating up more memory than it
> needs to because it's not releasing it when its done the backup. I've
> tried
> running a ram defragmenter/washer but the most effective solution is a
> reboot
> after each backup. Is there anything I can do to either in Backup Exec, or
> on
> the SBS SQL server so that the resources are released when the backup is
> complete, or is there a way to stop sql from eating all the resources in
> the
> first place?
> Both servers have sql sp3a and the symantec sasser identification tool I
> ran
> claims both servers are secure so I've already elininated that obvious
> suggestion for you.
> I'm looking for some sort of tweak solution, not necessarily reboot, or
> start and stop mssql services before and after the reboot, so If you can
> help, I'd greatly appreciate the assistance, because Veritas is doing
> little
> to help me.
> And yes, I'm inquiring about this because this is creating performance
> issues that sometimes causes the servers to hang or network connectivity
> to
> be lost.

msmsql.exe is eating my resources during backup.

I had the task manager open on Windows Small Business Server 2000 during the
last half of the backup and I took a peek every so often. In the last 15
minutes the backup started copying the sql databases on the Small Business
Server. The free memory went from 68% to 10% and stays at 10% after the
backup has finished. The CPU usage also soared to 100% during the backup of
these databases (which took maybe 5 to 7 minutes).
When I switched over to the processes tab sure enough sqlservr.exe was the
one eating up all the resources. After the databases were finished the cpu
usage went back to normal as it finished the rest of the backup but the mem
usage is still the same, even well after the backup finished.
The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
server box. I have the SQL backup portion of the backup job configured as
follows:
Backup Method: Full - Back up entire database or filegroup
Consistency Check before Backup: Full check, including indexes
Continue with backup if consistency check fails: checked
Consistency Check after Backup: Full check, including indexes
The backups are succeeding though, and several backups without any reboots
doesn't seem to lower my resources much more. The SBS server currently has 7%
virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15% to
20%. After the backups. My sqlserv.exe on the SBS server is currently using
1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This is
all after I think two succesful 5-hour full backups with no reboots.
My concern here is that the sql service is eating up more memory than it
needs to because it’s not releasing it when its done the backup. I've tried
running a ram defragmenter/washer but the most effective solution is a reboot
after each backup. Is there anything I can do to either in Backup Exec, or on
the SBS SQL server so that the resources are released when the backup is
complete, or is there a way to stop sql from eating all the resources in the
first place?
Both servers have sql sp3a and the symantec sasser identification tool I ran
claims both servers are secure so I've already elininated that obvious
suggestion for you.
I'm looking for some sort of tweak solution, not necessarily reboot, or
start and stop mssql services before and after the reboot, so If you can
help, I'd greatly appreciate the assistance, because Veritas is doing little
to help me.
And yes, I'm inquiring about this because this is creating performance
issues that sometimes causes the servers to hang or network connectivity to
be lost.
Hi
Have a look at this
http://support.microsoft.com/default...b;en-us;321363
It is by design. Once other applications ask for memory, SQL Server gives it
back.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:20F4D8B6-EC0B-455B-94B7-38EBFADDC892@.microsoft.com...
>I had the task manager open on Windows Small Business Server 2000 during
>the
> last half of the backup and I took a peek every so often. In the last 15
> minutes the backup started copying the sql databases on the Small Business
> Server. The free memory went from 68% to 10% and stays at 10% after the
> backup has finished. The CPU usage also soared to 100% during the backup
> of
> these databases (which took maybe 5 to 7 minutes).
> When I switched over to the processes tab sure enough sqlservr.exe was the
> one eating up all the resources. After the databases were finished the cpu
> usage went back to normal as it finished the rest of the backup but the
> mem
> usage is still the same, even well after the backup finished.
> The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
> server box. I have the SQL backup portion of the backup job configured as
> follows:
> Backup Method: Full - Back up entire database or filegroup
> Consistency Check before Backup: Full check, including indexes
> Continue with backup if consistency check fails: checked
> Consistency Check after Backup: Full check, including indexes
> The backups are succeeding though, and several backups without any reboots
> doesn't seem to lower my resources much more. The SBS server currently has
> 7%
> virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15%
> to
> 20%. After the backups. My sqlserv.exe on the SBS server is currently
> using
> 1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This
> is
> all after I think two succesful 5-hour full backups with no reboots.
> My concern here is that the sql service is eating up more memory than it
> needs to because it's not releasing it when its done the backup. I've
> tried
> running a ram defragmenter/washer but the most effective solution is a
> reboot
> after each backup. Is there anything I can do to either in Backup Exec, or
> on
> the SBS SQL server so that the resources are released when the backup is
> complete, or is there a way to stop sql from eating all the resources in
> the
> first place?
> Both servers have sql sp3a and the symantec sasser identification tool I
> ran
> claims both servers are secure so I've already elininated that obvious
> suggestion for you.
> I'm looking for some sort of tweak solution, not necessarily reboot, or
> start and stop mssql services before and after the reboot, so If you can
> help, I'd greatly appreciate the assistance, because Veritas is doing
> little
> to help me.
> And yes, I'm inquiring about this because this is creating performance
> issues that sometimes causes the servers to hang or network connectivity
> to
> be lost.

msmsql.exe is eating my resources during backup.

I had the task manager open on Windows Small Business Server 2000 during the
last half of the backup and I took a peek every so often. In the last 15
minutes the backup started copying the sql databases on the Small Business
Server. The free memory went from 68% to 10% and stays at 10% after the
backup has finished. The CPU usage also soared to 100% during the backup of
these databases (which took maybe 5 to 7 minutes).
When I switched over to the processes tab sure enough sqlservr.exe was the
one eating up all the resources. After the databases were finished the cpu
usage went back to normal as it finished the rest of the backup but the mem
usage is still the same, even well after the backup finished.
The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
server box. I have the SQL backup portion of the backup job configured as
follows:
Backup Method: Full - Back up entire database or filegroup
Consistency Check before Backup: Full check, including indexes
Continue with backup if consistency check fails: checked
Consistency Check after Backup: Full check, including indexes
The backups are succeeding though, and several backups without any reboots
doesn't seem to lower my resources much more. The SBS server currently has 7%
virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15% to
20%. After the backups. My sqlserv.exe on the SBS server is currently using
1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This is
all after I think two succesful 5-hour full backups with no reboots.
My concern here is that the sql service is eating up more memory than it
needs to because itâ's not releasing it when its done the backup. I've tried
running a ram defragmenter/washer but the most effective solution is a reboot
after each backup. Is there anything I can do to either in Backup Exec, or on
the SBS SQL server so that the resources are released when the backup is
complete, or is there a way to stop sql from eating all the resources in the
first place?
Both servers have sql sp3a and the symantec sasser identification tool I ran
claims both servers are secure so I've already elininated that obvious
suggestion for you.
I'm looking for some sort of tweak solution, not necessarily reboot, or
start and stop mssql services before and after the reboot, so If you can
help, I'd greatly appreciate the assistance, because Veritas is doing little
to help me.
And yes, I'm inquiring about this because this is creating performance
issues that sometimes causes the servers to hang or network connectivity to
be lost.Hi
Have a look at this
http://support.microsoft.com/default.aspx?scid=kb;en-us;321363
It is by design. Once other applications ask for memory, SQL Server gives it
back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:20F4D8B6-EC0B-455B-94B7-38EBFADDC892@.microsoft.com...
>I had the task manager open on Windows Small Business Server 2000 during
>the
> last half of the backup and I took a peek every so often. In the last 15
> minutes the backup started copying the sql databases on the Small Business
> Server. The free memory went from 68% to 10% and stays at 10% after the
> backup has finished. The CPU usage also soared to 100% during the backup
> of
> these databases (which took maybe 5 to 7 minutes).
> When I switched over to the processes tab sure enough sqlservr.exe was the
> one eating up all the resources. After the databases were finished the cpu
> usage went back to normal as it finished the rest of the backup but the
> mem
> usage is still the same, even well after the backup finished.
> The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
> server box. I have the SQL backup portion of the backup job configured as
> follows:
> Backup Method: Full - Back up entire database or filegroup
> Consistency Check before Backup: Full check, including indexes
> Continue with backup if consistency check fails: checked
> Consistency Check after Backup: Full check, including indexes
> The backups are succeeding though, and several backups without any reboots
> doesn't seem to lower my resources much more. The SBS server currently has
> 7%
> virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15%
> to
> 20%. After the backups. My sqlserv.exe on the SBS server is currently
> using
> 1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This
> is
> all after I think two succesful 5-hour full backups with no reboots.
> My concern here is that the sql service is eating up more memory than it
> needs to because it's not releasing it when its done the backup. I've
> tried
> running a ram defragmenter/washer but the most effective solution is a
> reboot
> after each backup. Is there anything I can do to either in Backup Exec, or
> on
> the SBS SQL server so that the resources are released when the backup is
> complete, or is there a way to stop sql from eating all the resources in
> the
> first place?
> Both servers have sql sp3a and the symantec sasser identification tool I
> ran
> claims both servers are secure so I've already elininated that obvious
> suggestion for you.
> I'm looking for some sort of tweak solution, not necessarily reboot, or
> start and stop mssql services before and after the reboot, so If you can
> help, I'd greatly appreciate the assistance, because Veritas is doing
> little
> to help me.
> And yes, I'm inquiring about this because this is creating performance
> issues that sometimes causes the servers to hang or network connectivity
> to
> be lost.sql

Msg (Loading) after db name

I wanted to restore a database to a new location on a different server. I
did a backup to a file and then did a restore of that file onto the new
server. I got a message that the restore was successful, but when I opened
Enterprise Manager the database had "(Loading)" after the database name and
was grayed out. When I tried to select properties it gave me "Error 927:
Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
Can anyone help? Thanks.
DavidSounds like you might have left your database in a state where you can
restore a differential or additional transaction logs. Could you possibly
have restored using the "NORECOVERY" options, or set the "Leave Database
nonoperation...." radio button when doing your restore.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23qBVFFmQEHA.1960@.TK2MSFTNGP10.phx.gbl...
> I wanted to restore a database to a new location on a different server. I
> did a backup to a file and then did a restore of that file onto the new
> server. I got a message that the restore was successful, but when I
opened
> Enterprise Manager the database had "(Loading)" after the database name
and
> was grayed out. When I tried to select properties it gave me "Error 927:
> Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
> Can anyone help? Thanks.
> David
>|||Hi,
Execute the below command from query analyzer:-
restore database <dbname> with recovery
Thanks
Hari
MCDBA
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:#qBVFFmQEHA.1960@.TK2MSFTNGP10.phx.gbl...
> I wanted to restore a database to a new location on a different server. I
> did a backup to a file and then did a restore of that file onto the new
> server. I got a message that the restore was successful, but when I
opened
> Enterprise Manager the database had "(Loading)" after the database name
and
> was grayed out. When I tried to select properties it gave me "Error 927:
> Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
> Can anyone help? Thanks.
> David
>

Msg (Loading) after db name

I wanted to restore a database to a new location on a different server. I
did a backup to a file and then did a restore of that file onto the new
server. I got a message that the restore was successful, but when I opened
Enterprise Manager the database had "(Loading)" after the database name and
was grayed out. When I tried to select properties it gave me "Error 927:
Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
Can anyone help? Thanks.
David
Sounds like you might have left your database in a state where you can
restore a differential or additional transaction logs. Could you possibly
have restored using the "NORECOVERY" options, or set the "Leave Database
nonoperation...." radio button when doing your restore.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23qBVFFmQEHA.1960@.TK2MSFTNGP10.phx.gbl...
> I wanted to restore a database to a new location on a different server. I
> did a backup to a file and then did a restore of that file onto the new
> server. I got a message that the restore was successful, but when I
opened
> Enterprise Manager the database had "(Loading)" after the database name
and
> was grayed out. When I tried to select properties it gave me "Error 927:
> Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
> Can anyone help? Thanks.
> David
>
|||Hi,
Execute the below command from query analyzer:-
restore database <dbname> with recovery
Thanks
Hari
MCDBA
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:#qBVFFmQEHA.1960@.TK2MSFTNGP10.phx.gbl...
> I wanted to restore a database to a new location on a different server. I
> did a backup to a file and then did a restore of that file onto the new
> server. I got a message that the restore was successful, but when I
opened
> Enterprise Manager the database had "(Loading)" after the database name
and
> was grayed out. When I tried to select properties it gave me "Error 927:
> Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
> Can anyone help? Thanks.
> David
>
|||Yup. That was it...had the "Leave database nonoperation..." radio boxed
checked. Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Msg (Loading) after db name

I wanted to restore a database to a new location on a different server. I
did a backup to a file and then did a restore of that file onto the new
server. I got a message that the restore was successful, but when I opened
Enterprise Manager the database had "(Loading)" after the database name and
was grayed out. When I tried to select properties it gave me "Error 927:
Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
Can anyone help? Thanks.
DavidSounds like you might have left your database in a state where you can
restore a differential or additional transaction logs. Could you possibly
have restored using the "NORECOVERY" options, or set the "Leave Database
nonoperation...." radio button when doing your restore.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23qBVFFmQEHA.1960@.TK2MSFTNGP10.phx.gbl...
> I wanted to restore a database to a new location on a different server. I
> did a backup to a file and then did a restore of that file onto the new
> server. I got a message that the restore was successful, but when I
opened
> Enterprise Manager the database had "(Loading)" after the database name
and
> was grayed out. When I tried to select properties it gave me "Error 927:
> Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
> Can anyone help? Thanks.
> David
>|||Hi,
Execute the below command from query analyzer:-
restore database <dbname> with recovery
Thanks
Hari
MCDBA
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:#qBVFFmQEHA.1960@.TK2MSFTNGP10.phx.gbl...
> I wanted to restore a database to a new location on a different server. I
> did a backup to a file and then did a restore of that file onto the new
> server. I got a message that the restore was successful, but when I
opened
> Enterprise Manager the database had "(Loading)" after the database name
and
> was grayed out. When I tried to select properties it gave me "Error 927:
> Database 'wcccu_db' cannot be opened. It is in the middle of a restore."
> Can anyone help? Thanks.
> David
>|||Yup. That was it...had the "Leave database nonoperation..." radio boxed
checked. Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!