Do I need to reinstall analysis services after we upgraded sqlserv

Do I need to reinstall/upgrade analysis services after we upgraded sqlserver
from stanadard edition to enterprise edition? The developer tried to use
partition on analysis service and message from analysis manager showed that
it is not aware that our sqlserver has been upgraded to enterprise edition
already. "user-defined partitions are available only if you installed
analysis services on enterprise edition".
May be the problem is caused by the meta data repository? If we migrate the
repository to SQL server, the problem will be resolved?
"sabby" wrote:

> Do I need to reinstall/upgrade analysis services after we upgraded sqlserver
> from stanadard edition to enterprise edition? The developer tried to use
> partition on analysis service and message from analysis manager showed that
> it is not aware that our sqlserver has been upgraded to enterprise edition
> already. "user-defined partitions are available only if you installed
> analysis services on enterprise edition".

Do I need to reinstall analysis services after we upgraded sqlserv

Do I need to reinstall/upgrade analysis services after we upgraded sqlserver
from stanadard edition to enterprise edition? The developer tried to use
partition on analysis service and message from analysis manager showed that
it is not aware that our sqlserver has been upgraded to enterprise edition
already. "user-defined partitions are available only if you installed
analysis services on enterprise edition".May be the problem is caused by the meta data repository? If we migrate the
repository to SQL server, the problem will be resolved?
"sabby" wrote:

> Do I need to reinstall/upgrade analysis services after we upgraded sqlserv
er
> from stanadard edition to enterprise edition? The developer tried to use
> partition on analysis service and message from analysis manager showed tha
t
> it is not aware that our sqlserver has been upgraded to enterprise edition
> already. "user-defined partitions are available only if you installed
> analysis services on enterprise edition".

Do I need to reinstall analysis services after we upgraded sqlserv

Do I need to reinstall/upgrade analysis services after we upgraded sqlserver
from stanadard edition to enterprise edition? The developer tried to use
partition on analysis service and message from analysis manager showed that
it is not aware that our sqlserver has been upgraded to enterprise edition
already. "user-defined partitions are available only if you installed
analysis services on enterprise edition".May be the problem is caused by the meta data repository? If we migrate the
repository to SQL server, the problem will be resolved?
"sabby" wrote:
> Do I need to reinstall/upgrade analysis services after we upgraded sqlserver
> from stanadard edition to enterprise edition? The developer tried to use
> partition on analysis service and message from analysis manager showed that
> it is not aware that our sqlserver has been upgraded to enterprise edition
> already. "user-defined partitions are available only if you installed
> analysis services on enterprise edition".

Do I need to add users for window Authentication?

I am trying to wrap the Windows Authentication in my brain. If I use window
authentication, do I add user through enterprise manager under Security tab
and logins. I want my user on my asp.net to login and connect to sql server,
but I windows Authentication. I don't want to add every single user. I'm I
on the right track?
thanks
Nick
Nick wrote:
> I am trying to wrap the Windows Authentication in my brain. If I use
> window authentication, do I add user through enterprise manager under
> Security tab and logins. I want my user on my asp.net to login and
> connect to sql server, but I windows Authentication. I don't want
> to add every single user. I'm I on the right track?
> thanks
> Nick
You can add a Windows Group that contains all the users.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Do I need to add users for window Authentication?

I am trying to wrap the Windows Authentication in my brain. If I use window
authentication, do I add user through enterprise manager under Security tab
and logins. I want my user on my asp.net to login and connect to sql server
,
but I windows Authentication. I don't want to add every single user. I'm
I
on the right track?
thanks
NickNick wrote:
> I am trying to wrap the Windows Authentication in my brain. If I use
> window authentication, do I add user through enterprise manager under
> Security tab and logins. I want my user on my asp.net to login and
> connect to sql server, but I windows Authentication. I don't want
> to add every single user. I'm I on the right track?
> thanks
> Nick
You can add a Windows Group that contains all the users.
David Gugick
Quest Software
www.imceda.com
www.quest.comsql

Do I need to add users for window Authentication?

I am trying to wrap the Windows Authentication in my brain. If I use window
authentication, do I add user through enterprise manager under Security tab
and logins. I want my user on my asp.net to login and connect to sql server,
but I windows Authentication. I don't want to add every single user. I'm I
on the right track?
thanks
NickNick wrote:
> I am trying to wrap the Windows Authentication in my brain. If I use
> window authentication, do I add user through enterprise manager under
> Security tab and logins. I want my user on my asp.net to login and
> connect to sql server, but I windows Authentication. I don't want
> to add every single user. I'm I on the right track?
> thanks
> Nick
You can add a Windows Group that contains all the users.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com

Do I need Enterprise to do clustering?

I'm confused. Reading the SQL 2000 Resource Kit, it definitely says I need
Enterprise in order to do failover clustering. But reading the product
guide on the 2005 version says Standard has clustering capabilities. Is
this something new to 2005 or is it a different type of clustering? We're
looking at clustering and it's all new to me so I'd appreciate any help you
can give me. Thanks.
--Sandy
It is a different feature set for a different product SKU matrix. SQL 2000
requires Enterprise Edition for any clustering. SQL 2005 will allow
two-node clusters in Standard Edition. Both are MSCS failover clustering.
I have been recommending SQL 2005 Standard Edition for lower-cost clustering
with several of my clients. So far, all the systems have performed very
well.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sandy Proesch" <sproe@.spamcop.net> wrote in message
news:%23dNoaEFSGHA.5908@.TK2MSFTNGP14.phx.gbl...
> I'm confused. Reading the SQL 2000 Resource Kit, it definitely says I
> need Enterprise in order to do failover clustering. But reading the
> product guide on the 2005 version says Standard has clustering
> capabilities. Is this something new to 2005 or is it a different type of
> clustering? We're looking at clustering and it's all new to me so I'd
> appreciate any help you can give me. Thanks.
> --Sandy
>
|||Thank you, that is exactly what we're looking to do - a 2-node failover
cluster.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OeBsiWFSGHA.4440@.TK2MSFTNGP11.phx.gbl...
> It is a different feature set for a different product SKU matrix. SQL
> 2000 requires Enterprise Edition for any clustering. SQL 2005 will allow
> two-node clusters in Standard Edition. Both are MSCS failover clustering.
> I have been recommending SQL 2005 Standard Edition for lower-cost
> clustering with several of my clients. So far, all the systems have
> performed very well.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Sandy Proesch" <sproe@.spamcop.net> wrote in message
> news:%23dNoaEFSGHA.5908@.TK2MSFTNGP14.phx.gbl...
>
|||Make sure and check out the 64-bit and dual-core processors. No difference
in licensing costs to go with either or both, but you get a huge performance
boost.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sandy Proesch" <sproe@.spamcop.net> wrote in message
news:%23Fq7LwFSGHA.4900@.TK2MSFTNGP09.phx.gbl...
> Thank you, that is exactly what we're looking to do - a 2-node failover
> cluster.
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OeBsiWFSGHA.4440@.TK2MSFTNGP11.phx.gbl...
>
|||Geoff,
If you have to do an upgrade in place on a cluster from 2000 to 2005, can
you go from 2000 Enterprise to 2005 Standard without problems?
Thanks
Chris Wood
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Q8l%23OGSGHA.1204@.TK2MSFTNGP12.phx.gbl...
> Make sure and check out the 64-bit and dual-core processors. No
> difference in licensing costs to go with either or both, but you get a
> huge performance boost.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Sandy Proesch" <sproe@.spamcop.net> wrote in message
> news:%23Fq7LwFSGHA.4900@.TK2MSFTNGP09.phx.gbl...
>
|||You cannot do this as an in-place upgrade. You can install a second
instance of SQL 2005 on the same hardware and do a database migration. I
would take the opportunity to build a cluster based on new hardware if your
system is more than a few years old.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:e4yn1oeSGHA.5884@.TK2MSFTNGP14.phx.gbl...
> Geoff,
> If you have to do an upgrade in place on a cluster from 2000 to 2005, can
> you go from 2000 Enterprise to 2005 Standard without problems?
> Thanks
> Chris Wood
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23Q8l%23OGSGHA.1204@.TK2MSFTNGP12.phx.gbl...
>
|||Geoff,
But we could upgrade SQL2000 Enterprise to SQL2005 Enterprise in place could
we not?
Chris
Currently there is no plan to purchase new hardware for the clustered
production server.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23okTDKfSGHA.5808@.TK2MSFTNGP12.phx.gbl...
> You cannot do this as an in-place upgrade. You can install a second
> instance of SQL 2005 on the same hardware and do a database migration. I
> would take the opportunity to build a cluster based on new hardware if
> your system is more than a few years old.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:e4yn1oeSGHA.5884@.TK2MSFTNGP14.phx.gbl...
>
|||Now that I have tested (for giggles only) and it works, but I really hate
upgrades!! Especially for HA systems!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23MmSCyfSGHA.4600@.TK2MSFTNGP11.phx.gbl...
> Geoff,
> But we could upgrade SQL2000 Enterprise to SQL2005 Enterprise in place
> could we not?
> Chris
> Currently there is no plan to purchase new hardware for the clustered
> production server.
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23okTDKfSGHA.5808@.TK2MSFTNGP12.phx.gbl...
>
|||In theory, yes. In practice, I have heard of a lot of problems with the
in-place cluster upgrade wizard and would not recommend that path at this
time. Side-by-side or new platform is the safest way to go.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23MmSCyfSGHA.4600@.TK2MSFTNGP11.phx.gbl...
> Geoff,
> But we could upgrade SQL2000 Enterprise to SQL2005 Enterprise in place
> could we not?
> Chris
> Currently there is no plan to purchase new hardware for the clustered
> production server.
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23okTDKfSGHA.5808@.TK2MSFTNGP12.phx.gbl...
>
|||Thank you Geoff. Not really the sort of news I wanted to hear.
Chris
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23$b804fSGHA.4616@.TK2MSFTNGP10.phx.gbl...
> In theory, yes. In practice, I have heard of a lot of problems with the
> in-place cluster upgrade wizard and would not recommend that path at this
> time. Side-by-side or new platform is the safest way to go.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23MmSCyfSGHA.4600@.TK2MSFTNGP11.phx.gbl...
>

Do comments work in EM job?

I've created a job in Enterprise Manager under Management | Jobs. I double
click the particular job, select the Steps tab, then double click the step
name. In the command window are four stored procedures that I execute:
exec sp1
exec sp2
exec sp3
exec sp4
This works fine. If I comment out sp1
-- sp1
does this have any affect? I did comment out all four SPs and they seem to
keep running. I had to disable the job to keep them from running.
Must I disable/enable a job for the comments to take affect?
Thanks,
BrettNot sure about that Brett,
I'd script out the job without/with comments and see what effect that had.
have a look in the scripts
From what you say, it sounds as tho you can't put comments in EM... which
isn't that surprising.
"Brett" <no@.spam.com> wrote in message
news:%23aq%23FmjCFHA.3280@.TK2MSFTNGP14.phx.gbl...
> I've created a job in Enterprise Manager under Management | Jobs. I
> double click the particular job, select the Steps tab, then double click
> the step name. In the command window are four stored procedures that I
> execute:
> exec sp1
> exec sp2
> exec sp3
> exec sp4
> This works fine. If I comment out sp1
> -- sp1
> does this have any affect? I did comment out all four SPs and they seem
> to keep running. I had to disable the job to keep them from running.
> Must I disable/enable a job for the comments to take affect?
> Thanks,
> Brett
>

distributor_admin error

Hi,
When i try to configure publisher, distributor, subscriber on the same remote server, i am getting the following error:
SQL Server Enterprise Manager could not configure '90.168.XX.XXX' as the distributor for '90.168.xx.xxx'
Error: 18483: could not connect to server 'different name' beacuse 'distributor_admin' isn ot defined as a remote login at the server
I changed the MSSQLSERVER and the SQL Server Agent and a dependant file to run froma domain account, i gave that domain account all the privileges on the database and the master database aswell. but i keep getting the error.
Also why is the error showing diffetent server name than the '90.168...' name?
Will i have problems later if i donot set up alias names rather than ip address. If so, how can i set up alias names for SQL Server's
I am quite new to all this, any detailed answer could really help.
thanks
stummalaGot that fixed by re registering the server name to the result of @.@.SERVERNAME

Distributor (Server) Name Changed... No Replication Monitor what to do ?

Hi there,
We have changed the name of our SQL Server. Now the Replication Monitor is not appearing on the Enterprise Manager.
I tried to change the name of Distributor but there is no option. We have plenty of publications which are still showing old SQL Server instance name.
How we can change the name of Publisher without deleting all the publications ?
Any Help will be appreciated.
Abid Malik
the simplest way to fix this is to remove replication using the Tools -
Replication - Disable Publishing menu options and then to reinstall it.
"Abid Malik" <abidmunirmalik@.hotmail.com> wrote in message
news:69D97665-3983-4400-BE1A-028D9A1D5EAF@.microsoft.com...
> Hi there,
> We have changed the name of our SQL Server. Now the Replication Monitor is
not appearing on the Enterprise Manager.
> I tried to change the name of Distributor but there is no option. We have
plenty of publications which are still showing old SQL Server instance name.
> How we can change the name of Publisher without deleting all the
publications ?
> Any Help will be appreciated.
> Abid Malik

Distribution Agent Fails on Pull subscriptions

Environment:
SQLServer 2000 Enterprise w/SP3
Win 2000 Server w/SP3
In testing replication against a copy of our production database, when I run
the snapshot agent, it completes with success. When I then run the
distribution agent, I get the following error returned:
The name ' ' is not permitted in this context. Only constants, expressions,
or variables allowed here. Column names are not permitted.
(Source: STAGING2 (Data source); Error number: 128)
As near as I can tell, the script being processed when the error is
generated is:
================================================== ==
SET QUOTED_IDENTIFIER ON
GO
drop procedure [spBDCInsertAddressRecord]
GO
CREATE PROCEDURE [spBDCInsertAddressRecord] @.pAddress_id_out int OUT
AS
/************************************************** ************************************************** ******
INSERTS A BLANK ADDRESS RECORD AND RETURNS THE ADDRESS_ID VALUE
************************************************** ************************************************** *******/
INSERT INTO ADDRESS (LINE1) VALUES(" ")
SELECT @.pAddress_id_out = @.@.IDENTITY
RETURN 0
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
================================================== =
This is a Transactional replication and the subscription is a Pull
subscription. The address_id column is the primary key for the table and is
an automatically generated INT data type.
Any thoughts?
TIA,
Ken
Try using INSERT INTO ADDRESS (LINE1) VALUES(' ') -- ie single quotes
Rgds,
Paul Ibison
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:3C35C8AF-8CD0-44E7-898C-BBF2C0978F5E@.microsoft.com...
> Environment:
> SQLServer 2000 Enterprise w/SP3
> Win 2000 Server w/SP3
> In testing replication against a copy of our production database, when I
run
> the snapshot agent, it completes with success. When I then run the
> distribution agent, I get the following error returned:
> The name ' ' is not permitted in this context. Only constants,
expressions,
> or variables allowed here. Column names are not permitted.
> (Source: STAGING2 (Data source); Error number: 128)
> As near as I can tell, the script being processed when the error is
> generated is:
> ================================================== ==
> SET QUOTED_IDENTIFIER ON
> GO
> drop procedure [spBDCInsertAddressRecord]
> GO
> CREATE PROCEDURE [spBDCInsertAddressRecord] @.pAddress_id_out int OUT
> AS
>
/************************************************** *************************
*******************************
> INSERTS A BLANK ADDRESS RECORD AND RETURNS THE ADDRESS_ID VALUE
>
************************************************** **************************
*******************************/
> INSERT INTO ADDRESS (LINE1) VALUES(" ")
> SELECT @.pAddress_id_out = @.@.IDENTITY
> RETURN 0
> GO
> SET QUOTED_IDENTIFIER OFF
> GO
> SET ANSI_NULLS ON
> GO
> ================================================== =
> This is a Transactional replication and the subscription is a Pull
> subscription. The address_id column is the primary key for the table and
is
> an automatically generated INT data type.
> Any thoughts?
> TIA,
> Ken

Distributing Processing of SQL Server

Hi,
We have a SQL Server 2005 Enterprise database running on a HP ML 370
Server with 4 processors, which has a Windows .Net 2003 as OS. But at
a time process of Sql Server running on a single processor of the
server.
1. Has Sql Server 2005 this capability that could run on Multi
Processors? Could we obtain to this aim by configuring Sql Server? or
can we achieve it by configuring Operating System?
2. Our database grows so fast,that We suggest that we encounter with
response time delay problem after a while. Which Administration
technique (like Indexing, clustering, moving old data to a secondary
DB, ... ) is better for maintaining our database.
Thanks in advanced.
Regards
SajjadSQL Server uses multiple processors by default, though it gets into details
I don't know.
Check 2005 BOL for the following page:
(max degree of parallelism)
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/4445b385-5992-4d2d-bfd7-9e8ad869c5c9.htm
Also:
RECONFIGURE;
and
EXEC sp_configure;
"Sajjad" <spirahesh@.gmail.com> wrote in message
news:1192975398.771008.300920@.e34g2000pro.googlegroups.com...
> Hi,
> We have a SQL Server 2005 Enterprise database running on a HP ML 370
> Server with 4 processors, which has a Windows .Net 2003 as OS. But at
> a time process of Sql Server running on a single processor of the
> server.
> 1. Has Sql Server 2005 this capability that could run on Multi
> Processors? Could we obtain to this aim by configuring Sql Server? or
> can we achieve it by configuring Operating System?
> 2. Our database grows so fast,that We suggest that we encounter with
> response time delay problem after a while. Which Administration
> technique (like Indexing, clustering, moving old data to a secondary
> DB, ... ) is better for maintaining our database.
> Thanks in advanced.
> Regards
> Sajjad
>|||> 1. Has Sql Server 2005 this capability that could run on Multi
> Processors? Could we obtain to this aim by configuring Sql Server? or
> can we achieve it by configuring Operating System?
SQL Server 2005 Enterprise Edition will use all available available
processors by default. However, a single query will use multiple processors
only with a parallel query plan. Only some types of queries will benefit
form parallelism.
> 2. Our database grows so fast,that We suggest that we encounter with
> response time delay problem after a while. Which Administration
> technique (like Indexing, clustering, moving old data to a secondary
> DB, ... ) is better for maintaining our database.
Most performance gains come from database and application design, query
tuning and indexing. Clustering is mostly for availability. Moving old
data to another database isn't usually needed to improve performance because
appropriate indexes can provide good response time regardless of table size.
Large tables (many millions or billions or rows) tables can be difficult to
manage. Partitioning can improve manageability without needing to move old
data elsewhere.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Sajjad" <spirahesh@.gmail.com> wrote in message
news:1192975398.771008.300920@.e34g2000pro.googlegroups.com...
> Hi,
> We have a SQL Server 2005 Enterprise database running on a HP ML 370
> Server with 4 processors, which has a Windows .Net 2003 as OS. But at
> a time process of Sql Server running on a single processor of the
> server.
> 1. Has Sql Server 2005 this capability that could run on Multi
> Processors? Could we obtain to this aim by configuring Sql Server? or
> can we achieve it by configuring Operating System?
> 2. Our database grows so fast,that We suggest that we encounter with
> response time delay problem after a while. Which Administration
> technique (like Indexing, clustering, moving old data to a secondary
> DB, ... ) is better for maintaining our database.
> Thanks in advanced.
> Regards
> Sajjad
>

Distributing a Custom SQL Server Enterprise Manager MMC with Server Registrations

Is it possible to make available to several administrators a custom
SQL Server Enterprise Manager MMC containing 80 server registrations?
I would like to avoid having to manually recreate the console on
multiple machines. I tried distributing the .MSC file and exporting
and importing the following registry key, but only the group names
appeared in the MMC, not the servers:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\80\Tools\SQLEW\Registered Servers X]
Any suggestions?
Thanks,
Eric
It used to work! Check here for some vb and java scripts:
http://groups.google.com.au/groups?h...adm=PqyaNXwaEH
A.2900%40cpmsftngxa06.phx.gbl&rnum=4&prev=/groups%3Fq%3Denterprise%2Bman
ager%2Bregistry%2Bsql%2Bimport%26hl%3Den%26lr%3D%2 6ie%3DUTF-8
HTH,
g.
http://www.sqlskunkworks.com
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Thanks for the reply! At your suggestion, I found the following message
which contained an effective solution:
From: "Mingqing Cheng [MSFT]" (v-mingqc@.online.microsoft.com)
Subject: RE: Export/Import SQL EM Registrations?
View: Complete Thread (6 articles)
Original Format
Newsgroups: microsoft.public.sqlserver.tools
Date: 2004-07-16 00:25:54 PST
Hi TIA,
From your descriptions, I understood that you would like to export all
registered Server and then import them in a new machine. Have I
understood
you? If there is anything I misunderstood, please feel free to let me
know
Based on my scope, The method by exporting Register Files is not
supported
from SQL7 SP3 as encryption has been put in the process. Furtuantely, we
could do it by creating SQL-DMO
Here are the steps:
1. Create a vbs file and call it readreg.vbs which contains the
following.
Please substitute [servername] with SQL Server name and [password] with
the
SA password.
It also creates a table RegServers in pubs database so make sure that
this
does not exist. This script collects information about the currently
registered servers and stores the information in the RegServers table.
Dim oApplication
Dim oServerGroups
Dim oServerGroup
Dim oRegisteredServer
Dim oNewRegisteredServer
Dim oSQLServer
Dim MsgOutput
set oSQLServer = CreateObject("SQLDMO.SQLServer")
Set oApplication = CreateObject("SQLDMO.Application")
Set oServerGroups = oApplication.ServerGroups
oSQLServer.Connect "servername", "sa", "password"
oSQLServer.ExecuteImmediate "Create table pubs..RegServers(ServerName
varchar(30),
SLogin varchar(30), SPassword varchar(30), IsNtAuth varchar(2))"
For Each oServerGroup in oApplication.ServerGroups
For Each oRegisteredServer in oServerGroup.RegisteredServers
MsgOutput = "Insert Into Pubs..RegServers values("
MsgOutput = MsgOutput + "'" + oRegisteredServer.Name + "', '" +
oRegisteredServer.Login + "', '" + oRegisteredServer.Password + "', '" +
CStr(oRegisteredServer.UseTrustedConnection) + "')"
oSQLServer.ExecuteImmediate MsgOutput
Next
Next
oSQLServer.Disconnect
msgbox "complete"
2. To run, open a command-prompt and run "cscript readreg.vbs".
3. To verify that the information was retrieved correctly, go to the
SQL
Server
specified in the script and run the following:
use pubs
select * from RegServers
4. Create another vbs file and call it createreg.vbs which contains the
following:
Again substitute [servername] with SQL Server name and [password] with
the
sa
password.
Dim oApplication
Dim oServerGroups
Dim oServerGroup
Dim oRegisteredServer
Dim oNewRegisteredServer
Dim oSQLServer
Dim oQueryResults
Dim MsgOutput
Dim num
Dim SrvNameOutput
Dim LoginOutput
Dim PassOutput
Dim AuthOutput
Dim GetLoginOutput
set oSQLServer = CreateObject("SQLDMO.SQLServer")
Set oApplication = CreateObject("SQLDMO.Application")
Set oServerGroups = oApplication.ServerGroups
oSQLServer.Connect "servername" , "sa", "password"
set oQueryResults = oSQLServer.ExecuteWithResults ("Select ServerName,
SLogin,
SPassword, IsNtAuth from pubs..RegServers")
For num = 1 To oQueryResults.Rows
SrvNameOutput = oQueryResults.GetColumnString(num, 1)
LoginOutput = oQueryResults.GetColumnString(num, 2)
PassOutput = oQueryResults.GetColumnString(num, 3)
AuthOutput = oQueryResults.GetColumnString(num, 4)
If LoginOutput = "" Then
LoginOutput = " "
End if
Set oNewRegisteredServer = CreateObject("SQLDMO.RegisteredServer")
oNewRegisteredServer.Login = LoginOutput
oNewRegisteredServer.Name = SrvNameOutput
oNewRegisteredServer.Password = PassOutput
oNewRegisteredServer.UseTrustedConnection = CLng(AuthOutput)
oServerGroups("SQL Server
Group").RegisteredServers.Add(oNewRegisteredServer )
Next
Msgbox "complete"
5. To run, open a command-prompt and run "cscript createreg.vbs".
NOTE:
a. When doing the tests, please make sure that Enterprise Manager is
closed.
b. The script gathers information about the registered servers for the
currently
logged on user.
c. If you want to test on a single machine, you may do the following:
- run readreg.vbs
- Delete the registration from Enterprise Manager or delete the entries
in
the
following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\80\Tools\SQLEW\Registered
Servers X
Please test the method and I strongly recommand you doing this in a
development machine first
Thank you for your patience and cooperation. If you have any questions
or
concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Distributing a Custom SQL Server Enterprise Manager MMC with Server Registrations

Is it possible to make available to several administrators a custom
SQL Server Enterprise Manager MMC containing 80 server registrations?
I would like to avoid having to manually recreate the console on
multiple machines. I tried distributing the .MSC file and exporting
and importing the following registry key, but only the group names
appeared in the MMC, not the servers:
& #91;HKEY_CURRENT_USER\Software\Microsoft
\Microsoft SQL
Server\80\Tools\SQLEW\Registered Servers X]
Any suggestions?
Thanks,
EricIt used to work! Check here for some vb and Java scripts:
http://groups.google.com.au/groups?...eadm=PqyaNXwaEH
A.2900%40cpmsftngxa06.phx.gbl&rnum=4&prev=/groups%3Fq%3Denterprise%2Bman
ager%2Bregistry%2Bsql%2Bimport%26hl%3Den
%26lr%3D%26ie%3DUTF-8
HTH,
g.
http://www.sqlskunkworks.com
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Thanks for the reply! At your suggestion, I found the following message
which contained an effective solution:
From: "Mingqing Cheng [MSFT]" (v-mingqc@.online.microsoft.com)
Subject: RE: Export/Import SQL EM Registrations?
View: Complete Thread (6 articles)
Original Format
Newsgroups: microsoft.public.sqlserver.tools
Date: 2004-07-16 00:25:54 PST
Hi TIA,
From your descriptions, I understood that you would like to export all
registered Server and then import them in a new machine. Have I
understood
you? If there is anything I misunderstood, please feel free to let me
know
Based on my scope, The method by exporting Register Files is not
supported
from SQL7 SP3 as encryption has been put in the process. Furtuantely, we
could do it by creating SQL-DMO
Here are the steps:
1. Create a vbs file and call it readreg.vbs which contains the
following.
Please substitute [servername] with SQL Server name and [password] w
ith
the
SA password.
It also creates a table RegServers in pubs database so make sure that
this
does not exist. This script collects information about the currently
registered servers and stores the information in the RegServers table.
Dim oApplication
Dim oServerGroups
Dim oServerGroup
Dim oRegisteredServer
Dim oNewRegisteredServer
Dim oSQLServer
Dim MsgOutput
set oSQLServer = CreateObject("SQLDMO.SQLServer")
Set oApplication = CreateObject("SQLDMO.Application")
Set oServerGroups = oApplication.ServerGroups
oSQLServer.Connect "servername", "sa", "password"
oSQLServer.ExecuteImmediate "Create table pubs..RegServers(ServerName
varchar(30),
SLogin varchar(30), SPassword varchar(30), IsNtAuth varchar(2))"
For Each oServerGroup in oApplication.ServerGroups
For Each oRegisteredServer in oServerGroup.RegisteredServers
MsgOutput = "Insert Into Pubs..RegServers values("
MsgOutput = MsgOutput + "'" + oRegisteredServer.Name + "', '" +
oRegisteredServer.Login + "', '" + oRegisteredServer.Password + "', '" +
CStr(oRegisteredServer.UseTrustedConnection) + "')"
oSQLServer.ExecuteImmediate MsgOutput
Next
Next
oSQLServer.Disconnect
msgbox "complete"
2. To run, open a command-prompt and run "cscript readreg.vbs".
3. To verify that the information was retrieved correctly, go to the
SQL
Server
specified in the script and run the following:
use pubs
select * from RegServers
4. Create another vbs file and call it createreg.vbs which contains the
following:
Again substitute [servername] with SQL Server name and [password] wi
th
the
sa
password.
Dim oApplication
Dim oServerGroups
Dim oServerGroup
Dim oRegisteredServer
Dim oNewRegisteredServer
Dim oSQLServer
Dim oQueryResults
Dim MsgOutput
Dim num
Dim SrvNameOutput
Dim LoginOutput
Dim PassOutput
Dim AuthOutput
Dim GetLoginOutput
set oSQLServer = CreateObject("SQLDMO.SQLServer")
Set oApplication = CreateObject("SQLDMO.Application")
Set oServerGroups = oApplication.ServerGroups
oSQLServer.Connect "servername" , "sa", "password"
set oQueryResults = oSQLServer.ExecuteWithResults ("Select ServerName,
SLogin,
SPassword, IsNtAuth from pubs..RegServers")
For num = 1 To oQueryResults.Rows
SrvNameOutput = oQueryResults.GetColumnString(num, 1)
LoginOutput = oQueryResults.GetColumnString(num, 2)
PassOutput = oQueryResults.GetColumnString(num, 3)
AuthOutput = oQueryResults.GetColumnString(num, 4)
If LoginOutput = "" Then
LoginOutput = " "
End if
Set oNewRegisteredServer = CreateObject("SQLDMO.RegisteredServer")
oNewRegisteredServer.Login = LoginOutput
oNewRegisteredServer.Name = SrvNameOutput
oNewRegisteredServer.Password = PassOutput
oNewRegisteredServer.UseTrustedConnection = CLng(AuthOutput)
oServerGroups("SQL Server
Group").RegisteredServers.Add(oNewRegisteredServer)
Next
Msgbox "complete"
5. To run, open a command-prompt and run "cscript createreg.vbs".
NOTE:
a. When doing the tests, please make sure that Enterprise Manager is
closed.
b. The script gathers information about the registered servers for the
currently
logged on user.
c. If you want to test on a single machine, you may do the following:
- run readreg.vbs
- Delete the registration from Enterprise Manager or delete the entries
in
the
following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Mic
rosoft SQL
Server\80\Tools\SQLEW\Registered
Servers X
Please test the method and I strongly recommand you doing this in a
development machine first
Thank you for your patience and cooperation. If you have any questions
or
concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Distributing a Custom SQL Server Enterprise Manager MMC with Server Registrations

Is it possible to make available to several administrators a custom
SQL Server Enterprise Manager MMC containing 80 server registrations?
I would like to avoid having to manually recreate the console on
multiple machines. I tried distributing the .MSC file and exporting
and importing the following registry key, but only the group names
appeared in the MMC, not the servers:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\80\Tools\SQLEW\Registered Servers X]
Any suggestions?
Thanks,
EricIt used to work! Check here for some vb and java scripts:
http://groups.google.com.au/groups?hl=en&lr=&ie=UTF-8&threadm=PqyaNXwaEH
A.2900%40cpmsftngxa06.phx.gbl&rnum=4&prev=/groups%3Fq%3Denterprise%2Bman
ager%2Bregistry%2Bsql%2Bimport%26hl%3Den%26lr%3D%26ie%3DUTF-8
HTH,
g.
http://www.sqlskunkworks.com
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Distributed transaction with clustering server

I can't perform a distributed transaction between a remote
server to the central server.
I have 3 sql server 2000 enterprise edition. 2 of them are
installed on win2K server (LOCAL1, LOCAL2) and the other
(CENTRAL_SQL) is installed on clustering win2K server.
None of them is in domain.
Linked servers are defined well between them and I can
perform select statement from any server to any other
server.
I can also perform a distributed transaction between the
remote servers, from LOCAL1 to LOCAL2 and contrarily:
set xact_abort on
begin distributed tran
select count(*) from
LOCAL1.tempdb.INFORMATION_SCHEMA.TABLES
commit
set xact_abort off
MSDTC service starts up with local system account or other
administrators belonging account.
I can also ping the local servers from the central and
even manage them using the Active Directory.
When I perform a distributed transaction between a remote
server (LOCAL1 or LOCAL2) and the central server I get an
error:
Server: Msg 7391, Level 16, State 1, Line 5
The operation could not be performed because the OLE DB
provider 'SQLOLEDB' was unable to begin a distributed
transaction.
[OLE/DB provider returned message: New transaction cannot
enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
What am I doing wrong?
Thanks,
Yuval Peleg
DBA, Nice SystemsLook for the following entry in the SQL Server errorlog:
Attempting to initialize Distributed Transaction Coordinator.
Is there an error after it?
If so, have you run comclust on both nodes of the cluster to make MSDTC
cluster aware?
I not run it on both nodes and then take SQL Server off line and back on
line. Then try your query.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||There is a masage before it:
"Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owne
r
Blocks."
I run comclust on both nodes.
Thanks,
Yuval Peleg
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Distributed transaction with clustering server

I can't perform a distributed transaction between a remote
server to the central server.
I have 3 sql server 2000 enterprise edition. 2 of them are
installed on win2K server (LOCAL1, LOCAL2) and the other
(CENTRAL_SQL) is installed on clustering win2K server.
None of them is in domain.
Linked servers are defined well between them and I can
perform select statement from any server to any other
server.
I can also perform a distributed transaction between the
remote servers, from LOCAL1 to LOCAL2 and contrarily:
set xact_abort on
begin distributed tran
select count(*) from
LOCAL1.tempdb.INFORMATION_SCHEMA.TABLES
commit
set xact_abort off
MSDTC service starts up with local system account or other
administrators belonging account.
I can also ping the local servers from the central and
even manage them using the Active Directory.
When I perform a distributed transaction between a remote
server (LOCAL1 or LOCAL2) and the central server I get an
error:
Server: Msg 7391, Level 16, State 1, Line 5
The operation could not be performed because the OLE DB
provider 'SQLOLEDB' was unable to begin a distributed
transaction.
[OLE/DB provider returned message: New transaction cannot
enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
What am I doing wrong?
Thanks,
Yuval Peleg
DBA, Nice Systems
Look for the following entry in the SQL Server errorlog:
Attempting to initialize Distributed Transaction Coordinator.
Is there an error after it?
If so, have you run comclust on both nodes of the cluster to make MSDTC
cluster aware?
I not run it on both nodes and then take SQL Server off line and back on
line. Then try your query.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||There is a masage before it:
"Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner
Blocks."
I run comclust on both nodes.
Thanks,
Yuval Peleg
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!