DB2, SQL Server, and Oracle

Hello all, I am curious to know if anyone has done a trade study on DB2, SQL Server, and Oracle databases (all Enterprise editions). Basically I am trying to identify which one to chose based on "Ease of implementation", Ease of maintenance", "Pricing" and "Ease of technical support". The criteria I am looking at can be obtained by interviewing people who have worked with these products. I appreciate any input I can get. Thanks, Shaunplease do not cross-post

http://www.dbforums.com/t1101738.htmlsql

db_owner role and table owner issues

Hi,

I have given a user db_owner role in a database. When he creates a table using Enterprise manager the table owner is dbo. When he creates a table using Query Analyzer the table owner is the user. eg

Enterprise Manager = dbo.Table1

Query Analyer = username.Table1

This causes a problem when the user is writing web applications. Is this an error in the way i have set up permissions ? How can i make them behave the same way?

Thanks for your help.First, don't create tables in EM

Second, it's how they are connecting...

Third, depending on how you want the application to work, qualify the owner...

Fourth, get control...

have them supply you with the DDL, and you create the tables for them...

My guess is that EM is connected with sa, and QA is connecting with their id...

just a guess...|||Thanks for your quick response. I should have included the following information.

I work in a University computing department where students must learn to create tables etc. I could not create their tables for them as it is part of their assessment (and there are 1700 students!)

Students can only log on to the server using windows authentication so will log on using the same windows account to both EM and QA.

Students are taught to use both EM and QA which is why they are finding problems.

Thanks again for all help.|||Gotta test it...which way do you want the tables qualified for their apps...

dbo?

I'll look into it...|||yes dbo thank you.

DB Transactional Log Files

I have SQL Server 2000 Enterprise with SP3A and Windows
2000 Advanced Server.
I have one database with two transactional log files. The
two transactional log files are on different drives
(F:,G.
I would like to have the first transaction log file (F
set to automatically grow and the second transaction log
file restricted log growth to 30GB.
Please help me with this issue.
Thanks,
Dan
Within Enterprise Manager (within the SQL Server program group) you =
should be able to=20
right click on the database icon
properties
transaction log tab
Configure one file to be restricted to a maximum file size and the other =
file would be unrestricted. =20
With that said, 30GB is a fairly large transaction log file. If you =
need more than this you are probably doing massive amounts of data =
movement (into a reporting database, perhaps) OR you are not backing up =
your data in the best manner. If you want to investigate backup =
techniques, Books Online (within the SQL Server program group) has lots =
of information regarding backup and restore as well as performing =
transaction log backups and having the ability to restore to the point =
of failure (should one occur).
--=20
Keith
"Dan" <anonymous@.discussions.microsoft.com> wrote in message =
news:1e1ea01c4554f$266f1d10$a301280a@.phx.gbl...
>=20
> I have SQL Server 2000 Enterprise with SP3A and Windows=20
> 2000 Advanced Server.
>=20
> I have one database with two transactional log files. The=20
> two transactional log files are on different drives=20
> (F:,G.=20
>=20
> I would like to have the first transaction log file (F=20
> set to automatically grow and the second transaction log=20
> file restricted log growth to 30GB.
>=20
> Please help me with this issue.
>=20
> Thanks,
>=20
> Dan

DB Transactional Log Files

I have SQL Server 2000 Enterprise with SP3A and Windows
2000 Advanced Server.
I have one database with two transactional log files. The
two transactional log files are on different drives
(F:,G.
I would like to have the first transaction log file (F
set to automatically grow and the second transaction log
file restricted log growth to 30GB.
Please help me with this issue.
Thanks,
DanWithin Enterprise Manager (within the SQL Server program group) you =
should be able to=20
right click on the database icon
properties
transaction log tab
Configure one file to be restricted to a maximum file size and the other =
file would be unrestricted. =20
With that said, 30GB is a fairly large transaction log file. If you =
need more than this you are probably doing massive amounts of data =
movement (into a reporting database, perhaps) OR you are not backing up =
your data in the best manner. If you want to investigate backup =
techniques, Books Online (within the SQL Server program group) has lots =
of information regarding backup and restore as well as performing =
transaction log backups and having the ability to restore to the point =
of failure (should one occur).
--=20
Keith
"Dan" <anonymous@.discussions.microsoft.com> wrote in message =
news:1e1ea01c4554f$266f1d10$a301280a@.phx
.gbl...
>=20
> I have SQL Server 2000 Enterprise with SP3A and Windows=20
> 2000 Advanced Server.
>=20
> I have one database with two transactional log files. The=20
> two transactional log files are on different drives=20
> (F:,G.=20
>=20
> I would like to have the first transaction log file (F=20
> set to automatically grow and the second transaction log=20
> file restricted log growth to 30GB.
>=20
> Please help me with this issue.
>=20
> Thanks,
>=20
> Dan

DB Transactional Log Files

I have SQL Server 2000 Enterprise with SP3A and Windows
2000 Advanced Server.
I have one database with two transactional log files. The
two transactional log files are on different drives
(F:,G:).
I would like to have the first transaction log file (F:)
set to automatically grow and the second transaction log
file restricted log growth to 30GB.
Please help me with this issue.
Thanks,
DanWithin Enterprise Manager (within the SQL Server program group) you =should be able to right click on the database icon
properties
transaction log tab
Configure one file to be restricted to a maximum file size and the other =file would be unrestricted.
With that said, 30GB is a fairly large transaction log file. If you =need more than this you are probably doing massive amounts of data =movement (into a reporting database, perhaps) OR you are not backing up =your data in the best manner. If you want to investigate backup =techniques, Books Online (within the SQL Server program group) has lots =of information regarding backup and restore as well as performing =transaction log backups and having the ability to restore to the point =of failure (should one occur).
-- Keith
"Dan" <anonymous@.discussions.microsoft.com> wrote in message =news:1e1ea01c4554f$266f1d10$a301280a@.phx.gbl...
> > I have SQL Server 2000 Enterprise with SP3A and Windows > 2000 Advanced Server.
> > I have one database with two transactional log files. The > two transactional log files are on different drives > (F:,G:). > > I would like to have the first transaction log file (F:) > set to automatically grow and the second transaction log > file restricted log growth to 30GB.
> > Please help me with this issue.
> > Thanks,
> > Dan

DB Suspect...

I'm using SQL Server 2K n 1 fine morning I recieve this
error saying "Database Suspect", in Enterprise Manager.
By the way, I'm using Windows NT.
How can I get my DB out of this Suspect mode?
Any answers will be highly appreciated.That CANNOT be a reason by any chance. As said have you tried the options
specified in the SQL Server BOL ?
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
"Biju" <reachcybercop@.yahoo.com> wrote in message
news:0e6201c37e83$75a614e0$a101280a@.phx.gbl...
> Well, I had installed SP3 just a couple of days back.
> Could this be the reason?
> >--Original Message--
> >Check in the SQL Server error logs and the NT event logs
> first. You
> >need to also know why it went west to prevent it
> happening again.
> >
> >Check out this in BOL also
> >
> >mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%
> 20Server\80\Tools\Book
> >s\trblsql.chm::/tr_servdatabse_494j.htm
> >
> >
> >Also just in case I would start to dig out your Backups.
> >
> >
> >Allan Mitchell (Microsoft SQL Server MVP)
> >MCSE,MCDBA
> >www.SQLDTS.com
> >I support PASS - the definitive, global community
> >for SQL Server professionals - http://www.sqlpass.org
> >
> >.
> >|||I wouldn't have thought so (SP3 what ? DB, Windows) as you would have
had to have rebooted after applying it and I would have expected things
to go west then. What do the logs say? Do you have enough Disk space?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org|||following err message comes up in SQL Server log:
Device activation error. The physical file
name 'C:\Program Files\Seagate
Software\Enterprise\ODBCSUPT\CE8_log.ldf' may be incorrect.
>--Original Message--
>Well, I had installed SP3 just a couple of days back.
>Could this be the reason?
>>--Original Message--
>>Check in the SQL Server error logs and the NT event logs
>first. You
>>need to also know why it went west to prevent it
>happening again.
>>Check out this in BOL also
>>mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%
>20Server\80\Tools\Book
>>s\trblsql.chm::/tr_servdatabse_494j.htm
>>
>>Also just in case I would start to dig out your Backups.
>>
>>Allan Mitchell (Microsoft SQL Server MVP)
>>MCSE,MCDBA
>>www.SQLDTS.com
>>I support PASS - the definitive, global community
>>for SQL Server professionals - http://www.sqlpass.org
>>.
>.
>|||have enough disk space
>--Original Message--
>following err message comes up in SQL Server log:
>Device activation error. The physical file
>name 'C:\Program Files\Seagate
>Software\Enterprise\ODBCSUPT\CE8_log.ldf' may be
incorrect.
>
>>--Original Message--
>>Well, I had installed SP3 just a couple of days back.
>>Could this be the reason?
>>--Original Message--
>>Check in the SQL Server error logs and the NT event
logs
>>first. You
>>need to also know why it went west to prevent it
>>happening again.
>>Check out this in BOL also
>>mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%
>>20Server\80\Tools\Book
>>s\trblsql.chm::/tr_servdatabse_494j.htm
>>
>>Also just in case I would start to dig out your Backups.
>>
>>Allan Mitchell (Microsoft SQL Server MVP)
>>MCSE,MCDBA
>>www.SQLDTS.com
>>I support PASS - the definitive, global community
>>for SQL Server professionals - http://www.sqlpass.org
>>.
>>.
>.
>|||In article <7f1701c37e88$ab23d490$a601280a@.phx.gbl>, Biju wrote:
> activation error. The physical file
> name 'C:\Program Files\Seagate
> Software\Enterprise\ODBCSUPT\CE8_log.ldf
>
check for
A. Diskspace on C:\
B. The existence of the file
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

DB Suspect (full error log attached)

Hi Gurus,
One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced server) went suspect yesterday. Here is part of the error log. Would appreciate any help/suggestions.
2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:17:42.74 spid72 pageno is/should be:objid is/should be:
2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)457768688/1269579561
2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to this object
2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to object 't050_pre_arch', not to object 't050_campaign_candidate'..
2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '16905830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
(actual dump manually taken out here)
* ----
2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>, line=321
Failed Assertion = 'm_len != 0'.
2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not available..
2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9189:1)..
2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% complete (approximately 2 more seconds)
2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% complete (approximately 0 more seconds)
2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complete (approximately 28 more seconds) (Phase 2 of 3).
2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% complete (approximately 98 more seconds) (Phase 2 of 3).
2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% complete (approximately 88 more seconds) (Phase 2 of 3).
2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% complete (approximately 83 more seconds) (Phase 2 of 3).
2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% complete (approximately 77 more seconds) (Phase 2 of 3).
2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% complete (approximately 72 more seconds) (Phase 2 of 3).
2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% complete (approximately 69 more seconds) (Phase 2 of 3).
2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% complete (approximately 64 more seconds) (Phase 2 of 3).
2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% complete (approximately 58 more seconds) (Phase 2 of 3).
2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% complete (approximately 53 more seconds) (Phase 2 of 3).
2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% complete (approximately 48 more seconds) (Phase 2 of 3).
2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% complete (approximately 44 more seconds) (Phase 2 of 3).
2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% complete (approximately 39 more seconds) (Phase 2 of 3).
2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% complete (approximately 35 more seconds) (Phase 2 of 3).
2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% complete (approximately 30 more seconds) (Phase 2 of 3).
2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% complete (approximately 26 more seconds) (Phase 2 of 3).
2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% complete (approximately 21 more seconds) (Phase 2 of 3).
2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% complete (approximately 17 more seconds) (Phase 2 of 3).
2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% complete (approximately 12 more seconds) (Phase 2 of 3).
2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% complete (approximately 7 more seconds) (Phase 2 of 3).
2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% complete (approximately 3 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database 'S094000' (27).
2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S094000' (27).
2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000' (27)
2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:21:19.65 spid61 pageno is/should be:objid is/should be:
2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)457768688/1269579561
2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to this object
2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to object 't050_pre_arch', not to object 't050_campaign_candidate'..
2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '16905830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:10761:6)..
2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
Hi -
1. Important :: {Do you have previously clean backup? If yes, please restore
from the backup.}
OR
1. Execute DBCC CHECKDB to determine the extent of the damage, use the
REPAIR_REBUILD clause. If problem persists drop and re-create the index
Also Please provide output from DBCC CHECKDB.
2. Examine the error log for any errors prior to error 3414. It is important
to examine errors that occurred before the first occurrence of error 3414
because subsequent attempts to start the server might not give the detailed
error information you need to diagnose the problem. If you do not have
sufficient information to recover from the previous errors, you can recover
from known clean backups
I guess the problem is with the corrupt index Allocation Map or some thing
whirred in the sysobjects table.
Thanks
-Surajit
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k
Advanced server) went suspect yesterday. Here is part of the error log.
Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should
be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
>
* ----
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is
0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File:
<scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not
available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is
16% complete (approximately 2 more seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is
100% complete (approximately 0 more seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0%
complete (approximately 28 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is
17% complete (approximately 98 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is
21% complete (approximately 88 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is
25% complete (approximately 83 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is
30% complete (approximately 77 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is
34% complete (approximately 72 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is
39% complete (approximately 69 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is
43% complete (approximately 64 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is
48% complete (approximately 58 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is
52% complete (approximately 53 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is
56% complete (approximately 48 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is
61% complete (approximately 44 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is
65% complete (approximately 39 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is
70% complete (approximately 35 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is
74% complete (approximately 30 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is
78% complete (approximately 26 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is
82% complete (approximately 21 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is
86% complete (approximately 17 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is
90% complete (approximately 12 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is
93% complete (approximately 7 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is
97% complete (approximately 3 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in
database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is
100% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database
'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database
'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should
be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>
|||In addition to Surajit's post:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced server) went suspect yesterday.
Here is part of the error log. Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '16905830100' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
> * ----
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% complete (approximately 2 more
seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% complete (approximately 0 more
seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complete (approximately 28 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% complete (approximately 98 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% complete (approximately 88 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% complete (approximately 83 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% complete (approximately 77 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% complete (approximately 72 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% complete (approximately 69 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% complete (approximately 64 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% complete (approximately 58 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% complete (approximately 53 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% complete (approximately 48 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% complete (approximately 44 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% complete (approximately 39 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% complete (approximately 35 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% complete (approximately 30 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% complete (approximately 26 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% complete (approximately 21 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% complete (approximately 17 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% complete (approximately 12 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% complete (approximately 7 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% complete (approximately 3 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% complete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '16905830100' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>

DB Suspect (full error log attached)

Hi Gurus,
One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced
server) went suspect yesterday. Here is part of the error log. Would apprec
iate any help/suggestions.
2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be:
2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/12695795
61
2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to
this object
2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in
database 'S094000' belongs to object 't050_pre_arch', not to object 't050_c
ampaign_candidate'..
2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '169
05830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
(actual dump manually taken out here)
* ----
--
2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>,
line=321
Failed Assertion = 'm_len != 0'.
2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not avail
able..
2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:9189:1)..
2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16%
complete (approximately 2 more seconds)
2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100%
complete (approximately 0 more seconds)
2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% c
omplete (approximately 28 more seconds) (Phase 2 of 3).
2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17%
complete (approximately 98 more seconds) (Phase 2 of 3).
2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21%
complete (approximately 88 more seconds) (Phase 2 of 3).
2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25%
complete (approximately 83 more seconds) (Phase 2 of 3).
2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30%
complete (approximately 77 more seconds) (Phase 2 of 3).
2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34%
complete (approximately 72 more seconds) (Phase 2 of 3).
2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39%
complete (approximately 69 more seconds) (Phase 2 of 3).
2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43%
complete (approximately 64 more seconds) (Phase 2 of 3).
2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48%
complete (approximately 58 more seconds) (Phase 2 of 3).
2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52%
complete (approximately 53 more seconds) (Phase 2 of 3).
2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56%
complete (approximately 48 more seconds) (Phase 2 of 3).
2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61%
complete (approximately 44 more seconds) (Phase 2 of 3).
2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65%
complete (approximately 39 more seconds) (Phase 2 of 3).
2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70%
complete (approximately 35 more seconds) (Phase 2 of 3).
2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74%
complete (approximately 30 more seconds) (Phase 2 of 3).
2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78%
complete (approximately 26 more seconds) (Phase 2 of 3).
2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82%
complete (approximately 21 more seconds) (Phase 2 of 3).
2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86%
complete (approximately 17 more seconds) (Phase 2 of 3).
2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90%
complete (approximately 12 more seconds) (Phase 2 of 3).
2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93%
complete (approximately 7 more seconds) (Phase 2 of 3).
2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97%
complete (approximately 3 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99%
complete (approximately 0 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database
'S094000' (27).
2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99%
complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100%
complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S09
4000' (27).
2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000
' (27)
2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be:
2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/12695795
61
2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to
this object
2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in
database 'S094000' belongs to object 't050_pre_arch', not to object 't050_c
ampaign_candidate'..
2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '169
05830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in dat
abase 'S094000'. Error at log record ID (63154:10761:6)..
2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528Hi -
1. Important :: {Do you have previously clean backup? If yes, please re
store
from the backup.}
OR
1. Execute DBCC CHECKDB to determine the extent of the damage, use the
REPAIR_REBUILD clause. If problem persists drop and re-create the index
Also Please provide output from DBCC CHECKDB.
2. Examine the error log for any errors prior to error 3414. It is important
to examine errors that occurred before the first occurrence of error 3414
because subsequent attempts to start the server might not give the detailed
error information you need to diagnose the problem. If you do not have
sufficient information to recover from the previous errors, you can recover
from known clean backups
I guess the problem is with the corrupt index Allocation Map or some thing
whirred in the sysobjects table.
Thanks
-Surajit
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k
Advanced server) went suspect yesterday. Here is part of the error log.
Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should
be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
>
* ----
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is
0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File:
<scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not
available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is
16% complete (approximately 2 more seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is
100% complete (approximately 0 more seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0%
complete (approximately 28 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is
17% complete (approximately 98 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is
21% complete (approximately 88 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is
25% complete (approximately 83 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is
30% complete (approximately 77 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is
34% complete (approximately 72 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is
39% complete (approximately 69 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is
43% complete (approximately 64 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is
48% complete (approximately 58 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is
52% complete (approximately 53 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is
56% complete (approximately 48 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is
61% complete (approximately 44 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is
65% complete (approximately 39 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is
70% complete (approximately 35 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is
74% complete (approximately 30 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is
78% complete (approximately 26 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is
82% complete (approximately 21 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is
86% complete (approximately 17 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is
90% complete (approximately 12 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is
93% complete (approximately 7 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is
97% complete (approximately 3 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in
database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is
100% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database
'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database
'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should
be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>|||In addition to Surajit's post:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced serve
r) went suspect yesterday.
Here is part of the error log. Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be
:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/1269579
561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in datab
ase 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '169058301
00' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
> * ---
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F8
2
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>
, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not ava
ilable..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% comple
te (approximately 2 more
seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% compl
ete (approximately 0 more
seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complet
e (approximately 28 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% comple
te (approximately 98 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% comple
te (approximately 88 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% comple
te (approximately 83 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% comple
te (approximately 77 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% comple
te (approximately 72 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% comple
te (approximately 69 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% comple
te (approximately 64 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% comple
te (approximately 58 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% comple
te (approximately 53 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% comple
te (approximately 48 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% comple
te (approximately 44 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% comple
te (approximately 39 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% comple
te (approximately 35 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% comple
te (approximately 30 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% comple
te (approximately 26 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% comple
te (approximately 21 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% comple
te (approximately 17 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% comple
te (approximately 12 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% comple
te (approximately 7 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% comple
te (approximately 3 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% comple
te (approximately 0 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in databa
se 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% comple
te (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% compl
ete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S
094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S0940
00' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be
:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/1269579
561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in datab
ase 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '169058301
00' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database
'S094000'. Error at log
record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>sql

DB schema in Visio

Hi,
we have database on SQL server 2000 and want to be able
to maintain it from within Visio (version 2003 Enterprise
Architect) or at least use Visio for documentation the
database.
Has anyone some experience with maintenance db schema in visio?
I created new Database model diagram and used Reverse
Engineering to fill it with our schema. The problem is
that if DB is modified, e.g. new table/SP is added (via
sql script or SQL Enterprise Manager) and then we want to
refresh the model in Visio with Database->Model->Refresh
command, Visio does not notice the change and does not
offer to add new table/SP into model.
How I could achieve this?
Thanks
eXavierWhen you refresh you must choose whether to update the model or the database
or both... Are you sure you are selecting update model?...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"eXavier" <hurta@.email.cz> wrote in message
news:bkcf3r$3c2$1@.ns.felk.cvut.cz...
> Hi,
> we have database on SQL server 2000 and want to be able
> to maintain it from within Visio (version 2003 Enterprise
> Architect) or at least use Visio for documentation the
> database.
> Has anyone some experience with maintenance db schema in visio?
> I created new Database model diagram and used Reverse
> Engineering to fill it with our schema. The problem is
> that if DB is modified, e.g. new table/SP is added (via
> sql script or SQL Enterprise Manager) and then we want to
> refresh the model in Visio with Database->Model->Refresh
> command, Visio does not notice the change and does not
> offer to add new table/SP into model.
> How I could achieve this?
> Thanks
> eXavier
>
>|||This should work. Visio should pick up the new table if the DSN is the same
and the created table has a new table name. Not sure why it isn't working in
this case.
Please try your workflow on the Northwind database and see if it works.
Reverse-engineer NW, then add a table to NW and do a Model Refresh.
--
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:OwkSXUgfDHA.2348@.TK2MSFTNGP12.phx.gbl...
> When you refresh you must choose whether to update the model or the
database
> or both... Are you sure you are selecting update model?...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "eXavier" <hurta@.email.cz> wrote in message
> news:bkcf3r$3c2$1@.ns.felk.cvut.cz...
> > Hi,
> > we have database on SQL server 2000 and want to be able
> > to maintain it from within Visio (version 2003 Enterprise
> > Architect) or at least use Visio for documentation the
> > database.
> > Has anyone some experience with maintenance db schema in visio?
> > I created new Database model diagram and used Reverse
> > Engineering to fill it with our schema. The problem is
> > that if DB is modified, e.g. new table/SP is added (via
> > sql script or SQL Enterprise Manager) and then we want to
> > refresh the model in Visio with Database->Model->Refresh
> > command, Visio does not notice the change and does not
> > offer to add new table/SP into model.
> > How I could achieve this?
> >
> > Thanks
> > eXavier
> >
> >
> >
>

DB properties cannot be changed with Enterprise Manager

Hello,

after the upgrade of MS SQL Server 7 to MS SQL Server 2000 on MS Windows 2000 Server and installation of MS SQL Server 2000 SP2 it is not possible to make changes to DB properties of user DBs with Enterprise Manager. MS SQL Server Instance properties and System DB properties are changeable with Enterprise Manager, but user DB properties can only be changed using Query Analyzer.

Has anybody an idea how to fix this problem?

Regards
Joe :rolleyes:Hi,

Do u trying to change by local Enterprise Manager or over Network?

Remember that are some new things in (2000) Permissions topic.

Explain more your schema.

[ ]'s|||Hi,

I tried to use the enterprise manager local and remote. Both doesn't work. I can display the user DB properties, but the ok button is grey. So I cannot use it.
What do you mean with new permissions at SQL 2000?

Regards
Joe

db permissions in EM

i've got a user that has permissions to read and write in two
databases. that user has enterprise manager installed and uses it (i
know he shouldn't really have it, but that's another topic). he can see
all of the databases on the server. is there any way to make EM only
show him the two databases which he can access?
ch
Unfortunatly,NO
"ch" <ch@.dontemailme.com> wrote in message
news:41862283.D2817F00@.dontemailme.com...
> i've got a user that has permissions to read and write in two
> databases. that user has enterprise manager installed and uses it (i
> know he shouldn't really have it, but that's another topic). he can see
> all of the databases on the server. is there any way to make EM only
> show him the two databases which he can access?
|||i think i figured out how to do it.
a few changes to master.dbo.sp_MSdbuseraccess
Uri Dimant wrote:[vbcol=seagreen]
> ch
> Unfortunatly,NO
> "ch" <ch@.dontemailme.com> wrote in message
> news:41862283.D2817F00@.dontemailme.com...
|||Which means you no longer have a supported SQL server installation. Be careful when modifying system
objects. Not supported.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:41862EC4.7EF0C91A@.dontemailme.com...
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
>
|||ch
You can hide a system databases from seeing them with EM , but user
databases you cannot.
"ch" <ch@.dontemailme.com> wrote in message
news:41862EC4.7EF0C91A@.dontemailme.com...[vbcol=seagreen]
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
>
> Uri Dimant wrote:
see[vbcol=seagreen]
|||this is sort of goofy.
query analyzer uses master.dbo.sp_MShasdbaccess intead of
master.dbo.sp_MSdbuseraccess.
sp_MShasdbaccess only returns the databases that the user can get into
or the db's that have a guest account.
sp_MSdbuseraccess returns all databases (when run from master).
query analyzer therefore only shows the user the databases that user can
actually get into which is what i'd really like enterprise manager to
do. i wonder why the two different standards between the two tools?
ch wrote:[vbcol=seagreen]
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
> Uri Dimant wrote:

db permissions in EM

i've got a user that has permissions to read and write in two
databases. that user has enterprise manager installed and uses it (i
know he shouldn't really have it, but that's another topic). he can see
all of the databases on the server. is there any way to make EM only
show him the two databases which he can access?ch
Unfortunatly,NO
"ch" <ch@.dontemailme.com> wrote in message
news:41862283.D2817F00@.dontemailme.com...
> i've got a user that has permissions to read and write in two
> databases. that user has enterprise manager installed and uses it (i
> know he shouldn't really have it, but that's another topic). he can see
> all of the databases on the server. is there any way to make EM only
> show him the two databases which he can access?|||i think i figured out how to do it.
a few changes to master.dbo.sp_MSdbuseraccess
Uri Dimant wrote:[vbcol=seagreen]
> ch
> Unfortunatly,NO
> "ch" <ch@.dontemailme.com> wrote in message
> news:41862283.D2817F00@.dontemailme.com...|||Which means you no longer have a supported SQL server installation. Be caref
ul when modifying system
objects. Not supported.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:41862EC4.7EF0C91A@.dontemailme.com...eagreen">
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
>|||ch
You can hide a system databases from seeing them with EM , but user
databases you cannot.
"ch" <ch@.dontemailme.com> wrote in message
news:41862EC4.7EF0C91A@.dontemailme.com...[vbcol=seagreen]
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
>
> Uri Dimant wrote:
see[vbcol=seagreen]|||this is sort of goofy.
query analyzer uses master.dbo.sp_MShasdbaccess intead of
master.dbo.sp_MSdbuseraccess.
sp_MShasdbaccess only returns the databases that the user can get into
or the db's that have a guest account.
sp_MSdbuseraccess returns all databases (when run from master).
query analyzer therefore only shows the user the databases that user can
actually get into which is what i'd really like enterprise manager to
do. i wonder why the two different standards between the two tools?
ch wrote:[vbcol=seagreen]
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
> Uri Dimant wrote:

db permissions in EM

i've got a user that has permissions to read and write in two
databases. that user has enterprise manager installed and uses it (i
know he shouldn't really have it, but that's another topic). he can see
all of the databases on the server. is there any way to make EM only
show him the two databases which he can access?ch
Unfortunatly,NO
"ch" <ch@.dontemailme.com> wrote in message
news:41862283.D2817F00@.dontemailme.com...
> i've got a user that has permissions to read and write in two
> databases. that user has enterprise manager installed and uses it (i
> know he shouldn't really have it, but that's another topic). he can see
> all of the databases on the server. is there any way to make EM only
> show him the two databases which he can access?|||i think i figured out how to do it.
a few changes to master.dbo.sp_MSdbuseraccess
Uri Dimant wrote:
> ch
> Unfortunatly,NO
> "ch" <ch@.dontemailme.com> wrote in message
> news:41862283.D2817F00@.dontemailme.com...
> > i've got a user that has permissions to read and write in two
> > databases. that user has enterprise manager installed and uses it (i
> > know he shouldn't really have it, but that's another topic). he can see
> > all of the databases on the server. is there any way to make EM only
> > show him the two databases which he can access?|||Which means you no longer have a supported SQL server installation. Be careful when modifying system
objects. Not supported.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:41862EC4.7EF0C91A@.dontemailme.com...
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
>|||ch
You can hide a system databases from seeing them with EM , but user
databases you cannot.
"ch" <ch@.dontemailme.com> wrote in message
news:41862EC4.7EF0C91A@.dontemailme.com...
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
>
> Uri Dimant wrote:
> >
> > ch
> > Unfortunatly,NO
> >
> > "ch" <ch@.dontemailme.com> wrote in message
> > news:41862283.D2817F00@.dontemailme.com...
> > > i've got a user that has permissions to read and write in two
> > > databases. that user has enterprise manager installed and uses it (i
> > > know he shouldn't really have it, but that's another topic). he can
see
> > > all of the databases on the server. is there any way to make EM only
> > > show him the two databases which he can access?|||this is sort of goofy.
query analyzer uses master.dbo.sp_MShasdbaccess intead of
master.dbo.sp_MSdbuseraccess.
sp_MShasdbaccess only returns the databases that the user can get into
or the db's that have a guest account.
sp_MSdbuseraccess returns all databases (when run from master).
query analyzer therefore only shows the user the databases that user can
actually get into which is what i'd really like enterprise manager to
do. i wonder why the two different standards between the two tools?
ch wrote:
> i think i figured out how to do it.
> a few changes to master.dbo.sp_MSdbuseraccess
> Uri Dimant wrote:
> >
> > ch
> > Unfortunatly,NO
> >
> > "ch" <ch@.dontemailme.com> wrote in message
> > news:41862283.D2817F00@.dontemailme.com...
> > > i've got a user that has permissions to read and write in two
> > > databases. that user has enterprise manager installed and uses it (i
> > > know he shouldn't really have it, but that's another topic). he can see
> > > all of the databases on the server. is there any way to make EM only
> > > show him the two databases which he can access?