Showing posts with label query. Show all posts
Showing posts with label query. Show all posts

Monday, March 26, 2012

EnterpriseManager/SQL Query Analysier (Authentication)

We have a sql 2005 server mirror set that we need to connect to.

I am in one active directory domain (eg DomainA) and the sql 2005 mirror is in another (eg DomainB).

We are not allowed (by the sql 2005 server provider) to put a trust between the two active directory domains and if we use a sql server login then if the mirror fails over then we will lose access since the master does not get mirrored.

Is there a way of logining in to the sql server 2005 mirror in DomainB with out logging my whole machine into DomainB or is there a way to mirror the sql users between the two sql 2005 mirror servers.

Any help would be grreatly apperiated

Hi,

Stored credentials can be found navigating to the to the Control Panel > User Accounts > Choose the User > manage you network accounts. You might have a fixed stored credential enetered there ?

HTH, Jens K. Suessmeyer.


http://www.sqlserver2005.de

Thursday, March 22, 2012

Enterprise Manager/Query Analyser hangs

Hi, hope somebody can help - we have found a strange problem at one of our
clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
when they click the + on Databases on Enterprise manager, it hangs and also
hangs the server (applications accessing the DB timeout). We found that user
sa did not have access to any DBs! -- which we restored with sp_changedbowner
- but still hangs! Query analyser also hangs when opening object browser. All
other actions also very slow. Have also checked and switched off autoclose on
all DBs.
Could not yet determine how and exactly when this happened.
Any advice appreciated.
Alice van Rensburg
>. We found that user
> sa did not have access to any DBs! --
sa is a sysadmin and has acceess by default to all databases
Is it poosible another actvities on the server?
"Alice" <Alice@.discussions.microsoft.com> wrote in message
news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> Hi, hope somebody can help - we have found a strange problem at one of our
> clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> when they click the + on Databases on Enterprise manager, it hangs and
> also
> hangs the server (applications accessing the DB timeout). We found that
> user
> sa did not have access to any DBs! -- which we restored with
> sp_changedbowner
> - but still hangs! Query analyser also hangs when opening object browser.
> All
> other actions also very slow. Have also checked and switched off autoclose
> on
> all DBs.
> Could not yet determine how and exactly when this happened.
> Any advice appreciated.
> Alice van Rensburg
>
|||Thanx for your reply - the interesting thing is that user sa did have access
to all DBs when we last checked (in December) - something must have happened
to change that, but we do not know what. Have checked - nothing else running
on the SQL server. We are seriously considering uninstall and reinstall.
"Uri Dimant" wrote:

> sa is a sysadmin and has acceess by default to all databases
> Is it poosible another actvities on the server?
>
> "Alice" <Alice@.discussions.microsoft.com> wrote in message
> news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
>
>
|||Managed to resolve this issue - seems like one of the dbs still had a
non-existing Windows NT user as dbowner. We detached all DBs, and reattached
them one by one, each time checking the owner and checking if DataBases
folder opens.
Regards
A
"Alice" wrote:
[vbcol=seagreen]
> Thanx for your reply - the interesting thing is that user sa did have access
> to all DBs when we last checked (in December) - something must have happened
> to change that, but we do not know what. Have checked - nothing else running
> on the SQL server. We are seriously considering uninstall and reinstall.
> "Uri Dimant" wrote:

Enterprise Manager/Query Analyser hangs

Hi, hope somebody can help - we have found a strange problem at one of our
clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
when they click the + on Databases on Enterprise manager, it hangs and also
hangs the server (applications accessing the DB timeout). We found that user
sa did not have access to any DBs! -- which we restored with sp_changedbowner
- but still hangs! Query analyser also hangs when opening object browser. All
other actions also very slow. Have also checked and switched off autoclose on
all DBs.
Could not yet determine how and exactly when this happened.
Any advice appreciated.
Alice van Rensburg>. We found that user
> sa did not have access to any DBs! --
sa is a sysadmin and has acceess by default to all databases
Is it poosible another actvities on the server?
"Alice" <Alice@.discussions.microsoft.com> wrote in message
news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> Hi, hope somebody can help - we have found a strange problem at one of our
> clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> when they click the + on Databases on Enterprise manager, it hangs and
> also
> hangs the server (applications accessing the DB timeout). We found that
> user
> sa did not have access to any DBs! -- which we restored with
> sp_changedbowner
> - but still hangs! Query analyser also hangs when opening object browser.
> All
> other actions also very slow. Have also checked and switched off autoclose
> on
> all DBs.
> Could not yet determine how and exactly when this happened.
> Any advice appreciated.
> Alice van Rensburg
>|||Thanx for your reply - the interesting thing is that user sa did have access
to all DBs when we last checked (in December) - something must have happened
to change that, but we do not know what. Have checked - nothing else running
on the SQL server. We are seriously considering uninstall and reinstall.
"Uri Dimant" wrote:
> >. We found that user
> > sa did not have access to any DBs! --
> sa is a sysadmin and has acceess by default to all databases
> Is it poosible another actvities on the server?
>
> "Alice" <Alice@.discussions.microsoft.com> wrote in message
> news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> > Hi, hope somebody can help - we have found a strange problem at one of our
> > clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> > when they click the + on Databases on Enterprise manager, it hangs and
> > also
> > hangs the server (applications accessing the DB timeout). We found that
> > user
> > sa did not have access to any DBs! -- which we restored with
> > sp_changedbowner
> > - but still hangs! Query analyser also hangs when opening object browser.
> > All
> > other actions also very slow. Have also checked and switched off autoclose
> > on
> > all DBs.
> > Could not yet determine how and exactly when this happened.
> > Any advice appreciated.
> > Alice van Rensburg
> >
>
>|||Managed to resolve this issue - seems like one of the dbs still had a
non-existing Windows NT user as dbowner. We detached all DBs, and reattached
them one by one, each time checking the owner and checking if DataBases
folder opens.
Regards
A
"Alice" wrote:
> Thanx for your reply - the interesting thing is that user sa did have access
> to all DBs when we last checked (in December) - something must have happened
> to change that, but we do not know what. Have checked - nothing else running
> on the SQL server. We are seriously considering uninstall and reinstall.
> "Uri Dimant" wrote:
> > >. We found that user
> > > sa did not have access to any DBs! --
> >
> > sa is a sysadmin and has acceess by default to all databases
> >
> > Is it poosible another actvities on the server?
> >
> >
> >
> > "Alice" <Alice@.discussions.microsoft.com> wrote in message
> > news:B476EE93-18CB-4DCE-8D24-A80EE1062587@.microsoft.com...
> > > Hi, hope somebody can help - we have found a strange problem at one of our
> > > clients (they run SQL srv 2000 with SP4 on Windows Server 2000 with SP3) -
> > > when they click the + on Databases on Enterprise manager, it hangs and
> > > also
> > > hangs the server (applications accessing the DB timeout). We found that
> > > user
> > > sa did not have access to any DBs! -- which we restored with
> > > sp_changedbowner
> > > - but still hangs! Query analyser also hangs when opening object browser.
> > > All
> > > other actions also very slow. Have also checked and switched off autoclose
> > > on
> > > all DBs.
> > > Could not yet determine how and exactly when this happened.
> > > Any advice appreciated.
> > > Alice van Rensburg
> > >
> >
> >
> >

Wednesday, March 21, 2012

Enterprise Manager Tools SQL2000

I have a new laptop with xp pro. Where are the client tools for SQL2000?
I need Query Anzlyser and Enterprise Mgr.

Thanks,
MikeHi Mike,

The SQL Server client tools are part of the SQL Server installation and come with the SQL Server CD.

See the following KB article: (see section: To Install Client Tools Only for SQL Server 2000)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303747

This is not included as part of Windows XP Professional.

Regards,
Vikram

Monday, March 19, 2012

Enterprise Manager results timeout

Hi -
Often when working on a query or viewing a table in Enterprise Manager, I ge
t messages such as "There has been no recent activity in the results pane" a
nd threatening to clear it. Is there any way to get rid of these messages? I
'm capable of determining w
hen too many resources are in use on the server without the help of these me
ssages.
Thanks,
JimNo...other than using Query Analyzer instead.
The behavior is by design. The following article applies to
SQL Server 2000 as well:
PRB: Table Designer Automatically Clears Results Pane When
Idle
http://support.microsoft.com/?id=252434
-Sue
On Wed, 10 Mar 2004 08:46:23 -0800, "Jim S"
<anonymous@.discussions.microsoft.com> wrote:

>Hi -
>Often when working on a query or viewing a table in Enterprise Manager, I get messa
ges such as "There has been no recent activity in the results pane" and threatening
to clear it. Is there any way to get rid of these messages? I'm capable of determini
ng
when too many resources are in use on the server without the help of these messages.darkred">
>Thanks,
>Jim|||Hi Jim.
We share in your frustration. Have you come up with any solutions yet?
-Dan
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...

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 Query Tool

We have noticed some random failures to write data to some
of our databases. In the
research that I have done I think it is being caused by
users querying the tables
with Enterprise Manager's Query Tool. I am seeing table
level locks that are granted
against the table in Mode IS. I am interpreting this to
mean that there is an 'Shared
Intent' Lock on that table. Which to my understanding
means that anyone can continue
to read but that I have also declared an intent to update
the table and therefore
requests for exclusive locks for update, insert or delete
operations would block
until my intent lock is removed. If the block occurs for
too long the blocked call
would then timeout. I believe that Enterprise Manager is
creating this type of lock
because the user interface allows the data that is
displayed to be updated and if the
Intent lock was not declared then data syncronization
issues would occur.
For now I have instructed people who access the tables to
use Query Analyzer since it
will only lock when queries that require the lock are
executed and will not hold the
lock while the user browses the results.
My questions are as follows:
1) Is my interpretation of the IS Mode Table lock correct?
2) Is there a way to prevent Enterprise Manager from
locking the table in this way
(i.e. make the query results read-only)?
3) If the user that is performing the query only has
dbreader privledges then why is
the Intent lock being created?
Thanxshttp://vyaskn.tripod.com/sql_enterp...er_or_t-sql.htm
"" <anonymous@.discussions.microsoft.com> wrote in message
news:535b01c4003c$1ec4aca0$a301280a@.phx.gbl...
> We have noticed some random failures to write data to some
> of our databases. In the
> research that I have done I think it is being caused by
> users querying the tables
> with Enterprise Manager's Query Tool. I am seeing table
> level locks that are granted
> against the table in Mode IS. I am interpreting this to
> mean that there is an 'Shared
> Intent' Lock on that table. Which to my understanding
> means that anyone can continue
> to read but that I have also declared an intent to update
> the table and therefore
> requests for exclusive locks for update, insert or delete
> operations would block
> until my intent lock is removed. If the block occurs for
> too long the blocked call
> would then timeout. I believe that Enterprise Manager is
> creating this type of lock
> because the user interface allows the data that is
> displayed to be updated and if the
> Intent lock was not declared then data syncronization
> issues would occur.
> For now I have instructed people who access the tables to
> use Query Analyzer since it
> will only lock when queries that require the lock are
> executed and will not hold the
> lock while the user browses the results.
> My questions are as follows:
> 1) Is my interpretation of the IS Mode Table lock correct?
> 2) Is there a way to prevent Enterprise Manager from
> locking the table in this way
> (i.e. make the query results read-only)?
> 3) If the user that is performing the query only has
> dbreader privledges then why is
> the Intent lock being created?
> Thanxs

Enterprise Manager Query Tool

We have noticed some random failures to write data to some
of our databases. In the
research that I have done I think it is being caused by
users querying the tables
with Enterprise Manager's Query Tool. I am seeing table
level locks that are granted
against the table in Mode IS. I am interpreting this to
mean that there is an 'Shared
Intent' Lock on that table. Which to my understanding
means that anyone can continue
to read but that I have also declared an intent to update
the table and therefore
requests for exclusive locks for update, insert or delete
operations would block
until my intent lock is removed. If the block occurs for
too long the blocked call
would then timeout. I believe that Enterprise Manager is
creating this type of lock
because the user interface allows the data that is
displayed to be updated and if the
Intent lock was not declared then data syncronization
issues would occur.
For now I have instructed people who access the tables to
use Query Analyzer since it
will only lock when queries that require the lock are
executed and will not hold the
lock while the user browses the results.
My questions are as follows:
1) Is my interpretation of the IS Mode Table lock correct?
2) Is there a way to prevent Enterprise Manager from
locking the table in this way
(i.e. make the query results read-only)?
3) If the user that is performing the query only has
dbreader privledges then why is
the Intent lock being created?
Thanxshttp://vyaskn.tripod.com/sql_enterprise_manager_or_t-sql.htm
":)" <anonymous@.discussions.microsoft.com> wrote in message
news:535b01c4003c$1ec4aca0$a301280a@.phx.gbl...
> We have noticed some random failures to write data to some
> of our databases. In the
> research that I have done I think it is being caused by
> users querying the tables
> with Enterprise Manager's Query Tool. I am seeing table
> level locks that are granted
> against the table in Mode IS. I am interpreting this to
> mean that there is an 'Shared
> Intent' Lock on that table. Which to my understanding
> means that anyone can continue
> to read but that I have also declared an intent to update
> the table and therefore
> requests for exclusive locks for update, insert or delete
> operations would block
> until my intent lock is removed. If the block occurs for
> too long the blocked call
> would then timeout. I believe that Enterprise Manager is
> creating this type of lock
> because the user interface allows the data that is
> displayed to be updated and if the
> Intent lock was not declared then data syncronization
> issues would occur.
> For now I have instructed people who access the tables to
> use Query Analyzer since it
> will only lock when queries that require the lock are
> executed and will not hold the
> lock while the user browses the results.
> My questions are as follows:
> 1) Is my interpretation of the IS Mode Table lock correct?
> 2) Is there a way to prevent Enterprise Manager from
> locking the table in this way
> (i.e. make the query results read-only)?
> 3) If the user that is performing the query only has
> dbreader privledges then why is
> the Intent lock being created?
> Thanxs

Enterprise manager query timeout

When I check the server's query timeout on the Server properties /
Connections tab in enterprise manager, it is set to 600 seconds.
Yet when I run a complicated query, it times out after 40 seconds.
The same query takes about a minute in OSQL, and succeeds there.
Is there an additional time-out that EM imposes, and can it be changed?
"Lucvdv" <replace_name@.null.net> wrote in message
news:kpjgh1lgjsqe3boeredlvn7iu5ipr3dp2k@.4ax.com...
> When I check the server's query timeout on the Server properties /
> Connections tab in enterprise manager, it is set to 600 seconds.
> Yet when I run a complicated query, it times out after 40 seconds.
> The same query takes about a minute in OSQL, and succeeds there.
> Is there an additional time-out that EM imposes, and can it be
> changed?
I believe this is a known issue. You should use Query Analyzer for all
your querying rather than going through SQL EM. This problem may have
been addressed in the recent SQL Server service pack (not sure). What SP
are you running on the client?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||On Fri, 2 Sep 2005 10:34:38 -0400, "David Gugick"
<david.gugick-nospam@.quest.com> wrote:

> "Lucvdv" <replace_name@.null.net> wrote in message
> news:kpjgh1lgjsqe3boeredlvn7iu5ipr3dp2k@.4ax.com...
> I believe this is a known issue. You should use Query Analyzer for all
> your querying rather than going through SQL EM. This problem may have
> been addressed in the recent SQL Server service pack (not sure). What SP
> are you running on the client?
Still SP3 on server and client.
I haven't downloaded SP4 yet because it looked like the changes are mostly
intended for 64 bit systems, I decided to wait until I get it through MSDN.
I'll take your advice and use Query Analyzer.
|||First of all the query time-out setting on the connections tab is only
for remote server queries. From what I understand your running a local
query.
The problem is that EM as a client application has it's own timeout
configuration setting which I admit is rather short. Query Analyzer on
the other hand by default waits as long as it needs, so you won't get
any timeout.
M
|||On 5 Sep 2005 01:03:31 -0700, m.bohse@.quest-consultants.com wrote:

> First of all the query time-out setting on the connections tab is only
> for remote server queries. From what I understand your running a local
> query.
> The problem is that EM as a client application has it's own timeout
> configuration setting which I admit is rather short. Query Analyzer on
> the other hand by default waits as long as it needs, so you won't get
> any timeout.
I found the setting, Tools -> Options -> Advanced -> Connection settings,
the default is 0 = infinite (says online help).
Trying to override it (I set it to 600 seconds) makes no difference.
I upgraded to SP4, and it's still the same

Sunday, March 11, 2012

Enterprise manager problem

hi, i've just installed sql server2000 on my home pc, im using to connect to
a sql server at my work. My query analyser works fine, but enterprise manger
seems to freeze and ultimatly not respond when i try to open the data base
folder, I downloaded that latsest server packs, but evey time i rry to run
them I get a PackageForTheWeb error.
My home computer is using xp pro
im new comer to sql server, so if u have any suggestions please give like ur
explaining to a complete novice.
Thanks guysTry adjusting your connection parameters -- try SQL Server authentication
credentials or Windows credentials. I would say go into SQL Client Network
utility, but I don't know what more that would offer when Query Analyzer
connects.
The one other thing to check is your version of ADO (look at properties for
c:\program files\common files\system\msado\msado15.dll). If it is less than
2.6 or 2.7, you might want to go to http://www.microsoft.com/ado and
grabbing the MDAC 2.8 release.
****************************************
*********
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.noreply.yahoo.com
Please remove "noreply" before replying.
This posting is provided "as is" with
no warranties and confers no rights.
****************************************
*********
"airwalker" <airwalker@.discussions.microsoft.com> wrote in message
news:1BB646CB-0EB7-4B70-9AC7-59538924B1E4@.microsoft.com...
> hi, i've just installed sql server2000 on my home pc, im using to connect
> to
> a sql server at my work. My query analyser works fine, but enterprise
> manger
> seems to freeze and ultimatly not respond when i try to open the data base
> folder, I downloaded that latsest server packs, but evey time i rry to run
> them I get a PackageForTheWeb error.
> My home computer is using xp pro
> im new comer to sql server, so if u have any suggestions please give like
> ur
> explaining to a complete novice.
> Thanks guys

Enterprise manager problem

hi, i've just installed sql server2000 on my home pc, im using to connect to
a sql server at my work. My query analyser works fine, but enterprise manger
seems to freeze and ultimatly not respond when i try to open the data base
folder, I downloaded that latsest server packs, but evey time i rry to run
them I get a PackageForTheWeb error.
My home computer is using xp pro
im new comer to sql server, so if u have any suggestions please give like ur
explaining to a complete novice.
Thanks guys
Try adjusting your connection parameters -- try SQL Server authentication
credentials or Windows credentials. I would say go into SQL Client Network
utility, but I don't know what more that would offer when Query Analyzer
connects.
The one other thing to check is your version of ADO (look at properties for
c:\program files\common files\system\msado\msado15.dll). If it is less than
2.6 or 2.7, you might want to go to http://www.microsoft.com/ado and
grabbing the MDAC 2.8 release.

*************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.noreply.yahoo.com
Please remove "noreply" before replying.
This posting is provided "as is" with
no warranties and confers no rights.
*************************************************
"airwalker" <airwalker@.discussions.microsoft.com> wrote in message
news:1BB646CB-0EB7-4B70-9AC7-59538924B1E4@.microsoft.com...
> hi, i've just installed sql server2000 on my home pc, im using to connect
> to
> a sql server at my work. My query analyser works fine, but enterprise
> manger
> seems to freeze and ultimatly not respond when i try to open the data base
> folder, I downloaded that latsest server packs, but evey time i rry to run
> them I get a PackageForTheWeb error.
> My home computer is using xp pro
> im new comer to sql server, so if u have any suggestions please give like
> ur
> explaining to a complete novice.
> Thanks guys

Wednesday, March 7, 2012

Enterprise Manager field > 900 chars not displaying post SP4

I think this started happening post SP4.
I have an nvarchar(4000) field. If I query the table in Enterprise Manager,
the data for the field only displays in rows where the value is 900 chars or
less. Otherwise, the field looks empty, but when I click in it and type, I
get a popup that says "Cannot edit this field."
I can query the data, so I know it's there, but it's annoying not to see it
in the results.
Has anyone else noticed this?
<Cliff>
Enterprise Manager is not meant to be a data editor. May I suggest that you
use Query Analyzer (and Transact-SQL statements to edit the data)? The
other option is to create a GUI that you can use to edit the data within
your databases.
Keith
"Cliff Morrison" <CliffMorrison@.discussions.microsoft.com> wrote in message
news:3C026C09-A968-466A-B1D0-FAE7EC4EACE5@.microsoft.com...
>I think this started happening post SP4.
> I have an nvarchar(4000) field. If I query the table in Enterprise
> Manager,
> the data for the field only displays in rows where the value is 900 chars
> or
> less. Otherwise, the field looks empty, but when I click in it and type,
> I
> get a popup that says "Cannot edit this field."
> I can query the data, so I know it's there, but it's annoying not to see
> it
> in the results.
> Has anyone else noticed this?
> <Cliff>
|||I'm not really trying to edit. The only reason I did in my example was to
show that something strange was happening with the field.
I do think I should be able to visually verify in Enterprise Manager query
results that data is in a field, regardless of whether that data is less than
or equal to 900 characters in length.
<Cliff>
"Keith Kratochvil" wrote:

> Enterprise Manager is not meant to be a data editor. May I suggest that you
> use Query Analyzer (and Transact-SQL statements to edit the data)? The
> other option is to create a GUI that you can use to edit the data within
> your databases.
> --
> Keith
|||I am having the same problem, except it is happening with text fields and a
char(1024) field. Shorter fields and a varchar(4096) field seem to show up
just fine. EM used to display the data in these fields before I upgraded to
SP4. What is going on?
Rob
"Cliff Morrison" wrote:

> I'm not really trying to edit. The only reason I did in my example was to
> show that something strange was happening with the field.
> I do think I should be able to visually verify in Enterprise Manager query
> results that data is in a field, regardless of whether that data is less than
> or equal to 900 characters in length.
> <Cliff>
> "Keith Kratochvil" wrote:
>
|||Or check out AgileInfoSoftware DataStudio for editing data. You can directly
update table content, and there is no known limit for the length of
character.
John King
http://www.agileinfollc.com
"Rob Drollinger" <RobDrollinger@.discussions.microsoft.com> wrote in message
news:993820FF-C681-4E34-8344-BBC28C8CF008@.microsoft.com...[vbcol=seagreen]
>I am having the same problem, except it is happening with text fields and a
> char(1024) field. Shorter fields and a varchar(4096) field seem to show
> up
> just fine. EM used to display the data in these fields before I upgraded
> to
> SP4. What is going on?
> Rob
>
> "Cliff Morrison" wrote:

Friday, February 24, 2012

Enterprise Manager 'Change Query Type' Window

I'm running a SQL Server Enterprise Manager. When I click on 'Change Query
Type', a window pops up on the bottom right hand corner of my screen with the
options: 'Select, Insert from, Insert into, Update, etc.'. The window used
to appear right under the bottom, but now every time I click it, the window
shows up on the bottom right of the screen. Does anyone know how to change
this? I want it to appear closer to the button.
Thanks,
On Fri, 17 Mar 2006 05:16:31 -0800, PML wrote:

>I'm running a SQL Server Enterprise Manager. When I click on 'Change Query
>Type', a window pops up on the bottom right hand corner of my screen with the
>options: 'Select, Insert from, Insert into, Update, etc.'. The window used
>to appear right under the bottom, but now every time I click it, the window
>shows up on the bottom right of the screen. Does anyone know how to change
>this? I want it to appear closer to the button.
Hi PML,
Don't use Enterprise Manager to design your queries. This part of EM has
lots of bugs and other "funny" issues.
http://www.aspfaq.com/show.asp?id=2455
Hugo Kornelis, SQL Server MVP

Enterprise Manager Cannot Display Table Records or Run Query

I have a new installation of SQL Server 2000 Dev Edition on a Win2K3 Standard Edition Server that I used for development. I just set this machine up in th last week and installed all Win2K3 patches and then installed SQL2K and SP3a. I have a single named instance. I just noticed today that I cannot view table data or use the Query part of EM. When I right click a table and select Open Table->Return All Rows it gives me an error dialog "An unexpected error happened during this operation". While the EM is diplaying this dialog the EM screen looks like Internet Explorer and says "Action Canceled - You might not have permission to view this directory or page using the credentials you supplied." I believe that this is a EM issue as I cannot view table content on other remote server. ANy ideas? Might this be an IE security patch disallowing some connectivity ?

--Frank

--
Message posted via http://www.sqlmonster.com"Frank Rizzo via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:08f32b66479d4ddcbe5ab7a876ff377d@.SQLMonster.c om...
>I have a new installation of SQL Server 2000 Dev Edition on a Win2K3
>Standard Edition Server that I used for development. I just set this
>machine up in th last week and installed all Win2K3 patches and then
>installed SQL2K and SP3a. I have a single named instance. I just noticed
>today that I cannot view table data or use the Query part of EM. When I
>right click a table and select Open Table->Return All Rows it gives me an
>error dialog "An unexpected error happened during this operation". While
>the EM is diplaying this dialog the EM screen looks like Internet Explorer
>and says "Action Canceled - You might not have permission to view this
>directory or page using the credentials you supplied." I believe that this
>is a EM issue as I cannot view table content on other remote server. ANy
>ideas? Might this be an IE security patch disallowing some connectivity ?
> --Frank
> --
> Message posted via http://www.sqlmonster.com

A number of people seem to have had similar issues - if you Google the
newsgroups, you'll see that the usual response is to reinstall either the
MSSQL client tools (including SP3a) and/or the latest MDAC version.
Unfortunately, it doesn't always seem to solve the problem.

Simon

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
RonYou can try to reinstall the SQL Server service pack to start with...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
Ron
You can try to reinstall the SQL Server service pack to start with...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>
|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:

> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>

Enterprise Manager Behaviour for SQL 2000

Thanks in Advance,
I am seeing a strange behavior in the query interface on EM that is
new for me, and it has only occurred in a new environment. So I
believe that this is a configuration setting that one of you can point
out to me.
We I have multiple query windows open, if I turn my attention to
another task in remote desktop, the reminder that a query window has
not been in use for sometime pops up and asks if it can clear the
results. In this environment, that window somehow gets trapped behind
the query windows. This creates a catch 22. I cannot move the focus
to close any of the query windows to reveal the system message, and I
cannot get to the system message to allow me to move the focus.
Is there a configuration solution here?
Mark Simmerman
Napa, CADon't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
Analyzer.
In Enteprise Manager, you are maintaining an association with the source
table (so that you can treat SQL Server like Excel, and edit a "cell"), and
this causes resource drain no matter how long you let it sit there.
<xxxdbaxxx@.gmail.com> wrote in message
news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
> Thanks in Advance,
> I am seeing a strange behavior in the query interface on EM that is
> new for me, and it has only occurred in a new environment. So I
> believe that this is a configuration setting that one of you can point
> out to me.
> We I have multiple query windows open, if I turn my attention to
> another task in remote desktop, the reminder that a query window has
> not been in use for sometime pops up and asks if it can clear the
> results. In this environment, that window somehow gets trapped behind
> the query windows. This creates a catch 22. I cannot move the focus
> to close any of the query windows to reveal the system message, and I
> cannot get to the system message to allow me to move the focus.
> Is there a configuration solution here?
> Mark Simmerman
> Napa, CA
>|||On Jan 31, 10:52 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
> Analyzer.
> In Enteprise Manager, you are maintaining an association with the source
> table (so that you can treat SQL Server like Excel, and edit a "cell"), and
> this causes resource drain no matter how long you let it sit there.
> <xxxdba...@.gmail.com> wrote in message
> news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
>
> > Thanks in Advance,
> > I am seeing a strange behavior in the query interface on EM that is
> > new for me, and it has only occurred in a new environment. So I
> > believe that this is a configuration setting that one of you can point
> > out to me.
> > We I have multiple query windows open, if I turn my attention to
> > another task in remote desktop, the reminder that a query window has
> > not been in use for sometime pops up and asks if it can clear the
> > results. In this environment, that window somehow gets trapped behind
> > the query windows. This creates a catch 22. I cannot move the focus
> > to close any of the query windows to reveal the system message, and I
> > cannot get to the system message to allow me to move the focus.
> > Is there a configuration solution here?
> > Mark Simmerman
> > Napa, CA- Hide quoted text -
> - Show quoted text -
OK. Other than telling me to use another tool (in SQL 2005 they are
one and the same), is there any solution or configuration setting that
can address this?
Mark|||> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same),
Yes, but you still have different options, like Open Table (bad), and query
windows (good).
> is there any solution or configuration setting that
> can address this?
Not that I know of.|||xxxdbaxxx@.gmail.com wrote:
> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same), is there any solution or configuration setting that
> can address this?
> Mark
>
No, they're not really "one and the same". You can "open" tables using
a GUI, ala Enterprise Manager, or you can query them properly ala Query
Analyzer. The only difference in 2005 is that you don't "launch" two
seperate applications.
The limitations are the same - opening a table through the GUI is a
heavy process, prone to blocking. The GUI tools are acceptable for a
development environment, but should not be used against a production
system. Manipulating your tables properly, using T-SQL commands, is the
preferred method.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||On Feb 1, 7:34 am, Tracy McKibben <t...@.realsqlguy.com> wrote:
> xxxdba...@.gmail.com wrote:
> > OK. Other than telling me to use another tool (in SQL 2005 they are
> > one and the same), is there any solution or configuration setting that
> > can address this?
> > Mark
> No, they're not really "one and the same". You can "open" tables using
> a GUI, ala Enterprise Manager, or you can query them properly ala Query
> Analyzer. The only difference in 2005 is that you don't "launch" two
> seperate applications.
> The limitations are the same - opening a table through the GUI is a
> heavy process, prone to blocking. The GUI tools are acceptable for a
> development environment, but should not be used against a production
> system. Manipulating your tables properly, using T-SQL commands, is the
> preferred method.
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com
OK. I am in a development environment. I would still like to know if
anyone has an answer to the question. It is an annoying behavior on
the part of the GUI. Do you guys get points for non-responsive
responses?
Mark|||> OK. I am in a development environment. I would still like to know if
> anyone has an answer to the question. It is an annoying behavior on
> the part of the GUI. Do you guys get points for non-responsive
> responses?
We don't get "points" for anything. We are here, volunteering our time to
help other people solve problems we might have insight on. Every once in a
while, the recipients feigns appreciation.
If "not that I know of" is not responsive enough for you, then maybe you
know of a better place to get more responsive answers, and should try there.
<shrug><sigh><resisting smacking own forehead>

Enterprise Manager Behaviour for SQL 2000

Thanks in Advance,
I am seeing a strange behavior in the query interface on EM that is
new for me, and it has only occurred in a new environment. So I
believe that this is a configuration setting that one of you can point
out to me.
We I have multiple query windows open, if I turn my attention to
another task in remote desktop, the reminder that a query window has
not been in use for sometime pops up and asks if it can clear the
results. In this environment, that window somehow gets trapped behind
the query windows. This creates a catch 22. I cannot move the focus
to close any of the query windows to reveal the system message, and I
cannot get to the system message to allow me to move the focus.
Is there a configuration solution here?
Mark Simmerman
Napa, CA
Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
Analyzer.
In Enteprise Manager, you are maintaining an association with the source
table (so that you can treat SQL Server like Excel, and edit a "cell"), and
this causes resource drain no matter how long you let it sit there.
<xxxdbaxxx@.gmail.com> wrote in message
news:1170262471.222466.129540@.l53g2000cwa.googlegr oups.com...
> Thanks in Advance,
> I am seeing a strange behavior in the query interface on EM that is
> new for me, and it has only occurred in a new environment. So I
> believe that this is a configuration setting that one of you can point
> out to me.
> We I have multiple query windows open, if I turn my attention to
> another task in remote desktop, the reminder that a query window has
> not been in use for sometime pops up and asks if it can clear the
> results. In this environment, that window somehow gets trapped behind
> the query windows. This creates a catch 22. I cannot move the focus
> to close any of the query windows to reveal the system message, and I
> cannot get to the system message to allow me to move the focus.
> Is there a configuration solution here?
> Mark Simmerman
> Napa, CA
>
|||On Jan 31, 10:52 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
> Analyzer.
> In Enteprise Manager, you are maintaining an association with the source
> table (so that you can treat SQL Server like Excel, and edit a "cell"), and
> this causes resource drain no matter how long you let it sit there.
> <xxxdba...@.gmail.com> wrote in message
> news:1170262471.222466.129540@.l53g2000cwa.googlegr oups.com...
>
>
>
>
> - Show quoted text -
OK. Other than telling me to use another tool (in SQL 2005 they are
one and the same), is there any solution or configuration setting that
can address this?
Mark
|||> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same),
Yes, but you still have different options, like Open Table (bad), and query
windows (good).

> is there any solution or configuration setting that
> can address this?
Not that I know of.
|||xxxdbaxxx@.gmail.com wrote:
> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same), is there any solution or configuration setting that
> can address this?
> Mark
>
No, they're not really "one and the same". You can "open" tables using
a GUI, ala Enterprise Manager, or you can query them properly ala Query
Analyzer. The only difference in 2005 is that you don't "launch" two
seperate applications.
The limitations are the same - opening a table through the GUI is a
heavy process, prone to blocking. The GUI tools are acceptable for a
development environment, but should not be used against a production
system. Manipulating your tables properly, using T-SQL commands, is the
preferred method.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||On Feb 1, 7:34 am, Tracy McKibben <t...@.realsqlguy.com> wrote:
> xxxdba...@.gmail.com wrote:
>
> No, they're not really "one and the same". You can "open" tables using
> a GUI, ala Enterprise Manager, or you can query them properly ala Query
> Analyzer. The only difference in 2005 is that you don't "launch" two
> seperate applications.
> The limitations are the same - opening a table through the GUI is a
> heavy process, prone to blocking. The GUI tools are acceptable for a
> development environment, but should not be used against a production
> system. Manipulating your tables properly, using T-SQL commands, is the
> preferred method.
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com
OK. I am in a development environment. I would still like to know if
anyone has an answer to the question. It is an annoying behavior on
the part of the GUI. Do you guys get points for non-responsive
responses?
Mark
|||> OK. I am in a development environment. I would still like to know if
> anyone has an answer to the question. It is an annoying behavior on
> the part of the GUI. Do you guys get points for non-responsive
> responses?
We don't get "points" for anything. We are here, volunteering our time to
help other people solve problems we might have insight on. Every once in a
while, the recipients feigns appreciation.
If "not that I know of" is not responsive enough for you, then maybe you
know of a better place to get more responsive answers, and should try there.
<shrug><sigh><resisting smacking own forehead>

Enterprise Manager Behaviour for SQL 2000

Thanks in Advance,
I am seeing a strange behavior in the query interface on EM that is
new for me, and it has only occurred in a new environment. So I
believe that this is a configuration setting that one of you can point
out to me.
We I have multiple query windows open, if I turn my attention to
another task in remote desktop, the reminder that a query window has
not been in use for sometime pops up and asks if it can clear the
results. In this environment, that window somehow gets trapped behind
the query windows. This creates a catch 22. I cannot move the focus
to close any of the query windows to reveal the system message, and I
cannot get to the system message to allow me to move the focus.
Is there a configuration solution here?
Mark Simmerman
Napa, CADon't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
Analyzer.
In Enteprise Manager, you are maintaining an association with the source
table (so that you can treat SQL Server like Excel, and edit a "cell"), and
this causes resource drain no matter how long you let it sit there.
<xxxdbaxxx@.gmail.com> wrote in message
news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
> Thanks in Advance,
> I am seeing a strange behavior in the query interface on EM that is
> new for me, and it has only occurred in a new environment. So I
> believe that this is a configuration setting that one of you can point
> out to me.
> We I have multiple query windows open, if I turn my attention to
> another task in remote desktop, the reminder that a query window has
> not been in use for sometime pops up and asks if it can clear the
> results. In this environment, that window somehow gets trapped behind
> the query windows. This creates a catch 22. I cannot move the focus
> to close any of the query windows to reveal the system message, and I
> cannot get to the system message to allow me to move the focus.
> Is there a configuration solution here?
> Mark Simmerman
> Napa, CA
>|||On Jan 31, 10:52 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
> Analyzer.
> In Enteprise Manager, you are maintaining an association with the source
> table (so that you can treat SQL Server like Excel, and edit a "cell"), an
d
> this causes resource drain no matter how long you let it sit there.
> <xxxdba...@.gmail.com> wrote in message
> news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
>
>
>
>
>
>
> - Show quoted text -
OK. Other than telling me to use another tool (in SQL 2005 they are
one and the same), is there any solution or configuration setting that
can address this?
Mark|||> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same),
Yes, but you still have different options, like Open Table (bad), and query
windows (good).

> is there any solution or configuration setting that
> can address this?
Not that I know of.|||xxxdbaxxx@.gmail.com wrote:
> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same), is there any solution or configuration setting that
> can address this?
> Mark
>
No, they're not really "one and the same". You can "open" tables using
a GUI, ala Enterprise Manager, or you can query them properly ala Query
Analyzer. The only difference in 2005 is that you don't "launch" two
seperate applications.
The limitations are the same - opening a table through the GUI is a
heavy process, prone to blocking. The GUI tools are acceptable for a
development environment, but should not be used against a production
system. Manipulating your tables properly, using T-SQL commands, is the
preferred method.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||On Feb 1, 7:34 am, Tracy McKibben <t...@.realsqlguy.com> wrote:
> xxxdba...@.gmail.com wrote:
>
>
> No, they're not really "one and the same". You can "open" tables using
> a GUI, ala Enterprise Manager, or you can query them properly ala Query
> Analyzer. The only difference in 2005 is that you don't "launch" two
> seperate applications.
> The limitations are the same - opening a table through the GUI is a
> heavy process, prone to blocking. The GUI tools are acceptable for a
> development environment, but should not be used against a production
> system. Manipulating your tables properly, using T-SQL commands, is the
> preferred method.
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com
OK. I am in a development environment. I would still like to know if
anyone has an answer to the question. It is an annoying behavior on
the part of the GUI. Do you guys get points for non-responsive
responses?
Mark|||> OK. I am in a development environment. I would still like to know if
> anyone has an answer to the question. It is an annoying behavior on
> the part of the GUI. Do you guys get points for non-responsive
> responses?
We don't get "points" for anything. We are here, volunteering our time to
help other people solve problems we might have insight on. Every once in a
while, the recipients feigns appreciation.
If "not that I know of" is not responsive enough for you, then maybe you
know of a better place to get more responsive answers, and should try there.
<shrug><sigh><resisting smacking own forehead>

Enterprise Manager Availability

Is Enterprise Manager and Query Analyzer available as separate licenses? or
downloads?
Ritche M wrote:
> Is Enterprise Manager and Query Analyzer available as separate
> licenses? or downloads?
If you purchase a CAL using a client licensing model, that gives you the
rights to install the client tools. If you already have a processor
license, your users can install client tools. The client tools are
installed from the main SQL Server CD. There are no separate downloads
AFAIK. None of this applies if you don't own a SQL Server license. There
are some free and more capable retail tools out there to perform the
functions of SQL EM / QA.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||check out http://www.agileinfollc.com DataStudio, it has superior user
interface and functionalities for managing SQL Server and other databases.
John King
http://www.agileinfollc.com
"Ritche M" <Ritche M@.discussions.microsoft.com> wrote in message
news:F291C016-4266-446C-B2E8-B68ACCDA0C27@.microsoft.com...
> Is Enterprise Manager and Query Analyzer available as separate licenses?
> or
> downloads?