Enterprise Manager Showing Wrong Authentication Mechanism

This is strange,
SQL Authentication is set to mixed mode on an SQL 2000 Server but if I TS
into the server or I look on the console locally, it shows it as only being
Windows Authentication...
Anyone know of this bug? And how to fix?How do you know it's set to mixed mode? Did you try logging
in with a SQL login?
If you are just looking at a registry setting, it's possible
the service was not restarted to allow the server to be set
to mixed mode.
-Sue
On Tue, 13 Sep 2005 14:38:59 -0700, "Chuck"
<Chuck@.discussions.microsoft.com> wrote:

>This is strange,
>SQL Authentication is set to mixed mode on an SQL 2000 Server but if I TS
>into the server or I look on the console locally, it shows it as only being
>Windows Authentication...
>Anyone know of this bug? And how to fix?|||Yes, I am currently logging in as an SQL login account. This client of mine
does not use Windows authentication...
"Sue Hoegemeier" wrote:

> How do you know it's set to mixed mode? Did you try logging
> in with a SQL login?
> If you are just looking at a registry setting, it's possible
> the service was not restarted to allow the server to be set
> to mixed mode.
> -Sue
> On Tue, 13 Sep 2005 14:38:59 -0700, "Chuck"
> <Chuck@.discussions.microsoft.com> wrote:
>
>|||_-=?/today_-=?/354
"Chuck" wrote:

> This is strange,
> SQL Authentication is set to mixed mode on an SQL 2000 Server but if I TS
> into the server or I look on the console locally, it shows it as only bein
g
> Windows Authentication...
> Anyone know of this bug? And how to fix?|||_-=?/today_-=?/354
"Chuck" wrote:
[vbcol=seagreen]
> Yes, I am currently logging in as an SQL login account. This client of mi
ne
> does not use Windows authentication...
> "Sue Hoegemeier" wrote:
>

Enterprise Manager reporting wrong server version

I am running MS SQL 2000.

I recently ran a procedure in Query Analyzer from the Master db to
clear out all replication information so I could start/recreate it
again.

After I ran this procedure Enterprise Manager no longer showed the
registered server in the tree. When I tried to re-register it gave me
the following message:

"A connection could not be established to ([Database Name])"

"Reason: [SQL-DMO]Sql Server ([Database Name]) must be upgraded to
version 7.0 or later to be administered by this version of SQL-DMO"

"Please verify that sql is running and check your SQL server
registration properties (by right click on the ([Database Name]) node)
and try again."

I ran the following procedure:

<code>
exec sp_configure N'allow updates', 1
go
reconfigure with override
go

DECLARE @.name varchar(129)
DECLARE @.username varchar(129)
DECLARE @.insname varchar(129)
DECLARE @.delname varchar(129)
DECLARE @.updname varchar(129)
set @.insname=''
set @.updname=''
set @.delname=''

DECLARE list_triggers CURSOR FOR
select distinct replace(artid,'-',''), sysusers.name from
sysmergearticles,sysobjects, sysusers where
sysmergearticles.objid=sysobjects.id
and sysusers.uid=sysobjects.uid

OPEN list_triggers

FETCH NEXT FROM list_triggers INTO @.name, @.username
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping trigger ins_' +@.name
select @.insname='drop trigger ' +@.username+'.ins_'+@.name
exec (@.insname)
PRINT 'dropping trigger upd_' +@.name
select @.updname='drop trigger ' +@.username+'.upd_'+@.name
exec (@.delname)
PRINT 'dropping trigger del_' +@.name
select @.delname='drop trigger ' +@.username+'.del_'+@.name
exec (@.updname)
FETCH NEXT FROM list_triggers INTO @.name, @.username
END

CLOSE list_triggers
DEALLOCATE list_triggers
go

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[syspublications]') and OBJECTPROPERTY(id,
N'IsUserTable')
= 1) begin DECLARE @.name varchar(129)
DECLARE list_pubs CURSOR FOR
SELECT name FROM syspublications

OPEN list_pubs

FETCH NEXT FROM list_pubs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping publication ' +@.name
EXEC sp_dropsubscription @.publication=@.name, @.article='all',
@.subscriber
='all'
EXEC sp_droppublication @.name
FETCH NEXT FROM list_pubs INTO @.name
END

CLOSE list_pubs
DEALLOCATE list_pubs
end
GO

DECLARE @.name varchar(129)
DECLARE list_replicated_tables CURSOR FOR
SELECT name FROM sysobjects WHERE replinfo <>0
UNION
SELECT name FROM sysmergearticles

OPEN list_replicated_tables

FETCH NEXT FROM list_replicated_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'unmarking replicated table ' +@.name
--select @.name='drop Table ' + @.name
EXEC sp_msunmarkreplinfo @.name
FETCH NEXT FROM list_replicated_tables INTO @.name
END

CLOSE list_replicated_tables
DEALLOCATE list_replicated_tables

GO

UPDATE syscolumns set colstat = colstat & ~4096 WHERE colstat &4096
<>0
GO

UPDATE sysobjects set replinfo=0
GO

DECLARE @.name nvarchar(129)
DECLARE list_views CURSOR FOR
SELECT name FROM sysobjects WHERE type='V' and (name like 'syncobj_%'
or
name
like 'ctsv_%' or name like 'tsvw_%' or name like 'ms_bi%')

OPEN list_views

FETCH NEXT FROM list_views INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping View ' +@.name
select @.name='drop View ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_views INTO @.name
END

CLOSE list_views
DEALLOCATE list_views

GO

DECLARE @.name nvarchar(129)
DECLARE list_procs CURSOR FOR
SELECT name FROM sysobjects WHERE type='p' and (name like 'sp_ins_%'
or
name
like 'sp_MSdel_%' or name like 'sp_MSins_%'or name like 'sp_MSupd_%' or
name
like 'sp_sel_%' or name like 'sp_upd_%')

OPEN list_procs

FETCH NEXT FROM list_procs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping procs ' +@.name
select @.name='drop procedure ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_procs INTO @.name
END

CLOSE list_procs
DEALLOCATE list_procs

GO

DECLARE @.name nvarchar(129)
DECLARE list_conflict_tables CURSOR FOR
SELECT name From sysobjects WHERE type='u' and name like '_onflict%'

OPEN list_conflict_tables

FETCH NEXT FROM list_conflict_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping conflict_tables ' +@.name
select @.name='drop Table ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_conflict_tables INTO @.name
END

CLOSE list_conflict_tables
DEALLOCATE list_conflict_tables

GO

UPDATE syscolumns set colstat=2 WHERE name='rowguid'

GO

Declare @.name nvarchar(200), @.constraint nvarchar(200)
DECLARE list_rowguid_constraints CURSOR FOR
select sysusers.name+'.'+object_name(sysobjects.parent_ob j),
sysobjects.name
from sysobjects, syscolumns,sysusers where sysobjects.type ='d' and
syscolumns.id=sysobjects.parent_obj
and sysusers.uid=sysobjects.uid
and syscolumns.name='rowguid'

OPEN list_rowguid_constraints

FETCH NEXT FROM list_rowguid_constraints INTO @.name, @.constraint WHILE
@.@.FETCH_STATUS = 0 BEGIN
PRINT 'dropping rowguid constraints ' +@.name
select @.name='ALTER TABLE ' + rtrim(@.name) + ' DROP CONSTRAINT '
+@.constraint
print @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_constraints INTO @.name, @.constraint END

CLOSE list_rowguid_constraints
DEALLOCATE list_rowguid_constraints

GO

Declare @.name nvarchar(129), @.constraint nvarchar(129)
DECLARE list_rowguid_indexes CURSOR FOR
select sysusers.name+'.'+object_name(sysindexes.id), sysindexes.name
from
sysindexes, sysobjects,sysusers where sysindexes.name like 'index%' and
sysobjects.id=sysindexes.id and sysusers.uid=sysobjects.uid

OPEN list_rowguid_indexes

FETCH NEXT FROM list_rowguid_indexes INTO @.name, @.constraint WHILE
@.@.FETCH_STATUS = 0 BEGIN
PRINT 'dropping rowguid indexes ' +@.name
select @.name='drop index ' + rtrim(@.name ) + '.' +@.constraint
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_indexes INTO @.name, @.constraint END

CLOSE list_rowguid_indexes
DEALLOCATE list_rowguid_indexes
GO

Declare @.name nvarchar(129), @.constraint nvarchar(129)
DECLARE list_ms_bidi_tables CURSOR FOR
select sysusers.name+'.'+sysobjects.name from
sysobjects,sysusers where sysobjects.name like 'ms_bi%'
and sysusers.uid=sysobjects.uid
and sysobjects.type='u'

OPEN list_ms_bidi_tables

FETCH NEXT FROM list_ms_bidi_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping ms_bidi ' +@.name
select @.name='drop table ' + rtrim(@.name )
EXEC sp_executesql @.name
FETCH NEXT FROM list_ms_bidi_tables INTO @.name
END

CLOSE list_ms_bidi_tables
DEALLOCATE list_ms_bidi_tables

GO

Declare @.name nvarchar(129)
DECLARE list_rowguid_columns CURSOR FOR
select sysusers.name+'.'+object_name(syscolumns.id) from syscolumns,
sysobjects,sysusers where syscolumns.name like 'rowguid' and
object_Name(sysobjects.id) not like 'msmerge%'
and sysobjects.id=syscolumns.id
and sysusers.uid=sysobjects.uid
and sysobjects.type='u' order by 1

OPEN list_rowguid_columns

FETCH NEXT FROM list_rowguid_columns INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid columns ' +@.name
select @.name='Alter Table ' + rtrim(@.name ) + ' drop column rowguid'
print @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_columns INTO @.name
END

CLOSE list_rowguid_columns
DEALLOCATE list_rowguid_columns
go

Declare @.name nvarchar(129)
DECLARE list_views CURSOR FOR

select name From sysobjects where type ='v' and status =-1073741824 and
name
<>'sysmergeextendedarticlesview'

OPEN list_views

FETCH NEXT FROM list_views INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping replication views ' +@.name
select @.name='drop view ' + rtrim(@.name )
print @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_views INTO @.name
END

CLOSE list_views
DEALLOCATE list_views
go
Declare @.name nvarchar(129)
DECLARE list_procs CURSOR FOR

select name From sysobjects where type ='p' and status = -536870912

OPEN list_procs

FETCH NEXT FROM list_procs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping replication procedure ' +@.name
select @.name='drop procedure ' + rtrim(@.name )
print @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_procs INTO @.name
END

CLOSE list_procs
DEALLOCATE list_procs

go

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergepublications]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergepublications
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergesubscriptions]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergesubscriptions
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[syssubscriptions]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM syssubscriptions
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysarticleupdates]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysarticleupdates
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[systranschemas]') and OBJECTPROPERTY(id,
N'IsUserTable')
= 1)
DELETE FROM systranschemas
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergearticles]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergearticles
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergeschemaarticles]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergeschemaarticles
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergesubscriptions]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergesubscriptions
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysarticles]') and OBJECTPROPERTY(id,
N'IsUserTable') =
1)
DELETE FROM sysarticles
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysschemaarticles]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysschemaarticles
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[syspublications]') and OBJECTPROPERTY(id,
N'IsUserTable')
= 1)
DELETE FROM syspublications
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergeschemachange]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergeschemachange
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysmergesubsetfilters]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM sysmergesubsetfilters
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSdynamicsnapshotjobs]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSdynamicsnapshotjobs
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSdynamicsnapshotviews]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSdynamicsnapshotviews
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_altsyncpartners]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_altsyncpartners
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_contents]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_contents
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_delete_conflicts]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_delete_conflicts
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_errorlineage]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_errorlineage
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_genhistory]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_genhistory
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_replinfo]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_replinfo
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSmerge_tombstone]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSmerge_tombstone
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSpub_identity_range]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSpub_identity_range
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSrepl_identity_range]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSrepl_identity_range
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSreplication_subscriptions]') and
OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSreplication_subscriptions
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[MSsubscription_agents]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
DELETE FROM MSsubscription_agents
GO

if not exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[syssubscriptions]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
create table syssubscriptions (artid int, srvid smallint, dest_db
sysname,
status tinyint, sync_type tinyint, login_name sysname,
subscription_type
int, distribution_jobid binary, timestamp timestamp,update_mode
tinyint,
loopback_detection tinyint, queued_reinit bit)

CREATE TABLE [dbo].[syspublications] (
[description] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[name] [sysname] NOT NULL ,
[pubid] [int] IDENTITY (1, 1) NOT NULL ,
[repl_freq] [tinyint] NOT NULL ,
[status] [tinyint] NOT NULL ,
[sync_method] [tinyint] NOT NULL ,
[snapshot_jobid] [binary] (16) NULL ,
[independent_agent] [bit] NOT NULL ,
[immediate_sync] [bit] NOT NULL ,
[enabled_for_internet] [bit] NOT NULL ,
[allow_push] [bit] NOT NULL ,
[allow_pull] [bit] NOT NULL ,
[allow_anonymous] [bit] NOT NULL ,
[immediate_sync_ready] [bit] NOT NULL ,
[allow_sync_tran] [bit] NOT NULL ,
[autogen_sync_procs] [bit] NOT NULL ,
[retention] [int] NULL ,
[allow_queued_tran] [bit] NOT NULL ,
[snapshot_in_defaultfolder] [bit] NOT NULL ,
[alt_snapshot_folder] [nvarchar] (255) COLLATE
SQL_Latin1_General_CP1_CI_AS
NULL ,
[pre_snapshot_script] [nvarchar] (255) COLLATE
SQL_Latin1_General_CP1_CI_AS
NULL ,
[post_snapshot_script] [nvarchar] (255) COLLATE
SQL_Latin1_General_CP1_CI_AS
NULL ,
[compress_snapshot] [bit] NOT NULL ,
[ftp_address] [sysname] NULL ,
[ftp_port] [int] NOT NULL ,
[ftp_subdirectory] [nvarchar] (255) COLLATE
SQL_Latin1_General_CP1_CI_AS
NULL ,
[ftp_login] [sysname] NULL ,
[ftp_password] [nvarchar] (524) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[allow_dts] [bit] NOT NULL ,
[allow_subscription_copy] [bit] NOT NULL ,
[centralized_conflicts] [bit] NULL ,
[conflict_retention] [int] NULL ,
[conflict_policy] [int] NULL ,
[queue_type] [int] NULL ,
[ad_guidname] [sysname] NULL ,
[backward_comp_level] [int] NOT NULL
) ON [PRIMARY]
GO
create view sysextendedarticlesview
as
SELECT *
FROM sysarticles
UNION ALL
SELECT artid, NULL, creation_script, NULL, description,
dest_object,
NULL, NULL, NULL, name, objid, pubid, pre_creation_cmd, status, NULL,
type,
NULL,
schema_option, dest_owner
FROM sysschemaarticles
go

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysarticles]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[sysarticles]
GO

CREATE TABLE [dbo].[sysarticles] (
[artid] [int] IDENTITY (1, 1) NOT NULL ,
[columns] [varbinary] (32) NULL ,
[creation_script] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL
,
[del_cmd] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[description] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[dest_table] [sysname] NOT NULL ,
[filter] [int] NOT NULL ,
[filter_clause] [ntext] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ins_cmd] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[name] [sysname] NOT NULL ,
[objid] [int] NOT NULL ,
[pubid] [int] NOT NULL ,
[pre_creation_cmd] [tinyint] NOT NULL ,
[status] [tinyint] NOT NULL ,
[sync_objid] [int] NOT NULL ,
[type] [tinyint] NOT NULL ,
[upd_cmd] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[schema_option] [binary] (8) NULL ,
[dest_owner] [sysname] NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO

if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[sysschemaarticles]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[sysschemaarticles]
GO

CREATE TABLE [dbo].[sysschemaarticles] (
[artid] [int] NOT NULL ,
[creation_script] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL
,
[description] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[dest_object] [sysname] NOT NULL ,
[name] [sysname] NOT NULL ,
[objid] [int] NOT NULL ,
[pubid] [int] NOT NULL ,
[pre_creation_cmd] [tinyint] NOT NULL ,
[status] [int] NOT NULL ,
[type] [tinyint] NOT NULL ,
[schema_option] [binary] (8) NULL ,
[dest_owner] [sysname] NULL
) ON [PRIMARY]
GO

declare @.dbname varchar(130)
select @.dbname ='sp_replicationdboption
'+char(39)+db_name()+char(39)+',''merge publish'',''false'''
exec (@.dbname)
select @.dbname ='sp_replicationdboption
'+char(39)+db_name()+char(39)+',''publish'',''fals e'''
exec (@.dbname)

reconfigure with override
go

select db_name()
</code>

Can any one please help me as this is a production machine and needs
fixing ASAP.

Regards,

BenBenzine (bfausti@.gmail.com) writes:

Quote:

Originally Posted by

I recently ran a procedure in Query Analyzer from the Master db to
clear out all replication information so I could start/recreate it
again.
>
After I ran this procedure Enterprise Manager no longer showed the
registered server in the tree. When I tried to re-register it gave me
the following message:
>
"A connection could not be established to ([Database Name])"
>
"Reason: [SQL-DMO]Sql Server ([Database Name]) must be upgraded to
version 7.0 or later to be administered by this version of SQL-DMO"
>
"Please verify that sql is running and check your SQL server
registration properties (by right click on the ([Database Name]) node)
and try again."
>...
Can any one please help me as this is a production machine and needs
fixing ASAP.

OK, so you've learnt a lesson for the next time: run in test before you
run in production.

You run a script that performs a lot of updates to the system tables,
and in many cases to undocumented columns, and now you wonder why your
server is hosed?

I can't tell if there were was more that was harmful, but this cursor
definitely was:

SELECT name FROM sysobjects WHERE type='P' and (name like 'sp_ins_%'
or name like 'sp_MSdel_%' or name like 'sp_MSins_%'or
name like 'sp_MSupd_%' or name like 'sp_sel_%' or name like 'sp_upd_%')

OPEN list_procs

FETCH NEXT FROM list_procs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping procs ' +@.name
select @.name='drop procedure ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_procs INTO @.name
END

The SELECT hits 30 system procedures on my server, and far from all
are related to replication, for instance sp_updatestats and
sp_updateextendedproperty.

I would recommand that you at first possible maintenance window, detach
all databases and use the rebuildm tool to rebuild the master database.
Or simply reinstall SQL Server. Whatever, don't forget to reapply the
service pack.

If it's difficult to find the time for a reinstall, I suggest that you
open a case with Microsoft. I don't really want to guide you which
scripts to run, as my guidance could be wrong.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thank you for your reply.

Unfortunately I didn't have the luxury of a test environment, so I
took a big risk I know. Thankfully we had backups running on Veritas, I
restored to a previous version of the master and msdb databases and
this fixed my problem.

Erland Sommarskog wrote:

Quote:

Originally Posted by

Benzine (bfausti@.gmail.com) writes:

Quote:

Originally Posted by

I recently ran a procedure in Query Analyzer from the Master db to
clear out all replication information so I could start/recreate it
again.

After I ran this procedure Enterprise Manager no longer showed the
registered server in the tree. When I tried to re-register it gave me
the following message:

"A connection could not be established to ([Database Name])"

"Reason: [SQL-DMO]Sql Server ([Database Name]) must be upgraded to
version 7.0 or later to be administered by this version of SQL-DMO"

"Please verify that sql is running and check your SQL server
registration properties (by right click on the ([Database Name]) node)
and try again."
...
Can any one please help me as this is a production machine and needs
fixing ASAP.

>
OK, so you've learnt a lesson for the next time: run in test before you
run in production.
>
You run a script that performs a lot of updates to the system tables,
and in many cases to undocumented columns, and now you wonder why your
server is hosed?
>
I can't tell if there were was more that was harmful, but this cursor
definitely was:
>
SELECT name FROM sysobjects WHERE type='P' and (name like 'sp_ins_%'
or name like 'sp_MSdel_%' or name like 'sp_MSins_%'or
name like 'sp_MSupd_%' or name like 'sp_sel_%' or name like 'sp_upd_%')
>
OPEN list_procs
>
FETCH NEXT FROM list_procs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping procs ' +@.name
select @.name='drop procedure ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_procs INTO @.name
END
>
The SELECT hits 30 system procedures on my server, and far from all
are related to replication, for instance sp_updatestats and
sp_updateextendedproperty.
>
I would recommand that you at first possible maintenance window, detach
all databases and use the rebuildm tool to rebuild the master database.
Or simply reinstall SQL Server. Whatever, don't forget to reapply the
service pack.
>
If it's difficult to find the time for a reinstall, I suggest that you
open a case with Microsoft. I don't really want to guide you which
scripts to run, as my guidance could be wrong.
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Enterprise Manager reporting wrong OS memory (SQL 2000 SP4+)

I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The SQL Server instance is at SP4 with the
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
EdEd
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
name minimum maximum config_value run_value
awe enabled 0 1 1 1
max server memory (MB) 4 2147483647 6144 6144
min server memory (MB) 0 2147483647 0 0
"Uri Dimant" wrote:
> Ed
> Did you set up MAX Memory?
>|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:
> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
>> Where exactly are you seeing this 4GB? What does sp_configure show for
>> the
>> MAX Memory?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Hi Andrew,
Results from xp_msver:
Index Name Internal_Value Character_Value
1 ProductName Microsoft SQL Server
2 ProductVersion 524288 8.00.2187
3 Language 1033 English (United States)
4 Platform NT INTEL X86
5 Comments NT INTEL X86
6 CompanyName Microsoft Corporation
7 FileDescription SQL Server Windows NT
8 FileVersion 2000.080.2187.00
9 InternalName SQLSERVR
10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename SQLSERVR.EXE
13 PrivateBuild
14 SpecialBuild 143327232
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 4 4
17 ProcessorActiveMask 15 0000000f
18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
19 PhysicalMemory 3839 3839 (4025999360)
20 Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:
> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> > In Enterprise Manager, right-click on the instance.
> > On the General tab, the OS Memory: line shows 3839(MB)
> > The Memory tab shows range of 0 to 3839 MB.
> > in sp_configure, max server memory (MB) is 6144
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Where exactly are you seeing this 4GB? What does sp_configure show for
> >> the
> >> MAX Memory?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
>|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
>> It sounds like either the hotfix did not succeed or you applied the wrong
>> one. If you run xp_msver do you see the proper version for that hotfix?
>> Is
>> this Enterprise Edition of SQL Server? This was on a cluster. Did the
>> hotfix get applied to both nodes?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed" <Ed@.discussions.microsoft.com> wrote in message
>> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>> > In Enterprise Manager, right-click on the instance.
>> > On the General tab, the OS Memory: line shows 3839(MB)
>> > The Memory tab shows range of 0 to 3839 MB.
>> > in sp_configure, max server memory (MB) is 6144
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Where exactly are you seeing this 4GB? What does sp_configure show
>> >> for
>> >> the
>> >> MAX Memory?
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>>|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:
> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:
>> OK well you actually have the Cumulative Update not just the hotfix but
>> it
>> still should contain it as far as I know. What do the perfmon counters
>> for
>> SQL Memory Target and Total memory show? If they show the 6GB then it
>> sounds like a bug in the gui. You may need to contact PSS if perfmon or
>> DBCC MEMORYSTATUS are not showing the right amount.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Right. I've pretty much come to the same conclusion.
Thanks for the help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||The problem has been solved. It turns out that we had to stop and restart
the cluster in order for SQL Server to see the extra memory. We had to wait
until Friday night to do it.
When we added the memory, we failed over the SQL Server service, took the
machine down, added the memory and brought the machine back up again. The
cluster was never stopped.
Thanks again for your help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors

Enterprise Manager reporting wrong OS memory (SQL 2000 SP4+)

I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The SQL Server instance is at SP4 with the
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
Ed
Ed
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed
|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
nameminimummaximumconfig_valuerun_value
awe enabled0111
max server memory (MB)4214748364761446144
min server memory (MB)0214748364700
"Uri Dimant" wrote:

> Ed
> Did you set up MAX Memory?
>
|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed
|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:

> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...[vbcol=seagreen]
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
|||Hi Andrew,
Results from xp_msver:
IndexNameInternal_ValueCharacter_Value
1ProductNameMicrosoft SQL Server
2ProductVersion5242888.00.2187
3Language1033English (United States)
4PlatformNT INTEL X86
5CommentsNT INTEL X86
6CompanyNameMicrosoft Corporation
7FileDescriptionSQL Server Windows NT
8FileVersion2000.080.2187.00
9InternalNameSQLSERVR
10LegalCopyright? 1988-2004 Microsoft Corp. All rights reserved.
11LegalTrademarksMicrosoft? is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12OriginalFilenameSQLSERVR.EXE
13PrivateBuild
14SpecialBuild143327232
15WindowsVersion2483819575.2 (3790)
16ProcessorCount44
17ProcessorActiveMask150000000f
18ProcessorType586PROCESSOR_INTEL_PENTIUM
19PhysicalMemory38393839 (4025999360)
20Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:

> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>
|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...[vbcol=seagreen]
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright ? 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft? is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:

> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...[vbcol=seagreen]
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:

enterprise manager loading DB

Hello
I have a problem with a loading DB in Enterprise Manager.
I had restored a DB from another Sql Server and something seems wrong. I´ve
got no error message but I have a grey DB Icon with my DB Name and a loading
behind the name. I can´t delete the DB with Enterprise manager, can´t open
the properties nothing.
I have tried in Sql Query analyzer to drop the database, but I´ve got an
error that the db can´t be deleted because an use for replication exist.
On the Sql Server where I have restored the DB is no replication configured
only on the sql server where the backup was made.
Any idea how to remove the DB?
(Sql Server 2000 sp3)
Thx
BjörnPerhaps the restore was done using NORECOVERY option? Try:
RESTORE DATABASE dbname WITH RECOVERY
That would make the database accessible. Then drop the database, possibly removing replication
config first if needed (Google for details...).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Björn" <prodevelop@.gmx.net> wrote in message news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...
> Hello
> I have a problem with a loading DB in Enterprise Manager.
> I had restored a DB from another Sql Server and something seems wrong. I´ve
> got no error message but I have a grey DB Icon with my DB Name and a loading
> behind the name. I can´t delete the DB with Enterprise manager, can´t open
> the properties nothing.
> I have tried in Sql Query analyzer to drop the database, but I´ve got an
> error that the db can´t be deleted because an use for replication exist.
> On the Sql Server where I have restored the DB is no replication configured
> only on the sql server where the backup was made.
> Any idea how to remove the DB?
> (Sql Server 2000 sp3)
> Thx
> Björn
>|||Hi,
Add on to Tibor; You could also try
RESTORE LOG dbname WITH RECOVERY
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
> Perhaps the restore was done using NORECOVERY option? Try:
> RESTORE DATABASE dbname WITH RECOVERY
> That would make the database accessible. Then drop the database, possibly
> removing replication config first if needed (Google for details...).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Björn" <prodevelop@.gmx.net> wrote in message
> news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...
>> Hello
>> I have a problem with a loading DB in Enterprise Manager.
>> I had restored a DB from another Sql Server and something seems wrong.
>> I´ve
>> got no error message but I have a grey DB Icon with my DB Name and a
>> loading
>> behind the name. I can´t delete the DB with Enterprise manager, can´t
>> open
>> the properties nothing.
>> I have tried in Sql Query analyzer to drop the database, but I´ve got an
>> error that the db can´t be deleted because an use for replication exist.
>> On the Sql Server where I have restored the DB is no replication
>> configured
>> only on the sql server where the backup was made.
>> Any idea how to remove the DB?
>> (Sql Server 2000 sp3)
>> Thx
>> Björn
>>
>|||Hi
Thx for your answer
Now the DB is deleted:)
regards
Björn
"Hari Prasad" <hari_prasad_k@.hotmail.com> schrieb im Newsbeitrag
news:#tECW2wyGHA.3568@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Add on to Tibor; You could also try
> RESTORE LOG dbname WITH RECOVERY
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
> > Perhaps the restore was done using NORECOVERY option? Try:
> >
> > RESTORE DATABASE dbname WITH RECOVERY
> >
> > That would make the database accessible. Then drop the database,
possibly
> > removing replication config first if needed (Google for details...).
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Björn" <prodevelop@.gmx.net> wrote in message
> > news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...
> >> Hello
> >>
> >> I have a problem with a loading DB in Enterprise Manager.
> >> I had restored a DB from another Sql Server and something seems wrong.
> >> I´ve
> >> got no error message but I have a grey DB Icon with my DB Name and a
> >> loading
> >> behind the name. I can´t delete the DB with Enterprise manager, can´t
> >> open
> >> the properties nothing.
> >> I have tried in Sql Query analyzer to drop the database, but I´ve got
an
> >> error that the db can´t be deleted because an use for replication
exist.
> >> On the Sql Server where I have restored the DB is no replication
> >> configured
> >> only on the sql server where the backup was made.
> >> Any idea how to remove the DB?
> >> (Sql Server 2000 sp3)
> >>
> >> Thx
> >>
> >> Björn
> >>
> >>
> >
>

enterprise manager loading DB

Hello
I have a problem with a loading DB in Enterprise Manager.
I had restored a DB from another Sql Server and something seems wrong. Ive
got no error message but I have a grey DB Icon with my DB Name and a loading
behind the name. I cant delete the DB with Enterprise manager, cant open
the properties nothing.
I have tried in Sql Query analyzer to drop the database, but Ive got an
error that the db cant be deleted because an use for replication exist.
On the Sql Server where I have restored the DB is no replication configured
only on the sql server where the backup was made.
Any idea how to remove the DB?
(Sql Server 2000 sp3)
Thx
BjrnPerhaps the restore was done using NORECOVERY option? Try:
RESTORE DATABASE dbname WITH RECOVERY
That would make the database accessible. Then drop the database, possibly re
moving replication
config first if needed (Google for details...).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bjrn" <prodevelop@.gmx.net> wrote in message news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...[
vbcol=seagreen]
> Hello
> I have a problem with a loading DB in Enterprise Manager.
> I had restored a DB from another Sql Server and something seems wrong. Iv
e
> got no error message but I have a grey DB Icon with my DB Name and a loadi
ng
> behind the name. I cant delete the DB with Enterprise manager, cant open
> the properties nothing.
> I have tried in Sql Query analyzer to drop the database, but Ive got an
> error that the db cant be deleted because an use for replication exist.
> On the Sql Server where I have restored the DB is no replication configure
d
> only on the sql server where the backup was made.
> Any idea how to remove the DB?
> (Sql Server 2000 sp3)
> Thx
> Bjrn
>[/vbcol]|||Hi,
Add on to Tibor; You could also try
RESTORE LOG dbname WITH RECOVERY
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
> Perhaps the restore was done using NORECOVERY option? Try:
> RESTORE DATABASE dbname WITH RECOVERY
> That would make the database accessible. Then drop the database, possibly
> removing replication config first if needed (Google for details...).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Bjrn" <prodevelop@.gmx.net> wrote in message
> news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...
>|||Hi
Thx for your answer
Now the DB is deleted
regards
Bjrn
"Hari Prasad" <hari_prasad_k@.hotmail.com> schrieb im Newsbeitrag
news:#tECW2wyGHA.3568@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Add on to Tibor; You could also try
> RESTORE LOG dbname WITH RECOVERY
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
possibly[vbcol=seagreen]
an[vbcol=seagreen]
exist.[vbcol=seagreen]
>