database in load

Hello,

I am an administrator of a SQL server 2000 machine residing on a windows 2000 box. I tried restoring a database on this server from a backup file that i copied from another server. Halfway through the restore, the user comes up to me saying they did not want the database restored again. I stopped the restore process and since then it has not gone back to its previous state. Secondly it is grayed out with a (loading) text next to the database icon.

how did this happen and how do you suggest i solve this.

regards

This is because the restore process is not complete. Try dropping the database and restore the backup prior to this state as it will recreate the database.

database full backup

How to take the full backup the database from one server onto a tape and how to restore it onto a different server.
ThanksHowdy

Read books on line...all info is there.

Post back if problems.

Cheers

SG

database File size problem

Hi,
I have a database which is 10 GB big but on disk it shows 20GB. I did
backup and shrinkdb but it doesn't shrink. I could shrink log but not
the actual db. Any hints why I cannot do this? Also weird thing is that
when I run DBCC shrinkdb I don't get any error message.
Here is the exact command I run:
DBCC SHRINKDATABASE (MYDB, 5, TRUNCATEONLY)
GO
Tnank you,
hjHi
DBCC SHRINKDATABASE will not shrink a file smaller than it's initial size,
which may be the issue in your case. Use DBCC SHRINKFILE to shrink the
individual file, but if you are will be expanding to 20GB at some time, then
you may not want to shrink it at all. Your log file should be a reasonably
constant size, if you backup the log regularly (in FULL recovery mode).
John
"Hitesh" wrote:
> Hi,
> I have a database which is 10 GB big but on disk it shows 20GB. I did
> backup and shrinkdb but it doesn't shrink. I could shrink log but not
> the actual db. Any hints why I cannot do this? Also weird thing is that
> when I run DBCC shrinkdb I don't get any error message.
> Here is the exact command I run:
> DBCC SHRINKDATABASE (MYDB, 5, TRUNCATEONLY)
> GO
> Tnank you,
> hj
>|||DBCC SHRINKDATABASE will not shrink a file smaller than its shrinkpoint.
The shrinkpoint starts out at the initial size of the file, but once you use
DBCC SHRINKFILE, that can set a new shrinkpoint, and subsequent DBCC
SHRINKDATABASE operations can shrink to that new smaller size.
Also, Hitesh, make sure you're aware what the parameters to DBCC
SHRINKDATABASE mean. The 5 parameter means to shrink so that there is 5%
free space in the file. If there is already more than 5% free space, no
shrinking will take place.
When you run DBCC SHRINKFILE, then the number is the size in MB to which you
want to shrink the file.
Why do you think you might get an error message?
--
HTH
Kalen Delaney, SQL Server MVP
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:79C1DC8D-4BB0-4D11-BBED-A98A9BA35A2C@.microsoft.com...
> Hi
> DBCC SHRINKDATABASE will not shrink a file smaller than it's initial size,
> which may be the issue in your case. Use DBCC SHRINKFILE to shrink the
> individual file, but if you are will be expanding to 20GB at some time,
> then
> you may not want to shrink it at all. Your log file should be a reasonably
> constant size, if you backup the log regularly (in FULL recovery mode).
> John
> "Hitesh" wrote:
>> Hi,
>> I have a database which is 10 GB big but on disk it shows 20GB. I did
>> backup and shrinkdb but it doesn't shrink. I could shrink log but not
>> the actual db. Any hints why I cannot do this? Also weird thing is that
>> when I run DBCC shrinkdb I don't get any error message.
>> Here is the exact command I run:
>> DBCC SHRINKDATABASE (MYDB, 5, TRUNCATEONLY)
>> GO
>> Tnank you,
>> hj
>>|||Thank you John & Kalean.
When I used DBCC SHRINKFILE on indivisual database files, it worked.
Kalean is right I might be using wrong free space percentage.
Thank you both for your help.
hj
Kalen Delaney wrote:
> DBCC SHRINKDATABASE will not shrink a file smaller than its shrinkpoint.
> The shrinkpoint starts out at the initial size of the file, but once you use
> DBCC SHRINKFILE, that can set a new shrinkpoint, and subsequent DBCC
> SHRINKDATABASE operations can shrink to that new smaller size.
> Also, Hitesh, make sure you're aware what the parameters to DBCC
> SHRINKDATABASE mean. The 5 parameter means to shrink so that there is 5%
> free space in the file. If there is already more than 5% free space, no
> shrinking will take place.
> When you run DBCC SHRINKFILE, then the number is the size in MB to which you
> want to shrink the file.
> Why do you think you might get an error message?
> --
> HTH
> Kalen Delaney, SQL Server MVP
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:79C1DC8D-4BB0-4D11-BBED-A98A9BA35A2C@.microsoft.com...
> > Hi
> >
> > DBCC SHRINKDATABASE will not shrink a file smaller than it's initial size,
> > which may be the issue in your case. Use DBCC SHRINKFILE to shrink the
> > individual file, but if you are will be expanding to 20GB at some time,
> > then
> > you may not want to shrink it at all. Your log file should be a reasonably
> > constant size, if you backup the log regularly (in FULL recovery mode).
> >
> > John
> >
> > "Hitesh" wrote:
> >
> >> Hi,
> >>
> >> I have a database which is 10 GB big but on disk it shows 20GB. I did
> >> backup and shrinkdb but it doesn't shrink. I could shrink log but not
> >> the actual db. Any hints why I cannot do this? Also weird thing is that
> >> when I run DBCC shrinkdb I don't get any error message.
> >> Here is the exact command I run:
> >>
> >> DBCC SHRINKDATABASE (MYDB, 5, TRUNCATEONLY)
> >>
> >> GO
> >>
> >> Tnank you,
> >> hj
> >>
> >>

database failure to restore from NT backup

Hello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J

>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>Julie
Thanks for the link, but the customer says that the Bull RAID controller is
a Milex, not Adaptec,|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J

>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>

database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a
work around, but they want to know what the root cause was.
Problem description
It seems that they had disk problems, then wanted to restore the database fr
om a backup. They were not doing backups to disk, just to shutting down the
services & doing a cold NT backup to tape.
Error Details
The server lost a disc (one of five from RAID5 array). After it was fixed,
the data was restored from a backup tape and the following appeared in the S
QL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_D
ata.NDF' is not a valid database file header. The PageAudit property is inco
rrect.
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file n
ame 'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
System Details
SQL Server 7
NT 4
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
4 * PIII 700 Mhz
2 GB RAM
40/80GB SCSI DLT Internal Tape Drive
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
Regards
DavidDavid,
This scenario is a typical case why you should do backup using SQL Server BA
CKUP command instead of just
picking up the physical files. In general, it should work assuming that you
indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a ca
se with MS Support for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work a
round, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a b
ackup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.[
vbcol=seagreen]
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the da
ta was restored from a[/vbcol]
backup tape and the following appeared in the SQL Server activity log. The database was in s
uspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF
.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.ND
F.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.ND
F' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name[/v
bcol]
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.[vbcol=seagreen]
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF
.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David

database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to know what the root cause was
Problem descriptio
It seems that they had disk problems, then wanted to restore the database from a backup. They were not doing backups to disk, just to shutting down the services & doing a cold NT backup to tape
Error Detail
The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database file header. The PageAudit property is incorrect
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name 'e:\SQL\data\dataname2_Data.NDF' may be incorrect
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF
System Detail
SQL Server
NT
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
4 * PIII 700 Mh
2 GB RA
40/80GB SCSI DLT Internal Tape Driv
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1"
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+
Regard
DavidHello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J
>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>|||David,
This scenario is a typical case why you should do backup using SQL Server BACKUP command instead of just
picking up the physical files. In general, it should work assuming that you indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a case with MS Support for this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a backup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a
backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David|||Juli
Thanks for the link, but the customer says that the Bull RAID controller is a Milex, not Adaptec,|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J
>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>sql

database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to know what the root cause was.
Problem description
It seems that they had disk problems, then wanted to restore the database from a backup. They were not doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.
Error Details
The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database file header. The PageAudit property is incorrect.
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name 'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
System Details
SQL Server 7
NT 4
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
4 * PIII 700 Mhz
2 GB RAM
40/80GB SCSI DLT Internal Tape Drive
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
Regards
David
David,
This scenario is a typical case why you should do backup using SQL Server BACKUP command instead of just
picking up the physical files. In general, it should work assuming that you indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a case with MS Support for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a backup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a
backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David

database failure to restore from NT backup

Hello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J

>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>
Julie
Thanks for the link, but the customer says that the Bull RAID controller is a Milex, not Adaptec,
|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J

>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>

Database Explorer or Backup Explorer Tool?

I just watched an on demand webcast for SharePoint which uses SQL as the bac
k
end database. The Microsoft presenter talked about using an explorer tool t
o
open sql backup files and extracting data. Does anybody know what tool he i
s
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
Will RobinsonI've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the ba
ck
> end database. The Microsoft presenter talked about using an explorer tool
to
> open sql backup files and extracting data. Does anybody know what tool he
is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got
to
> have it.
>
> --
> Will Robinsonsql

Database Explorer or Backup Explorer Tool?

I just watched an on demand webcast for SharePoint which uses SQL as the back
end database. The Microsoft presenter talked about using an explorer tool to
open sql backup files and extracting data. Does anybody know what tool he is
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
--
Will RobinsonI've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the back
> end database. The Microsoft presenter talked about using an explorer tool to
> open sql backup files and extracting data. Does anybody know what tool he is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got to
> have it.
>
> --
> Will Robinson

Database Explorer or Backup Explorer Tool?

I just watched an on demand webcast for SharePoint which uses SQL as the back
end database. The Microsoft presenter talked about using an explorer tool to
open sql backup files and extracting data. Does anybody know what tool he is
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
Will Robinson
I've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the back
> end database. The Microsoft presenter talked about using an explorer tool to
> open sql backup files and extracting data. Does anybody know what tool he is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got to
> have it.
>
> --
> Will Robinson

Database Error during backup

We are currently using SQL 2000 SP4. When I try to backup any of our
Databases I receive the error message below, any suggestions that would fix
this problem for me. I would also like to make note that I viewed the Error
Log and could not identify any possible causes to this error, I have also
checked the Event Log and nothing logged there either.
--
Microsoft SQL-DMO (ODBC SQLState: 01000)
--
Error 926: Database 'msdb' cannot be opened. It has been marked SUSPECT by
recovery. See the SQL Server errorlog for more information.
--
OK
--
Regards,
JohnCheck BOL for DBCC CHECKDB
"John" <John@.discussions.microsoft.com> wrote in message
news:10ECD5A7-3C9A-427C-BD9B-F0DAA3F1FBD9@.microsoft.com...
> We are currently using SQL 2000 SP4. When I try to backup any of our
> Databases I receive the error message below, any suggestions that would
> fix
> this problem for me. I would also like to make note that I viewed the
> Error
> Log and could not identify any possible causes to this error, I have also
> checked the Event Log and nothing logged there either.
> --
> Microsoft SQL-DMO (ODBC SQLState: 01000)
> --
> Error 926: Database 'msdb' cannot be opened. It has been marked SUSPECT by
> recovery. See the SQL Server errorlog for more information.
> --
> OK
> --
> Regards,
> John
>|||... and be prepared for the worst: to restore your msdb database from a clean backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <spam@.nospam.org> wrote in message news:u46ACdaEIHA.2004@.TK2MSFTNGP06.phx.gbl...
> Check BOL for DBCC CHECKDB
> "John" <John@.discussions.microsoft.com> wrote in message
> news:10ECD5A7-3C9A-427C-BD9B-F0DAA3F1FBD9@.microsoft.com...
>> We are currently using SQL 2000 SP4. When I try to backup any of our
>> Databases I receive the error message below, any suggestions that would
>> fix
>> this problem for me. I would also like to make note that I viewed the
>> Error
>> Log and could not identify any possible causes to this error, I have also
>> checked the Event Log and nothing logged there either.
>> --
>> Microsoft SQL-DMO (ODBC SQLState: 01000)
>> --
>> Error 926: Database 'msdb' cannot be opened. It has been marked SUSPECT by
>> recovery. See the SQL Server errorlog for more information.
>> --
>> OK
>> --
>> Regards,
>> John
>|||IIRC on sql2000 you can directly modify system tables. perhaps you can try
updating sysdatabases to clear the suspect flag (there may even be advice on
this in BOL) after you exhaust all other attempts and just before you
restore/rebuild your msdb.
You can also consider calling Microsoft for support.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"John" <John@.discussions.microsoft.com> wrote in message
news:10ECD5A7-3C9A-427C-BD9B-F0DAA3F1FBD9@.microsoft.com...
> We are currently using SQL 2000 SP4. When I try to backup any of our
> Databases I receive the error message below, any suggestions that would
> fix
> this problem for me. I would also like to make note that I viewed the
> Error
> Log and could not identify any possible causes to this error, I have also
> checked the Event Log and nothing logged there either.
> --
> Microsoft SQL-DMO (ODBC SQLState: 01000)
> --
> Error 926: Database 'msdb' cannot be opened. It has been marked SUSPECT by
> recovery. See the SQL Server errorlog for more information.
> --
> OK
> --
> Regards,
> John
>

Database dump size

Hi there. Running a Sql 2000 installation with latest service pack on
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.
What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.c om...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.
|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.c om...
>
|||Used the maintenance plan wizard to set it up. It's a dump to disk.
There aren't many options to select really. It does seem like it's
appending the dump. Is there an option in Enterprise manager to disable
append or will I have to do it the hard way? Thanks.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||Maint plan doesn't append. It creates a new backup device each time it performs a backup. Verify using RESTORE
HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christopher Scott" <christopher@.uncommonlaw.com> wrote in message
news:%23cTXggVTEHA.2416@.TK2MSFTNGP12.phx.gbl...
>
> Used the maintenance plan wizard to set it up. It's a dump to disk.
> There aren't many options to select really. It does seem like it's
> appending the dump. Is there an option in Enterprise manager to disable
> append or will I have to do it the hard way? Thanks.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!

Database dump size

Hi there. Running a Sql 2000 installation with latest service pack on
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
>|||Used the maintenance plan wizard to set it up. It's a dump to disk.
There aren't many options to select really. It does seem like it's
appending the dump. Is there an option in Enterprise manager to disable
append or will I have to do it the hard way? Thanks.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Maint plan doesn't append. It creates a new backup device each time it perfo
rms a backup. Verify using RESTORE
HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christopher Scott" <christopher@.uncommonlaw.com> wrote in message
news:%23cTXggVTEHA.2416@.TK2MSFTNGP12.phx.gbl...
>
> Used the maintenance plan wizard to set it up. It's a dump to disk.
> There aren't many options to select really. It does seem like it's
> appending the dump. Is there an option in Enterprise manager to disable
> append or will I have to do it the hard way? Thanks.
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!

Database dump size

Hi there. Running a Sql 2000 installation with latest service pack on
Windows 2000 server. My database dump to disk backup keeps increasing
by about 1 meg per day. The database itself is increasing by a small
percentage of that. In fact the dump is now about the same size as the
database. What's going on? Thanks.Hello
Can you please give us details of the type of backup your
doing as well as your recovery model.
J
>--Original Message--
>Hi there. Running a Sql 2000 installation with latest
service pack on
>Windows 2000 server. My database dump to disk backup
keeps increasing
>by about 1 meg per day. The database itself is increasing
by a small
>percentage of that. In fact the dump is now about the
same size as the
>database. What's going on? Thanks.
>.
>|||What kind of backup are you doing? If you don't use the INIT option the
current backup will append to the existing ones in the dump device.
--
Andrew J. Kelly
SQL Server MVP
"cscott" <christopher@.uncommonlaw.com> wrote in message
news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> Hi there. Running a Sql 2000 installation with latest service pack on
> Windows 2000 server. My database dump to disk backup keeps increasing
> by about 1 meg per day. The database itself is increasing by a small
> percentage of that. In fact the dump is now about the same size as the
> database. What's going on? Thanks.|||Hi ,
To add on to Andrew post, Execute the below comand from query analyzer to
check if BACKUP is executed in append mode.
restore headeronly from disk='Directory\dbname.BAK'
If this list more than 1 entry (Check the postion column in output), means
you have taken the backup in Append mode. To remove he append mode add an
OPTION
INIT along with backup database command
BACKUP DATABASE dbname to disk='c:\dbname.bak' with INIT
Thanks
Hari
MCDBA
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uYtrikJTEHA.2324@.TK2MSFTNGP10.phx.gbl...
> What kind of backup are you doing? If you don't use the INIT option the
> current backup will append to the existing ones in the dump device.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "cscott" <christopher@.uncommonlaw.com> wrote in message
> news:a94f8da8.0406070533.6a59d6fb@.posting.google.com...
> > Hi there. Running a Sql 2000 installation with latest service pack on
> > Windows 2000 server. My database dump to disk backup keeps increasing
> > by about 1 meg per day. The database itself is increasing by a small
> > percentage of that. In fact the dump is now about the same size as the
> > database. What's going on? Thanks.
>

Database Diff?

I was just looking at my database backups and i noticed there was about a
100MB difference in the backup files. We run optimization plans but those
are done on the weekend and this happened in the middle of the week.
Some people are a little curious as to why the database backup would shrink
so much. I was thinking of trying to do a DB diff between the two but wasnt
sure how to do this. Looked around a little and saw a few tools but i was
looking for a free solution.
Anyone know why this might have shrunk or a tool that i could use to do a
diff?
Thanks
Justin
You could restore a backup before the change, and a backup after the change,
and then use a trial copy of red-gate SQL Compare (or trial versions of
other tools), I guess. Tools like this pay for themselves in the long run,
unless this is the only time you will ever use it (which you can't possibly
know right now).
Aaron Bertrand
SQL Server MVP
"Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>I was just looking at my database backups and i noticed there was about a
>100MB difference in the backup files. We run optimization plans but those
>are done on the weekend and this happened in the middle of the week.
> Some people are a little curious as to why the database backup would
> shrink so much. I was thinking of trying to do a DB diff between the two
> but wasnt sure how to do this. Looked around a little and saw a few tools
> but i was looking for a free solution.
> Anyone know why this might have shrunk or a tool that i could use to do a
> diff?
>
> Thanks
> Justin
>
|||You can start by checking all the table sizes ;)
Maybe somebody/changed to diffirential backup ?
Cheers,
Harry
|||Yeah you are right, i dont know if i'll need it again but a trial would be a
great start. I'll look in to that product.
Thanks
Justin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23YHa4cSzHHA.4476@.TK2MSFTNGP06.phx.gbl...
> You could restore a backup before the change, and a backup after the
> change, and then use a trial copy of red-gate SQL Compare (or trial
> versions of other tools), I guess. Tools like this pay for themselves in
> the long run, unless this is the only time you will ever use it (which you
> can't possibly know right now).
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
> news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>
|||Yeah i guess i didnt really think about that. its really not too hard to run
a script to give some basic statistics about tables. More just a resource
problem but i have some spare servers i can run this on.
Thanks!
Justin
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:CABE43A2-BD14-4E93-89FA-D5D5C8E12393@.microsoft.com...
> You can start by checking all the table sizes ;)
> Maybe somebody/changed to diffirential backup ?
> Cheers,
> Harry
>

Database Diff?

I was just looking at my database backups and i noticed there was about a
100MB difference in the backup files. We run optimization plans but those
are done on the weekend and this happened in the middle of the week.
Some people are a little curious as to why the database backup would shrink
so much. I was thinking of trying to do a DB diff between the two but wasnt
sure how to do this. Looked around a little and saw a few tools but i was
looking for a free solution.
Anyone know why this might have shrunk or a tool that i could use to do a
diff?
Thanks
JustinYou could restore a backup before the change, and a backup after the change,
and then use a trial copy of red-gate SQL Compare (or trial versions of
other tools), I guess. Tools like this pay for themselves in the long run,
unless this is the only time you will ever use it (which you can't possibly
know right now).
Aaron Bertrand
SQL Server MVP
"Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>I was just looking at my database backups and i noticed there was about a
>100MB difference in the backup files. We run optimization plans but those
>are done on the weekend and this happened in the middle of the week.
> Some people are a little curious as to why the database backup would
> shrink so much. I was thinking of trying to do a DB diff between the two
> but wasnt sure how to do this. Looked around a little and saw a few tools
> but i was looking for a free solution.
> Anyone know why this might have shrunk or a tool that i could use to do a
> diff?
>
> Thanks
> Justin
>|||You can start by checking all the table sizes ;)
Maybe somebody/changed to diffirential backup ?
Cheers,
Harry|||Yeah you are right, i dont know if i'll need it again but a trial would be a
great start. I'll look in to that product.
Thanks
Justin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:%23YHa4cSzHHA.4476@.TK2MSFTNGP06.phx.gbl...
> You could restore a backup before the change, and a backup after the
> change, and then use a trial copy of red-gate SQL Compare (or trial
> versions of other tools), I guess. Tools like this pay for themselves in
> the long run, unless this is the only time you will ever use it (which you
> can't possibly know right now).
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
> news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>|||Yeah i guess i didnt really think about that. its really not too hard to run
a script to give some basic statistics about tables. More just a resource
problem but i have some spare servers i can run this on.
Thanks!
Justin
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:CABE43A2-BD14-4E93-89FA-D5D5C8E12393@.microsoft.com...
> You can start by checking all the table sizes ;)
> Maybe somebody/changed to diffirential backup ?
> Cheers,
> Harry
>

Database Diff?

I was just looking at my database backups and i noticed there was about a
100MB difference in the backup files. We run optimization plans but those
are done on the weekend and this happened in the middle of the week.
Some people are a little curious as to why the database backup would shrink
so much. I was thinking of trying to do a DB diff between the two but wasnt
sure how to do this. Looked around a little and saw a few tools but i was
looking for a free solution.
Anyone know why this might have shrunk or a tool that i could use to do a
diff?
Thanks
JustinYou could restore a backup before the change, and a backup after the change,
and then use a trial copy of red-gate SQL Compare (or trial versions of
other tools), I guess. Tools like this pay for themselves in the long run,
unless this is the only time you will ever use it (which you can't possibly
know right now).
--
Aaron Bertrand
SQL Server MVP
"Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>I was just looking at my database backups and i noticed there was about a
>100MB difference in the backup files. We run optimization plans but those
>are done on the weekend and this happened in the middle of the week.
> Some people are a little curious as to why the database backup would
> shrink so much. I was thinking of trying to do a DB diff between the two
> but wasnt sure how to do this. Looked around a little and saw a few tools
> but i was looking for a free solution.
> Anyone know why this might have shrunk or a tool that i could use to do a
> diff?
>
> Thanks
> Justin
>|||You can start by checking all the table sizes ;)
Maybe somebody/changed to diffirential backup ?
Cheers,
Harry|||Yeah you are right, i dont know if i'll need it again but a trial would be a
great start. I'll look in to that product.
Thanks
Justin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23YHa4cSzHHA.4476@.TK2MSFTNGP06.phx.gbl...
> You could restore a backup before the change, and a backup after the
> change, and then use a trial copy of red-gate SQL Compare (or trial
> versions of other tools), I guess. Tools like this pay for themselves in
> the long run, unless this is the only time you will ever use it (which you
> can't possibly know right now).
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Justin Rich" <jrich523@.yahoo.spam.com> wrote in message
> news:u0yWbRSzHHA.4824@.TK2MSFTNGP02.phx.gbl...
>>I was just looking at my database backups and i noticed there was about a
>>100MB difference in the backup files. We run optimization plans but those
>>are done on the weekend and this happened in the middle of the week.
>> Some people are a little curious as to why the database backup would
>> shrink so much. I was thinking of trying to do a DB diff between the two
>> but wasnt sure how to do this. Looked around a little and saw a few tools
>> but i was looking for a free solution.
>> Anyone know why this might have shrunk or a tool that i could use to do a
>> diff?
>>
>> Thanks
>> Justin
>|||Yeah i guess i didnt really think about that. its really not too hard to run
a script to give some basic statistics about tables. More just a resource
problem but i have some spare servers i can run this on.
Thanks!
Justin
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:CABE43A2-BD14-4E93-89FA-D5D5C8E12393@.microsoft.com...
> You can start by checking all the table sizes ;)
> Maybe somebody/changed to diffirential backup ?
> Cheers,
> Harry
>

Database Diagrams Problem....

Hi all,
I am trying to make DATABASE DIAGRAMs...I have restored a database called Tel from a backup file...n in that i have all the tables and procedures..now whenever i m clicking on its DATABASE DIAGRAMS it gives me the error as:

TITLE: Microsoft SQL Server Management Studio
----------

Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.

----------
so,what should i do??any suggestion will be helpful for me...thnks in advance...
regards..Try:

exec sp_changedbowner 'sa'

Database Diagrams

I have a SQL 2000 database that I imported into SQL Server 2005 by restoring
the database from a backup. I carefully re-did the Users to make sure there
were corresponding Logins.
I want to create a Database Diagram using the Microsoft SQL Server
Management Studio. When I right click on the Database Diagrams node within
the correct database I get the following error.
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTE AUTHORIZATION statement to set the
database owner to a valid login, then add the database diagram support
objects.
Now I did both of these suggestions and then looked at the owner of the
database, who in fact is a valid Login with sysadmin privileges.
I'm not sure where to go from here since everything seems to be done
correctly.
Any suggestions?
Michael Hockstein
This is covered in section 4.8 in the Readme file that comes with the
product .
To install database diagram support in SQL Server Management Studio,
databases must be in SQL Server 2005 database compatibility level. Database
compatibility level can be reset after diagram support is installed. To
create database diagrams, change the database compatibility level to 2005,
install database diagram support, and then return the database to the
desired database compatibility level. For more information, search for
"sp_dbcmptlevel" in SQL Server Books Online.
So, run the following statement and try the diagram again.
EXEC sp_dbcmptlevel database_name, 90
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"michael" <howlinghound@.nospam.nospam> wrote in message
news:EB3D155A-EC71-4854-BAC6-7B14BE038586@.microsoft.com...
>I have a SQL 2000 database that I imported into SQL Server 2005 by
>restoring
> the database from a backup. I carefully re-did the Users to make sure
> there
> were corresponding Logins.
> I want to create a Database Diagram using the Microsoft SQL Server
> Management Studio. When I right click on the Database Diagrams node
> within
> the correct database I get the following error.
> Database diagram support objects cannot be installed because this database
> does not have a valid owner. To continue, first use the Files page of the
> Database Properties dialog box or the ALTE AUTHORIZATION statement to set
> the
> database owner to a valid login, then add the database diagram support
> objects.
> Now I did both of these suggestions and then looked at the owner of the
> database, who in fact is a valid Login with sysadmin privileges.
> I'm not sure where to go from here since everything seems to be done
> correctly.
> Any suggestions?
> --
> Michael Hockstein
|||Fantastic. Worked like a charm. Could you also give me a clue as to where to
find the Readme file? I looked in the SQL Server directory and subs but
couldn't locate it. This would be a good one to keep on file.
Michael Hockstein
"Gail Erickson [MS]" wrote:

> This is covered in section 4.8 in the Readme file that comes with the
> product .
> To install database diagram support in SQL Server Management Studio,
> databases must be in SQL Server 2005 database compatibility level. Database
> compatibility level can be reset after diagram support is installed. To
> create database diagrams, change the database compatibility level to 2005,
> install database diagram support, and then return the database to the
> desired database compatibility level. For more information, search for
> "sp_dbcmptlevel" in SQL Server Books Online.
> So, run the following statement and try the diagram again.
> EXEC sp_dbcmptlevel database_name, 90
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:EB3D155A-EC71-4854-BAC6-7B14BE038586@.microsoft.com...
>
>
|||michael (howlinghound@.nospam.nospam) writes:
> Fantastic. Worked like a charm. Could you also give me a clue as to
> where to find the Readme file? I looked in the SQL Server directory and
> subs but couldn't locate it. This would be a good one to keep on file.
I happened to have the SQL 2005 server DVD in my player, and I found a
Readme in G:\SQL Server x86\Servers\ReadmeSQL2005.htm. There seem to be
one in every top-level setup directory.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
|||In addition to Erland's response, you can also find the readme here:
http://support.microsoft.com/default...b;en-us;910228
Also, the April update to Books Online will contain this information in the
various topics on database diagrams.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"michael" <howlinghound@.nospam.nospam> wrote in message
news:4885DE6E-B80F-4367-9B2E-D772F090CD7B@.microsoft.com...[vbcol=seagreen]
> Fantastic. Worked like a charm. Could you also give me a clue as to where
> to
> find the Readme file? I looked in the SQL Server directory and subs but
> couldn't locate it. This would be a good one to keep on file.
>
> --
> Michael Hockstein
>
> "Gail Erickson [MS]" wrote:
|||OK! Thanks for the tip.
Michael Hockstein
"Erland Sommarskog" wrote:

> michael (howlinghound@.nospam.nospam) writes:
> I happened to have the SQL 2005 server DVD in my player, and I found a
> Readme in G:\SQL Server x86\Servers\ReadmeSQL2005.htm. There seem to be
> one in every top-level setup directory.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pro...ads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinf...ons/books.mspx
>
|||Thanks Gail!
Michael Hockstein
"Gail Erickson [MS]" wrote:

> In addition to Erland's response, you can also find the readme here:
> http://support.microsoft.com/default...b;en-us;910228
> Also, the April update to Books Online will contain this information in the
> various topics on database diagrams.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "michael" <howlinghound@.nospam.nospam> wrote in message
> news:4885DE6E-B80F-4367-9B2E-D772F090CD7B@.microsoft.com...
>
>