Changing config table location on the fly

Hi everyone,

I am trying to create a proof of concept to show that we can have packages deployed on 3 different servers and all we need to do is tell the package, upon execution/scheduled task, where to go fetch it's configurations from.

The configurations are using SQL Server as the package configuration. This makes it easier for DBA's to maintain since DBA's are responsible for package executions and job scheduling.

For example, the configuration database and all package configurations would be found on server1, server2 and server3 The difference in values is that on Server1, the configuration for the source data and the destination data point to Server1\DatabaseSource and Server1\DatabaseDestination and on server2, the configs point the source to Server2\DatabaseSource and Server2\DatabaseDestination and for server 3, the same thing but pointing to server3.

There is also a connection for the SSIS_Config database we're getting the configurations from. In theory, if we specify a different server where this SSIS_Config database is found, it should override the settings in the package. No?

When I schedule OR execute the package, it's always getting it's configs from the config specified in the package independent of wether I specify it in the Connection Managers of the Execute Package Utility when I manually execute it OR in the data sources tab when I configure the package to be run as a job in SQL Server 2005.

Am I missing something here?

Thanks,

Rob

You use an XML file to set the "config database" location dynamically. You can't use a SQL Server based config table to control where the "config database" resides because that is what you're trying to change.

So, use an XML file, place it on all of the servers, each pointing to the correct "config database" for that environment.|||

Rob,

it sounds like you want to decide, at execution-time, which set of configurations it should use. Right?

So, in essence you need a way of "parameterising" your package so it needs which set of configurations to use. Right?

The best way to do this is to use the /SET option of dtexec.exe

Regards

Jamie

|||

Thats the one!

Thank you Jamie

|||

Jamie,

I've tried using the /SET option but I can't get it to change the set of configurations to use.

This is the command line options I've used, did I miss something?

/FILE "D:\Documents and Settings\forestr\Desktop\Deployment Test\Deployment Test\bin\Deployment\Package.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI /SET "\Package.Connections[b-ncrsql1.SSIS_CONFIG].Properties[ConnectionString]";"Data Source=b-ncrsql1\test;Initial Catalog=SSIS_CONFIG;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;"

|||

Jamie,

I've tried using the /SET option but I can't get it to change the set of configurations to use.

This is the command line options I've used, did I miss something?

/FILE "D:\Documents and Settings\forestr\Desktop\Deployment Test\Deployment Test\bin\Deployment\Package.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI /SET "\Package.Connections[b-ncrsql1.SSIS_CONFIG].Properties[ConnectionString]";"Data Source=b-ncrsql1\test;Initial Catalog=SSIS_CONFIG;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;"

|||

Hmmm, I wonder if the order in which things get applied is a problem? Davide Mauri talks a little avout this here: http://weblogs.sqlteam.com/dmauri/archive/2006/04/02/9489.aspx but I don't think it'll help in your case.

Sorry. I'm a bit stumped. Phil...any ideas?

-Jamie

|||

I've tried a different approach.

Storing the source and destination servers in my SSIS_Config tables on all three servers and storing the source server name for the package configurations in an xml file.

After altering between server1, server2 and server3 in the xml config file, the package always goes directly to the initial location set up in the package: server1.

So I'm confused, no matter what method I use, the configuration I tell the package to use is overridden with the initial configuration in the package.

If I edit the package and set the configuration table to point to server 2, that works but now I can't get it pointing to server 1 or server 3.

There's got to be something I am missing... but what?!

|||

r4enterprises wrote:

I've tried a different approach.

Storing the source and destination servers in my SSIS_Config tables on all three servers and storing the source server name for the package configurations in an xml file.

After altering between server1, server2 and server3 in the xml config file, the package always goes directly to the initial location set up in the package: server1.

So I'm confused, no matter what method I use, the configuration I tell the package to use is overridden with the initial configuration in the package.

If I edit the package and set the configuration table to point to server 2, that works but now I can't get it pointing to server 1 or server 3.

There's got to be something I am missing... but what?!

Make sure that you have that config file listed under "Package Configurations" and that you have package configurations enabled. It works, trust me! I use it all of the time. If it doesn't work for you, then something is wrong.

Know that you must use an absolute file path when pointing to the XML config file.|||If you're going to change the connection string of a connection, I'd use the /CONN switch.|||

Phil,

thanks for your insight. the absolute path might be the problem as when I would build the package, I'd go change the config settings of the xml file that is found in the /bin/Deployment directory and not in the project's folder. I never thought that it would reference an absolute path like that... kinda dumb since that would make packages non-movable between locations.

Please note that when you execute a package with the /conn, that didn't seem to work either. its still pointing to its original location.

I'll try a combination of things when I get to that and keep you guys posted.

Thanks for the help,

Robin

|||

r4enterprises wrote:

I never thought that it would reference an absolute path like that... kinda dumb since that would make packages non-movable between locations.

What if the package is stored in SQL Server? What is a "relative path" and what should it point to? This is why absolute paths are required.sql

Changing column collation

Hi all,
I have an interesting doubt:
In our SQL environments we have some problems with different collations.
Unfortunatelly when this servers and db's were created people didn't care
about collations.
Now would like normalize these environments and db's.
I have a DB with SQL collation SQL_Latin1_General_CP1_CI_AS and all tables
with string fields Latin1_General_CI_AS.
I did an scripts to first drop index and constraints of these string fields,
after I created a script with ALTER TABLE ALTER COLUMN to change the field
collation.
I would expected that this command would do the conversion of the data, but
it was so fast that I'm almost sure that it change only the collation in the
system table...
If i try to change the collation in Enterprise Manager and ask for save the
script SQL always create a new table and transfer the data doing so the
conversion.
My doubt is: If the command ALTER COLUMN doesn't convert the data, the SQL
collation SQL_Latin1_General_CP1_CI_AS is compatible with windows collation
Latin1_General_CI_AS in the sense that also there's no conversion I will not
have any join (between char fieds) problems?
Regards and thanks a lot
Alexandre Calderaro
MCDBA Avanade ItalyHi Alex
You didn't post the script you ran to change the tables. If your data in the
columns are mainly in the normal range (of alphanumerics) there should not be
a need to change the data. The following post gives a way of creating a
script to change the collations http://tinyurl.com/qwulo this assumes the
database has alredy been chagned to the correct collation with an ALTER
DATABASE statement.
John
"Alex" wrote:
> Hi all,
> I have an interesting doubt:
> In our SQL environments we have some problems with different collations.
> Unfortunatelly when this servers and db's were created people didn't care
> about collations.
> Now would like normalize these environments and db's.
> I have a DB with SQL collation SQL_Latin1_General_CP1_CI_AS and all tables
> with string fields Latin1_General_CI_AS.
> I did an scripts to first drop index and constraints of these string fields,
> after I created a script with ALTER TABLE ALTER COLUMN to change the field
> collation.
> I would expected that this command would do the conversion of the data, but
> it was so fast that I'm almost sure that it change only the collation in the
> system table...
> If i try to change the collation in Enterprise Manager and ask for save the
> script SQL always create a new table and transfer the data doing so the
> conversion.
> My doubt is: If the command ALTER COLUMN doesn't convert the data, the SQL
> collation SQL_Latin1_General_CP1_CI_AS is compatible with windows collation
> Latin1_General_CI_AS in the sense that also there's no conversion I will not
> have any join (between char fieds) problems?
> Regards and thanks a lot
> Alexandre Calderaro
> MCDBA Avanade Italy|||Thanks John,
I have a similar script to change the collation of all tables.
For each column I have a similar script:
ALTER TABLE tab ALTER COLUMN col nvarchar(255) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL
Could using a Unicode datatype change the behavior of this command?
My doubt is: what's the difference between using ALTER COLUMN (very fast)
and create a new table with the new collation and transfer data using INSERT
SELECT (obviously much more resource consuming and it's that SQL does if you
change the collation using Enterprise Manager)?
Regards
Alexandre
"John Bell" wrote:
> Hi Alex
> You didn't post the script you ran to change the tables. If your data in the
> columns are mainly in the normal range (of alphanumerics) there should not be
> a need to change the data. The following post gives a way of creating a
> script to change the collations http://tinyurl.com/qwulo this assumes the
> database has alredy been chagned to the correct collation with an ALTER
> DATABASE statement.
> John
>
> "Alex" wrote:
> > Hi all,
> > I have an interesting doubt:
> > In our SQL environments we have some problems with different collations.
> > Unfortunatelly when this servers and db's were created people didn't care
> > about collations.
> > Now would like normalize these environments and db's.
> > I have a DB with SQL collation SQL_Latin1_General_CP1_CI_AS and all tables
> > with string fields Latin1_General_CI_AS.
> > I did an scripts to first drop index and constraints of these string fields,
> > after I created a script with ALTER TABLE ALTER COLUMN to change the field
> > collation.
> > I would expected that this command would do the conversion of the data, but
> > it was so fast that I'm almost sure that it change only the collation in the
> > system table...
> > If i try to change the collation in Enterprise Manager and ask for save the
> > script SQL always create a new table and transfer the data doing so the
> > conversion.
> > My doubt is: If the command ALTER COLUMN doesn't convert the data, the SQL
> > collation SQL_Latin1_General_CP1_CI_AS is compatible with windows collation
> > Latin1_General_CI_AS in the sense that also there's no conversion I will not
> > have any join (between char fieds) problems?
> > Regards and thanks a lot
> >
> > Alexandre Calderaro
> > MCDBA Avanade Italy|||Hi
Enterprise Manager tends to use a belt and braces approach to the SQL
generated and not always the most efficient. The alter table command does not
have to move the data around. Your alter table command should be fine, but it
is always better to thoroughly test in a non-production first!
John
"Alex" wrote:
> Thanks John,
> I have a similar script to change the collation of all tables.
> For each column I have a similar script:
> ALTER TABLE tab ALTER COLUMN col nvarchar(255) COLLATE
> SQL_Latin1_General_CP1_CI_AS NOT NULL
> Could using a Unicode datatype change the behavior of this command?
> My doubt is: what's the difference between using ALTER COLUMN (very fast)
> and create a new table with the new collation and transfer data using INSERT
> SELECT (obviously much more resource consuming and it's that SQL does if you
> change the collation using Enterprise Manager)?
> Regards
> Alexandre
> "John Bell" wrote:
> > Hi Alex
> >
> > You didn't post the script you ran to change the tables. If your data in the
> > columns are mainly in the normal range (of alphanumerics) there should not be
> > a need to change the data. The following post gives a way of creating a
> > script to change the collations http://tinyurl.com/qwulo this assumes the
> > database has alredy been chagned to the correct collation with an ALTER
> > DATABASE statement.
> >
> > John
> >
> >
> >
> > "Alex" wrote:
> >
> > > Hi all,
> > > I have an interesting doubt:
> > > In our SQL environments we have some problems with different collations.
> > > Unfortunatelly when this servers and db's were created people didn't care
> > > about collations.
> > > Now would like normalize these environments and db's.
> > > I have a DB with SQL collation SQL_Latin1_General_CP1_CI_AS and all tables
> > > with string fields Latin1_General_CI_AS.
> > > I did an scripts to first drop index and constraints of these string fields,
> > > after I created a script with ALTER TABLE ALTER COLUMN to change the field
> > > collation.
> > > I would expected that this command would do the conversion of the data, but
> > > it was so fast that I'm almost sure that it change only the collation in the
> > > system table...
> > > If i try to change the collation in Enterprise Manager and ask for save the
> > > script SQL always create a new table and transfer the data doing so the
> > > conversion.
> > > My doubt is: If the command ALTER COLUMN doesn't convert the data, the SQL
> > > collation SQL_Latin1_General_CP1_CI_AS is compatible with windows collation
> > > Latin1_General_CI_AS in the sense that also there's no conversion I will not
> > > have any join (between char fieds) problems?
> > > Regards and thanks a lot
> > >
> > > Alexandre Calderaro
> > > MCDBA Avanade Italysql

Changing column collation

Hi all,
I have an interesting doubt:
In our SQL environments we have some problems with different collations.
Unfortunatelly when this servers and db's were created people didn't care
about collations.
Now would like normalize these environments and db's.
I have a DB with SQL collation SQL_Latin1_General_CP1_CI_AS and all tables
with string fields Latin1_General_CI_AS.
I did an scripts to first drop index and constraints of these string fields,
after I created a script with ALTER TABLE ALTER COLUMN to change the field
collation.
I would expected that this command would do the conversion of the data, but
it was so fast that I'm almost sure that it change only the collation in the
system table...
If i try to change the collation in Enterprise Manager and ask for save the
script SQL always create a new table and transfer the data doing so the
conversion.
My doubt is: If the command ALTER COLUMN doesn't convert the data, the SQL
collation SQL_Latin1_General_CP1_CI_AS is compatible with windows collation
Latin1_General_CI_AS in the sense that also there's no conversion I will not
have any join (between char fieds) problems?
Regards and thanks a lot
Alexandre Calderaro
MCDBA Avanade ItalyHi Alex
You didn't post the script you ran to change the tables. If your data in the
columns are mainly in the normal range (of alphanumerics) there should not b
e
a need to change the data. The following post gives a way of creating a
script to change the collations http://tinyurl.com/qwulo this assumes the
database has alredy been chagned to the correct collation with an ALTER
DATABASE statement.
John
"Alex" wrote:

> Hi all,
> I have an interesting doubt:
> In our SQL environments we have some problems with different collations.
> Unfortunatelly when this servers and db's were created people didn't care
> about collations.
> Now would like normalize these environments and db's.
> I have a DB with SQL collation SQL_Latin1_General_CP1_CI_AS and all tables
> with string fields Latin1_General_CI_AS.
> I did an scripts to first drop index and constraints of these string field
s,
> after I created a script with ALTER TABLE ALTER COLUMN to change the field
> collation.
> I would expected that this command would do the conversion of the data, bu
t
> it was so fast that I'm almost sure that it change only the collation in t
he
> system table...
> If i try to change the collation in Enterprise Manager and ask for save th
e
> script SQL always create a new table and transfer the data doing so the
> conversion.
> My doubt is: If the command ALTER COLUMN doesn't convert the data, the SQL
> collation SQL_Latin1_General_CP1_CI_AS is compatible with windows collati
on
> Latin1_General_CI_AS in the sense that also there's no conversion I will n
ot
> have any join (between char fieds) problems?
> Regards and thanks a lot
> Alexandre Calderaro
> MCDBA Avanade Italy|||Thanks John,
I have a similar script to change the collation of all tables.
For each column I have a similar script:
ALTER TABLE tab ALTER COLUMN col nvarchar(255) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL
Could using a Unicode datatype change the behavior of this command?
My doubt is: what's the difference between using ALTER COLUMN (very fast)
and create a new table with the new collation and transfer data using INSERT
SELECT (obviously much more resource consuming and it's that SQL does if you
change the collation using Enterprise Manager)?
Regards
Alexandre
"John Bell" wrote:
[vbcol=seagreen]
> Hi Alex
> You didn't post the script you ran to change the tables. If your data in t
he
> columns are mainly in the normal range (of alphanumerics) there should not
be
> a need to change the data. The following post gives a way of creating a
> script to change the collations http://tinyurl.com/qwulo this assumes the
> database has alredy been chagned to the correct collation with an ALTER
> DATABASE statement.
> John
>
> "Alex" wrote:
>|||Hi
Enterprise Manager tends to use a belt and braces approach to the SQL
generated and not always the most efficient. The alter table command does no
t
have to move the data around. Your alter table command should be fine, but i
t
is always better to thoroughly test in a non-production first!
John
"Alex" wrote:
[vbcol=seagreen]
> Thanks John,
> I have a similar script to change the collation of all tables.
> For each column I have a similar script:
> ALTER TABLE tab ALTER COLUMN col nvarchar(255) COLLATE
> SQL_Latin1_General_CP1_CI_AS NOT NULL
> Could using a Unicode datatype change the behavior of this command?
> My doubt is: what's the difference between using ALTER COLUMN (very fast)
> and create a new table with the new collation and transfer data using INSE
RT
> SELECT (obviously much more resource consuming and it's that SQL does if y
ou
> change the collation using Enterprise Manager)?
> Regards
> Alexandre
> "John Bell" wrote:
>

Changing collation on server

Hello there
On one of my servers diffrent collation is being declered.
I need to change it to SQL_LATIN1_GENERAL_SP1_CI_AS
I used rebuildm program for that. and it failed
what i need to do on the regional settings for allowing this type of
collation?Roy,
what do you mean with rebuildm.exe failed. Did you get any errors or do
you just mean that the collation of your server hasn't changed? By the
way be aware of the fact that rebuildm.exe only changes the collation
of the master, model, msdb and tempdb. Your user databases you have to
convert "manually".
Markus|||How do you change the user databases collation manualy? I have changed the
master db by using rebuildm.exe.
George
"MarkusB" wrote:
> Roy,
> what do you mean with rebuildm.exe failed. Did you get any errors or do
> you just mean that the collation of your server hasn't changed? By the
> way be aware of the fact that rebuildm.exe only changes the collation
> of the master, model, msdb and tempdb. Your user databases you have to
> convert "manually".
> Markus
>sql

Changing collation on server

Hello there
On one of my servers diffrent collation is being declered.
I need to change it to SQL_LATIN1_GENERAL_SP1_CI_AS
I used rebuildm program for that. and it failed
what i need to do on the regional settings for allowing this type of
collation?Roy,
what do you mean with rebuildm.exe failed. Did you get any errors or do
you just mean that the collation of your server hasn't changed? By the
way be aware of the fact that rebuildm.exe only changes the collation
of the master, model, msdb and tempdb. Your user databases you have to
convert "manually".
Markus|||How do you change the user databases collation manualy? I have changed the
master db by using rebuildm.exe.
George
"MarkusB" wrote:

> Roy,
> what do you mean with rebuildm.exe failed. Did you get any errors or do
> you just mean that the collation of your server hasn't changed? By the
> way be aware of the fact that rebuildm.exe only changes the collation
> of the master, model, msdb and tempdb. Your user databases you have to
> convert "manually".
> Markus
>

Changing collation on server

Hello there
On one of my servers diffrent collation is being declered.
I need to change it to SQL_LATIN1_GENERAL_SP1_CI_AS
I used rebuildm program for that. and it failed
what i need to do on the regional settings for allowing this type of
collation?
Roy,
what do you mean with rebuildm.exe failed. Did you get any errors or do
you just mean that the collation of your server hasn't changed? By the
way be aware of the fact that rebuildm.exe only changes the collation
of the master, model, msdb and tempdb. Your user databases you have to
convert "manually".
Markus

change the look of Report Manager

I would like to change the look of the Report Manager. I have Reporting
Services on both developement and production servers. I would like to
be able to change the color or font etc. so that I can tell without
having to look in the address box to figure out what server I am on.
Is there a value I can change somewhere that will do this for me?Hi Lou,
you could just edit the style sheet
\Reporting Services\ReportManager\Styles\ReportingServices.css
regards
Matt
"Lou" <lbonnes@.yahoo.com> wrote in message
news:1105847715.370619.296730@.f14g2000cwb.googlegroups.com...
> I would like to change the look of the Report Manager. I have Reporting
> Services on both developement and production servers. I would like to
> be able to change the color or font etc. so that I can tell without
> having to look in the address box to figure out what server I am on.
> Is there a value I can change somewhere that will do this for me?
>

Change Sql Server 2000 Enterprise to Standard Edition

Hi,

One of our main servers running on SQL Server 2000 Enterprise edition which has transactional replications on it which replicates to other servers running on the SQL Server 2000 Enterprise edition as well.

Due to Hardware problems the server is being migrated to a new machine but the client has installed SQL Server 2000 standard edition on the new machine.

We will be using a two processor cpu with 4GB RAM and we are also not planning about clustering. Is there any problem if i migrate the server in Standard Edition will the replications work properly between Standard and Enterprise editions.

What other complications can be there if i switch over to standard edition from enterprise edition

Thanks in ADVANCE

Jacx

In SQL 2000 there are no edition aware features for transactional replication (other than for MSDE). So you will be fine!

change sql ce merge replication servers

I have about 115 sql ce databases syncing to about 100 sql databases. The
sql databases are all on the same server. We want to move the sql databases
to a new server without any data loss. Does anyone have any good ideas on
how to accomplish this or links to resources about this kind of thing?
Thanks, Scott
I think you will need to create the new publications and then push the new
program doing the pull to the SQL CE devices with the updated publisher
information.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Scott S." <ScottS@.discussions.microsoft.com> wrote in message
news:7100354D-4314-46D2-A937-9D5D1964A0DD@.microsoft.com...
>I have about 115 sql ce databases syncing to about 100 sql databases. The
> sql databases are all on the same server. We want to move the sql
> databases
> to a new server without any data loss. Does anyone have any good ideas on
> how to accomplish this or links to resources about this kind of thing?
> Thanks, Scott
|||Here's what I got working: Stop clients from syncing, create a backup of the
databases to be switched, restore the backup to the new server and create the
publications, the last step is to reinitialize the subscriptions with upload
set to true.

Change server name in MSSQL cluster

Hi all, I've got PDC and BDC Windows NT 4.0 Servers (Enterprise edition) installed in the MS cluster. The clustered application is MS SQL server 7.0. Now I need to change names of both nodes - PDC and BDC Windows NT 4.0 Servers. Has anyone any experience with such operation ? Is it too risky ? Thanks a lot for any hint MichalChanging the server names will break your SQL servers.

I did this on a standalone (changed the server name) and SQL stopped working. The fix according to Microsoft was to reinstall SQL on the servers. When the installation starts it will see that all the components are already installed and then see the name resolution conflict and fix it.

This worked for the standalone but I dont' know about the cluster.|||Furthermore, you can not change the name of a PDC without reinstalling NT 4 server.

Change report host server name?

We have a SSRS web setup on one of our servers, and originally it was setup
using the server's internal name. we want to be able to change this to use
the external name. When you go to a report the frame which hosts the report
output the src shows http://zweb/reportserver. we want this to show instead
http://www.mycompany.com/reportserver. how can we change this?
we tried changing the rsreportserver.config.
We want to host the reports page under our clients sites so we can give them
reports for their web stats and the like. So eg. we have a client named
www.myclient.com. under their site, we made a virtual directory which points
to the server\reports web site.
Thanks in advance,
- Arthur Dent.I have run into the same problem. I tried changing the baseUrl and I end
up getting a 401 error.
--
Message posted via http://www.sqlmonster.com|||Found the answer to my problem here:
http://www.sqljunkies.com/forums/showpost.aspx?postid=4393
Also you may want to do a search on this term:
ReportServerExternalURL
It is a setting that microsoft says you need to set, but I couldn't get it
to work. I got mine to work using the link above!
Hope this helps!
--
Message posted via http://www.sqlmonster.com|||You need to make sure you have edited the RSReportManager.config file to
point to the new server.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Benedict via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:9c496e631eb14a3f81be421acb338af7@.SQLMonster.com...
>I have run into the same problem. I tried changing the baseUrl and I end
> up getting a 401 error.
> --
> Message posted via http://www.sqlmonster.com

Change Password in XP and Lose Servers in Enterprise

I have a frustrating situation but I have been unable to
find help elsewhere on this topic. Each time I change my
password at work on my Windows XP Professional machine I
lose all the servers that I had registered in SQL
Enterprise Manager. This is very frustrating because I
have to change my password every 45 days and I have over
20 servers registered. Any ideas on how to fix this to
not lose my registrations? Please help.
thanks,
allen...It happened few times to few developers at my company. After forced to
change the password, all registered servers were gone. However we haven't
seen this come back for about 8 - 10 months. Probably a windows update or
SQL update fixed it?
"Allen" <AMora@.tradestation.com> wrote in message
news:0d6a01c36e45$e5b48e40$a401280a@.phx.gbl...
> I have a frustrating situation but I have been unable to
> find help elsewhere on this topic. Each time I change my
> password at work on my Windows XP Professional machine I
> lose all the servers that I had registered in SQL
> Enterprise Manager. This is very frustrating because I
> have to change my password every 45 days and I have over
> 20 servers registered. Any ideas on how to fix this to
> not lose my registrations? Please help.
> thanks,
> allen...|||I've never lost any of my registrations this way. However, perhaps if you
use SQL authentication instead of Windows authentication for your
registration properties?
"Allen" <AMora@.tradestation.com> wrote in message
news:0d6a01c36e45$e5b48e40$a401280a@.phx.gbl...
> I have a frustrating situation but I have been unable to
> find help elsewhere on this topic. Each time I change my
> password at work on my Windows XP Professional machine I
> lose all the servers that I had registered in SQL
> Enterprise Manager. This is very frustrating because I
> have to change my password every 45 days and I have over
> 20 servers registered. Any ideas on how to fix this to
> not lose my registrations? Please help.
> thanks,
> allen...|||Allen,
Is this the issue?
FIX: Registered Remote Servers Disappear from SQL Enterprise Manager in
Windows XP When Non-Domain User Password is Changed
http://support.microsoft.com/default.aspx?scid=kb;en-us;323280
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Allen" <AMora@.tradestation.com> wrote in message
news:0d6a01c36e45$e5b48e40$a401280a@.phx.gbl...
> I have a frustrating situation but I have been unable to
> find help elsewhere on this topic. Each time I change my
> password at work on my Windows XP Professional machine I
> lose all the servers that I had registered in SQL
> Enterprise Manager. This is very frustrating because I
> have to change my password every 45 days and I have over
> 20 servers registered. Any ideas on how to fix this to
> not lose my registrations? Please help.
> thanks,
> allen...|||btw, we are using SQL logins, not Windows ...
"Flicker" <hthan@.superioraccess.com> wrote in message
news:%23s3IRckbDHA.1600@.TK2MSFTNGP09.phx.gbl...
> It happened few times to few developers at my company. After forced to
> change the password, all registered servers were gone. However we haven't
> seen this come back for about 8 - 10 months. Probably a windows update or
> SQL update fixed it?
> "Allen" <AMora@.tradestation.com> wrote in message
> news:0d6a01c36e45$e5b48e40$a401280a@.phx.gbl...
> > I have a frustrating situation but I have been unable to
> > find help elsewhere on this topic. Each time I change my
> > password at work on my Windows XP Professional machine I
> > lose all the servers that I had registered in SQL
> > Enterprise Manager. This is very frustrating because I
> > have to change my password every 45 days and I have over
> > 20 servers registered. Any ideas on how to fix this to
> > not lose my registrations? Please help.
> >
> > thanks,
> > allen...
>

Change NT Domain Name with SQL Servers in

Hello,
the administrators want to change our NT (NT 2000) domain name (no Active Di
rectory), where we have
several SQL Servers in.
Which actions should I do / which pitfalls should I take care of to make the
SQL Severs and their
accounts, services... run after the change ?
Thank You
Joachimone caveat with Service Accounts in general is to make sure that you change
the Service Accounts using Enterprise Manager as opposed to Services.msc
etc.
Most of the time you get away with if Service Account is Local Admin - but
if the box has been hardened you can get problems
documented below
http://support.microsoft.com/defaul...kb;en-us;283811
regards,
Andy
"Joachim Hofmann" <speicher@.freenet.de> wrote in message
news:40E1972B.73739A36@.freenet.de...
> Hello,
> the administrators want to change our NT (NT 2000) domain name (no Active
Directory), where we have
> several SQL Servers in.
> Which actions should I do / which pitfalls should I take care of to make
the SQL Severs and their
> accounts, services... run after the change ?
> Thank You
> Joachim