Best Practices for Moving SQL Server to Another domain?

I've been looking all over the KB trying to find documentation on Best
Practices for moving a SQL Server to another domain. What reACLing needs to
be done to the databases (if any) and what is the best way to do it?
Thanks for any links or help...Here are a couple of Links...
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
http://support.microsoft.com/default.aspx?scid=kb;en-us;304692
Personally I would go for the first one, as it will transfer everything over.
Once completion do a sp_createstats & sp_updatestats
After than I would advise you run a performance trace for a about a week and
implement any changes, then run the sp_createstats & sp_updatestats again
Peter
"Denial ain't just a river in Egypt."
Mark Twain
"Losferwords" wrote:
> I've been looking all over the KB trying to find documentation on Best
> Practices for moving a SQL Server to another domain. What reACLing needs to
> be done to the databases (if any) and what is the best way to do it?
> Thanks for any links or help...|||Let me be a little more specific... I'm moving a SQL Server from DOMAIN A to
DOMAIN B. Any Best Practices Guides on that?
"Losferwords" wrote:
> I've been looking all over the KB trying to find documentation on Best
> Practices for moving a SQL Server to another domain. What reACLing needs to
> be done to the databases (if any) and what is the best way to do it?
> Thanks for any links or help...

Best Practices for Moving SQL Server to Another domain?

I've been looking all over the KB trying to find documentation on Best
Practices for moving a SQL Server to another domain. What reACLing needs to
be done to the databases (if any) and what is the best way to do it?
Thanks for any links or help...
Here are a couple of Links...
http://support.microsoft.com/default...b;en-us;224071
http://support.microsoft.com/default...b;en-us;304692
Personally I would go for the first one, as it will transfer everything over.
Once completion do a sp_createstats & sp_updatestats
After than I would advise you run a performance trace for a about a week and
implement any changes, then run the sp_createstats & sp_updatestats again
Peter
"Denial ain't just a river in Egypt."
Mark Twain
"Losferwords" wrote:

> I've been looking all over the KB trying to find documentation on Best
> Practices for moving a SQL Server to another domain. What reACLing needs to
> be done to the databases (if any) and what is the best way to do it?
> Thanks for any links or help...
|||Let me be a little more specific... I'm moving a SQL Server from DOMAIN A to
DOMAIN B. Any Best Practices Guides on that?
"Losferwords" wrote:

> I've been looking all over the KB trying to find documentation on Best
> Practices for moving a SQL Server to another domain. What reACLing needs to
> be done to the databases (if any) and what is the best way to do it?
> Thanks for any links or help...
sql

Best Practices for Moving SQL Server to Another domain?

I've been looking all over the KB trying to find documentation on Best
Practices for moving a SQL Server to another domain. What reACLing needs to
be done to the databases (if any) and what is the best way to do it?
Thanks for any links or help...Here are a couple of Links...
http://support.microsoft.com/defaul...kb;en-us;224071
http://support.microsoft.com/defaul...kb;en-us;304692
Personally I would go for the first one, as it will transfer everything over
.
Once completion do a sp_createstats & sp_updatestats
After than I would advise you run a performance trace for a about a week and
implement any changes, then run the sp_createstats & sp_updatestats again
Peter
"Denial ain't just a river in Egypt."
Mark Twain
"Losferwords" wrote:

> I've been looking all over the KB trying to find documentation on Best
> Practices for moving a SQL Server to another domain. What reACLing needs
to
> be done to the databases (if any) and what is the best way to do it?
> Thanks for any links or help...|||Let me be a little more specific... I'm moving a SQL Server from DOMAIN A t
o
DOMAIN B. Any Best Practices Guides on that?
"Losferwords" wrote:

> I've been looking all over the KB trying to find documentation on Best
> Practices for moving a SQL Server to another domain. What reACLing needs
to
> be done to the databases (if any) and what is the best way to do it?
> Thanks for any links or help...

Best practice for SQL cluster and domains

Hi All,
We have a critical 24x7 SQL cluster (W2K), which is a member of an NT 4
domain. As hardware is getting old, and NT4 domain is going to disappear in
the near future, the cluster has to be re-newed. There is also a trusted
Active Directory domain, which holds about all user accounts and groups.
These accounts and groups have been assigned appropriate rights to SQL and
application generated reports.
What makes this a bit more difficult, is that the company is also going to
split, as is network and AD. The split will take place within few months,
but the new AD (where the users finally will be located) is expected to be
in place and fully functional within one year. However, the new cluster
should be up and running within two months. The cluster will be built on
Windows server 2003 Enterprise.
What I should do, is to provide best scenario for implementing new cluster,
so that it minimizes work when AD domains in question change.
As far as I am concerned, if you change a cluster domain membership, you
need to rebuild the whole cluster. This is not what we want to do. We are
prepared to re-assign all appropriate user right and roles as users' domain
changes.
I see following scenarios:
1. join new cluster to present AD domain
2. install new cluster nodes as domain controllers for new "domainlet" or
domain and create trust relationships as needed
3. install separate domain controllers, and join cluster to this domain,
create trust relationships as needed
4. something else?
In scenario 1 I see most work; rebuilding the whole cluster within a year or
so. About scenarios 2 and 3 I'd like to have comments, especially about
using domainlets
(http://www.microsoft.com/windows2000...cluster/domain
lets.asp). Or, there might be a lot better option, which I have not come to
think about.
Please share your opinions and comments,
John
Great questions.
I like option 1, have you read http://support.microsoft.com/?id=319016, no
need to rebuild the cluster and start all over. Pretty easy actually.
Have you read http://support.microsoft.com/?id=298570, so option 2 is not
looking good.
Option 3 will work, but I hate extra trusts, if I can avoid them.
Go with number 1, that is what I would do
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"John" <someone@.microsoft.com> wrote in message
news:41f50ef2@.usenet01.boi.hp.com...
> Hi All,
> We have a critical 24x7 SQL cluster (W2K), which is a member of an NT 4
> domain. As hardware is getting old, and NT4 domain is going to disappear
> in
> the near future, the cluster has to be re-newed. There is also a trusted
> Active Directory domain, which holds about all user accounts and groups.
> These accounts and groups have been assigned appropriate rights to SQL and
> application generated reports.
> What makes this a bit more difficult, is that the company is also going to
> split, as is network and AD. The split will take place within few months,
> but the new AD (where the users finally will be located) is expected to be
> in place and fully functional within one year. However, the new cluster
> should be up and running within two months. The cluster will be built on
> Windows server 2003 Enterprise.
> What I should do, is to provide best scenario for implementing new
> cluster,
> so that it minimizes work when AD domains in question change.
> As far as I am concerned, if you change a cluster domain membership, you
> need to rebuild the whole cluster. This is not what we want to do. We are
> prepared to re-assign all appropriate user right and roles as users'
> domain
> changes.
> I see following scenarios:
> 1. join new cluster to present AD domain
> 2. install new cluster nodes as domain controllers for new "domainlet" or
> domain and create trust relationships as needed
> 3. install separate domain controllers, and join cluster to this domain,
> create trust relationships as needed
> 4. something else?
> In scenario 1 I see most work; rebuilding the whole cluster within a year
> or
> so. About scenarios 2 and 3 I'd like to have comments, especially about
> using domainlets
> (http://www.microsoft.com/windows2000...cluster/domain
> lets.asp). Or, there might be a lot better option, which I have not come
> to
> think about.
> Please share your opinions and comments,
> John
>
|||Rod,
thanks really, this was great information. I'll investigate the options
again in the light of your recent information, the scenario 1 looks now
actually quite good. If you have something to add, please do not hesitate to
share it
Cheers, John
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23z6TlkjAFHA.3592@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Great questions.
> I like option 1, have you read http://support.microsoft.com/?id=319016, no
> need to rebuild the cluster and start all over. Pretty easy actually.
> Have you read http://support.microsoft.com/?id=298570, so option 2 is not
> looking good.
> Option 3 will work, but I hate extra trusts, if I can avoid them.
> Go with number 1, that is what I would do
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "John" <someone@.microsoft.com> wrote in message
> news:41f50ef2@.usenet01.boi.hp.com...
and[vbcol=seagreen]
to[vbcol=seagreen]
months,[vbcol=seagreen]
be[vbcol=seagreen]
are[vbcol=seagreen]
or[vbcol=seagreen]
year[vbcol=seagreen]
(http://www.microsoft.com/windows2000...cluster/domain
>

Best Practice for Domain Account for SQL Services?

Hello,

I've done some searching, but have found no definite answer yet. Our SQL 2005 servers are members of Active Directory Services. We want to run SQL services using an ADS account.

I see 7 SQL services in the SQL Server Configuration Manager: Integration Services, FullText Search, SQL Server, Analysis Services, Reporting Services, Browser, and Agent.

Question: Is it a bad move to run them all using the same domain account? I mean, wouldn't this give, say the Browser service, more privileges than it needs by allowing its account access to the same resources as, for example, the Agent service? What I'm concerned about is a vulnerability in one service compromising another service.

I would like to be able to use one domain account for all 7 services on two SQL servers, but I have a feeling this is a poor choice.

What is the best method for running SQL services using a domain account?

Thanks,

-Tony

Perhaps these articles will help you in your decison process:

Configuration -Service Accounts, SQL Server 2005 - Setting Up Windows Service Accounts
http://msdn2.microsoft.com/en-us/library/ms143691.aspx
http://msdn2.microsoft.com/en-us/library/ms143504.aspx

Configuration -Service Accounts, SQL Server or SQL Server Agent service account
http://support.microsoft.com/kb/283811/en-us
http://msdn2.microsoft.com/en-us/library/ms143691.aspx

Configuration -Service Accounts,Selecting an Account for the SQL Server Agent Service
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
http://support.microsoft.com/kb/907557

Often, SQL Agent needs a higher level of access to network resources than the SQL Server Service. It is a good practice to provide the minimum level of access to local and network resources as is required for the task. It would not be unusual to have multiple domain accounts for the various SQL Services. In fact, for those services that require network resources, some folks will have separate domain accounts for each server. I have seen every SQL Agent service running under a unique account -the theory is if one server is compomised, unique accounts protect the remaining servers from compromise.

It is a balance between amount of security desired vs. amount of effort required to maintain that security. (As always...)

Best approach SQL Reporting Authentication - WorkGroup

Hi there
Situration
1.Development Server is on WorkGroup, not main Domain. (win 2003
server(std))
2.Accessing dev server via \\Main Domain\Administrator
3.SQL 2K (Std)
SQL Reporting
1.Using SQL authentication for shared resource, rather win
authentication.
2.Shared folder, access set to everyone.
Current Situration
1.Have created 5 reports, each has a url within Domino Notes
application. Click on anyone of them (assuming
\\Main Domain\Administrator\) --> reports work ok.
2.Log-on as non-administrator --> click on url, enter site ok, but
popup appears asking for authentication of user
e.g. name, pwd & domain.
Constraints
1.Development Box cannot be joined to main domain i.e. Non-Wins
authentication
2.Host name e.g. http:\\wtdev01\reportserver --> dealt with WINS
server, not host file !
Requirement
Any user clicks on URL for the report, will open the report and be run
without authentication issues.
Tried
1.Custom Authentication (e.g. Form Authentication) - issue cannot use
Standard version of SQL Server ! Needs to be Enterprise. Dead end.
Any ideas.This is where Anonymous access may do the trick for you if you don't need RS
to differentiate the users. If you do, then one of your constraints needs to
go away.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"ImraneA" <i.akram@.weir.co.uk> wrote in message
news:24b9d612.0411010439.7f2e15d4@.posting.google.com...
> Hi there
> Situration
> 1.Development Server is on WorkGroup, not main Domain. (win 2003
> server(std))
> 2.Accessing dev server via \\Main Domain\Administrator
> 3.SQL 2K (Std)
> SQL Reporting
> 1.Using SQL authentication for shared resource, rather win
> authentication.
> 2.Shared folder, access set to everyone.
> Current Situration
> 1.Have created 5 reports, each has a url within Domino Notes
> application. Click on anyone of them (assuming
> \\Main Domain\Administrator\) --> reports work ok.
> 2.Log-on as non-administrator --> click on url, enter site ok, but
> popup appears asking for authentication of user
> e.g. name, pwd & domain.
> Constraints
> 1.Development Box cannot be joined to main domain i.e. Non-Wins
> authentication
> 2.Host name e.g. http:\\wtdev01\reportserver --> dealt with WINS
> server, not host file !
> Requirement
> Any user clicks on URL for the report, will open the report and be run
> without authentication issues.
> Tried
> 1.Custom Authentication (e.g. Form Authentication) - issue cannot use
> Standard version of SQL Server ! Needs to be Enterprise. Dead end.
> Any ideas.|||Give that a try. Thanks.