Collation of Database and Server

Hello,
I am working a problem according to the collation of MS SQL Server
2000 and a database.
Environment: German MS SQL Server 2000 SP3a
Server Collation: Latin1_General_CI_AS
Collation of the database: SQL_Latin1_General_CP1_CI_AS
(Note: the database was created in an english MSDE and dureing an
upgrade restored on the SQL Server)
During an application upgrade process (refering to the SQL Server
database) I was running into a lot of problems according the datetime
format. So my suggestion was that this problem is related to the
different collations, cause in a different testing environment with
another collation (server collation = database collation) I was able
to perform the upgrade.
So, now I am wondering if its possible to change the database
collation without loosing my data? (hoping that this will solve the
prolem)
Any suggestions or experiences are welcome
tia,
Marcus
Marcus
Yes , you can change COLLATION in the database
Look at ALTER DATABASE in the BOL
> I was running into a lot of problems according the datetime
> format.
Look, without seeing your code/query its hard to suggest something.
"Marcus Schmidt" <Schmidt_Marcus*at*gmx.de> wrote in message
news:t139p0lqkn9219ii7opkjv26tkto4u2528@.4ax.com...
> Hello,
> I am working a problem according to the collation of MS SQL Server
> 2000 and a database.
> Environment: German MS SQL Server 2000 SP3a
> Server Collation: Latin1_General_CI_AS
> Collation of the database: SQL_Latin1_General_CP1_CI_AS
> (Note: the database was created in an english MSDE and dureing an
> upgrade restored on the SQL Server)
> During an application upgrade process (refering to the SQL Server
> database) I was running into a lot of problems according the datetime
> format. So my suggestion was that this problem is related to the
> different collations, cause in a different testing environment with
> another collation (server collation = database collation) I was able
> to perform the upgrade.
> So, now I am wondering if its possible to change the database
> collation without loosing my data? (hoping that this will solve the
> prolem)
> Any suggestions or experiences are welcome
> tia,
> Marcus

Collation of Database and Server

Hello,
I am working a problem according to the collation of MS SQL Server
2000 and a database.
Environment: German MS SQL Server 2000 SP3a
Server Collation: Latin1_General_CI_AS
Collation of the database: SQL_Latin1_General_CP1_CI_AS
(Note: the database was created in an english MSDE and dureing an
upgrade restored on the SQL Server)
During an application upgrade process (refering to the SQL Server
database) I was running into a lot of problems according the datetime
format. So my suggestion was that this problem is related to the
different collations, cause in a different testing environment with
another collation (server collation = database collation) I was able
to perform the upgrade.
So, now I am wondering if its possible to change the database
collation without loosing my data? (hoping that this will solve the
prolem)
Any suggestions or experiences are welcome
tia,
MarcusMarcus
Yes , you can change COLLATION in the database
Look at ALTER DATABASE in the BOL
> I was running into a lot of problems according the datetime
> format.
Look, without seeing your code/query its hard to suggest something.
"Marcus Schmidt" <Schmidt_Marcus*at*gmx.de> wrote in message
news:t139p0lqkn9219ii7opkjv26tkto4u2528@.
4ax.com...
> Hello,
> I am working a problem according to the collation of MS SQL Server
> 2000 and a database.
> Environment: German MS SQL Server 2000 SP3a
> Server Collation: Latin1_General_CI_AS
> Collation of the database: SQL_Latin1_General_CP1_CI_AS
> (Note: the database was created in an english MSDE and dureing an
> upgrade restored on the SQL Server)
> During an application upgrade process (refering to the SQL Server
> database) I was running into a lot of problems according the datetime
> format. So my suggestion was that this problem is related to the
> different collations, cause in a different testing environment with
> another collation (server collation = database collation) I was able
> to perform the upgrade.
> So, now I am wondering if its possible to change the database
> collation without loosing my data? (hoping that this will solve the
> prolem)
> Any suggestions or experiences are welcome
> tia,
> Marcus

Collation and Win2K3 Clustered Environment.

This past weekend I was challenged a little in resolving what I hoped was a
simple collation issue. We are running Win2K3 Ent. Clustering Services, SQL
Server 2000 Enterprise, b.8.00.760.
On Friday, 2.11, a user migrated an application to this new clustered setup
and immediately received the infamous 446 collation error.
I spent most of Friday evening and all day Saturday reviewing support topics
and news groups. I found that there was 1 issue that could be affecting us -
the build of SQL Server for Win2K3 Ent. Clustering is subtly different than
for Win2KAS Clustering - and all of my research came back to one thing: Run
rebuildm.exe and set the collation of this instance to be the same as the
existing development/production environment. The default setup on the cluster
was different than the previous production setup, as well as different than
the current development environment.
So, I backed everyone's database up, then the master objects, shut the
instance down, executed rebuild and set the collation to what I needed it to
be.
When I brought this user's database online - the same exact error occurs.
Prior to doing this, here is what we were faced with:
Development / Previous Production: Server=Win2K, SQL=SQL Server 2000
Enterprise w/Collate=SQL_Latin1_General_CP1_CI_AS.
The new clustered SQL=SQL Server Enterprise, w/Collate=Latin1_General_CI_AI.
The database/application in question, at the procedure where we receive the
collation error, basically calls a function that creates a temp table, then
another that pulls data for a report - however, the data is collected as a
JOIN on this tempdb temp object and a series of Views the programmer
previously setup. These views in turn hit various other static tables as well.
We were thinking that because of the collation difference on the new Win2K3
setup, as well as Collation/Locale settings differences with Win2K3
Clustering, we should at a minimum change the instance to match the
SQL_Latin1, etc. collation of development. This however, has not solved the
problem.
At this juncture, the Win2K3 Clustered server has the collation
SQL_Latin1_General_CP1_CI_AI, and the development environment (as well as
their current production environment, which is 2KAS nonclustered) is
SQL_Latin1_General_CP1_CI_AS... The only difference in the two right now is
the accent sensitivity - but this should not be the issue.
If anyone else out there has any feedback, I'd be grateful for your time.
Thanks...
mhamilton"AT"nusoftsolutions"DOT"com
If the collation names are different you'll get the collation conflict
error -- a difference in accent sensitivity is sufficient to expose the
problem.
One option is rebuild master in dev or test (again) so that the two servers
have the same collation. You almost matched the collation last time, but
the different accent sensitivity setting is also critical.
Another option is to make sure that the T-SQL is written in a way that
makes it immune to the problem. For the scenario you describe you could do
this by making sure that your temp tables inherit the collation of the
current user database, not the collation of tempdb. A "COLLATE
database_default" clause will accomplish this. For example, when creating
the temp table in the stored proc:
CREATE TABLE #temp1 (
c1 int,
c2 varchar (30) COLLATE database_default,
c3 char(12) COLLATE database_default,
)
HTH,
Bart
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Collation and Win2K3 Clustered Environment.
| thread-index: AcUUNUWE2BoB7xCnSeWo8pOsRpOhYg==
| X-WBNR-Posting-Host: 12.227.130.93
| From: "=?Utf-8?B?TWlrZUg=?=" <MikeH@.discussions.microsoft.com>
| Subject: Collation and Win2K3 Clustered Environment.
| Date: Wed, 16 Feb 2005 06:39:08 -0800
| Lines: 51
| Message-ID: <87A19939-8444-4CEC-BBB4-ED092DFFD4D7@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.clustering
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFT NGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.clustering:3114
| X-Tomcat-NG: microsoft.public.sqlserver.clustering
|
| This past weekend I was challenged a little in resolving what I hoped was
a
| simple collation issue. We are running Win2K3 Ent. Clustering Services,
SQL
| Server 2000 Enterprise, b.8.00.760.
|
| On Friday, 2.11, a user migrated an application to this new clustered
setup
| and immediately received the infamous 446 collation error.
|
| I spent most of Friday evening and all day Saturday reviewing support
topics
| and news groups. I found that there was 1 issue that could be affecting
us -
| the build of SQL Server for Win2K3 Ent. Clustering is subtly different
than
| for Win2KAS Clustering - and all of my research came back to one thing:
Run
| rebuildm.exe and set the collation of this instance to be the same as the
| existing development/production environment. The default setup on the
cluster
| was different than the previous production setup, as well as different
than
| the current development environment.
|
| So, I backed everyone's database up, then the master objects, shut the
| instance down, executed rebuild and set the collation to what I needed it
to
| be.
|
| When I brought this user's database online - the same exact error occurs.
|
| Prior to doing this, here is what we were faced with:
| Development / Previous Production: Server=Win2K, SQL=SQL Server 2000
| Enterprise w/Collate=SQL_Latin1_General_CP1_CI_AS.
|
| The new clustered SQL=SQL Server Enterprise,
w/Collate=Latin1_General_CI_AI.
|
| The database/application in question, at the procedure where we receive
the
| collation error, basically calls a function that creates a temp table,
then
| another that pulls data for a report - however, the data is collected as
a
| JOIN on this tempdb temp object and a series of Views the programmer
| previously setup. These views in turn hit various other static tables as
well.
|
| We were thinking that because of the collation difference on the new
Win2K3
| setup, as well as Collation/Locale settings differences with Win2K3
| Clustering, we should at a minimum change the instance to match the
| SQL_Latin1, etc. collation of development. This however, has not solved
the
| problem.
|
| At this juncture, the Win2K3 Clustered server has the collation
| SQL_Latin1_General_CP1_CI_AI, and the development environment (as well as
| their current production environment, which is 2KAS nonclustered) is
| SQL_Latin1_General_CP1_CI_AS... The only difference in the two right now
is
| the accent sensitivity - but this should not be the issue.
|
| If anyone else out there has any feedback, I'd be grateful for your time.
|
| Thanks...
|
| mhamilton"AT"nusoftsolutions"DOT"com
|
|||Bart, thanks for getting back to me.
I must confess, moving from 2KAS Clustering to 2K3 Clustering is NOT fun.
Simply because of the nuances I am finding.
Foremost, I did get the application working, and thus far I have not
experienced the infamous 446 collation error.
However...
This particular cluster is only running 6 instances of SQL Server. Each
instance has the Full Text Search engine/component installed - yet only 2 of
the instances are actually using it - and the problem I ran into is on 1 of
these 2 instances.
Specifically, this instance has the full text search active.
Now...
IF - and I say this 'loudly' - IF the full text server was 'offline' when I
did the rebuild - then restarted the instance and tested the app - the app
failed. Most interesting...
It took me a couple days to see what was happening. So... I did the same
with the full text 'online' and voila!!! I have joy... The application worked
fine.
Now... I have a few questions, but I'm sure you're not going to be able to
answer them anymore than I can. This notwithstanding, I find it interesting
that rebuilding the instance - with the SQL Full Text 'offline' when I do it
-could actually keep it from working. Yes, software is software - but this is
quirky at best.
Anyway... Thank you for responding... I will be in contact with PSS and my
manager on this issue, and if you have any other questions regarding the
setup, please feel free to contact me.
"Bart Duncan [MSFT]" wrote:

> If the collation names are different you'll get the collation conflict
> error -- a difference in accent sensitivity is sufficient to expose the
> problem.
> One option is rebuild master in dev or test (again) so that the two servers
> have the same collation. You almost matched the collation last time, but
> the different accent sensitivity setting is also critical.
> Another option is to make sure that the T-SQL is written in a way that
> makes it immune to the problem. For the scenario you describe you could do
> this by making sure that your temp tables inherit the collation of the
> current user database, not the collation of tempdb. A "COLLATE
> database_default" clause will accomplish this. For example, when creating
> the temp table in the stored proc:
> CREATE TABLE #temp1 (
> c1 int,
> c2 varchar (30) COLLATE database_default,
> c3 char(12) COLLATE database_default,
> )
> HTH,
> Bart
> --
> Bart Duncan
> Microsoft SQL Server Support
> Please reply to the newsgroup only - thanks.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> | Thread-Topic: Collation and Win2K3 Clustered Environment.
> | thread-index: AcUUNUWE2BoB7xCnSeWo8pOsRpOhYg==
> | X-WBNR-Posting-Host: 12.227.130.93
> | From: "=?Utf-8?B?TWlrZUg=?=" <MikeH@.discussions.microsoft.com>
> | Subject: Collation and Win2K3 Clustered Environment.
> | Date: Wed, 16 Feb 2005 06:39:08 -0800
> | Lines: 51
> | Message-ID: <87A19939-8444-4CEC-BBB4-ED092DFFD4D7@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.clustering
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> | Path: TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFT NGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.clustering:3114
> | X-Tomcat-NG: microsoft.public.sqlserver.clustering
> |
> | This past weekend I was challenged a little in resolving what I hoped was
> a
> | simple collation issue. We are running Win2K3 Ent. Clustering Services,
> SQL
> | Server 2000 Enterprise, b.8.00.760.
> |
> | On Friday, 2.11, a user migrated an application to this new clustered
> setup
> | and immediately received the infamous 446 collation error.
> |
> | I spent most of Friday evening and all day Saturday reviewing support
> topics
> | and news groups. I found that there was 1 issue that could be affecting
> us -
> | the build of SQL Server for Win2K3 Ent. Clustering is subtly different
> than
> | for Win2KAS Clustering - and all of my research came back to one thing:
> Run
> | rebuildm.exe and set the collation of this instance to be the same as the
> | existing development/production environment. The default setup on the
> cluster
> | was different than the previous production setup, as well as different
> than
> | the current development environment.
> |
> | So, I backed everyone's database up, then the master objects, shut the
> | instance down, executed rebuild and set the collation to what I needed it
> to
> | be.
> |
> | When I brought this user's database online - the same exact error occurs.
> |
> | Prior to doing this, here is what we were faced with:
> | Development / Previous Production: Server=Win2K, SQL=SQL Server 2000
> | Enterprise w/Collate=SQL_Latin1_General_CP1_CI_AS.
> |
> | The new clustered SQL=SQL Server Enterprise,
> w/Collate=Latin1_General_CI_AI.
> |
> | The database/application in question, at the procedure where we receive
> the
> | collation error, basically calls a function that creates a temp table,
> then
> | another that pulls data for a report - however, the data is collected as
> a
> | JOIN on this tempdb temp object and a series of Views the programmer
> | previously setup. These views in turn hit various other static tables as
> well.
> |
> | We were thinking that because of the collation difference on the new
> Win2K3
> | setup, as well as Collation/Locale settings differences with Win2K3
> | Clustering, we should at a minimum change the instance to match the
> | SQL_Latin1, etc. collation of development. This however, has not solved
> the
> | problem.
> |
> | At this juncture, the Win2K3 Clustered server has the collation
> | SQL_Latin1_General_CP1_CI_AI, and the development environment (as well as
> | their current production environment, which is 2KAS nonclustered) is
> | SQL_Latin1_General_CP1_CI_AS... The only difference in the two right now
> is
> | the accent sensitivity - but this should not be the issue.
> |
> | If anyone else out there has any feedback, I'd be grateful for your time.
> |
> | Thanks...
> |
> | mhamilton"AT"nusoftsolutions"DOT"com
> |
>

Codepage 932 is not supported by the Java environment.

I have a JDBC type 4 driver, connecting to a Japanese SQL Server 2000. The connection gives this SQL exception:

SQLException: Codepage 932 is not supported by the Java environment.

SQL State: null

SQL Code: 0

This same software has been in use and working just fine for over 2 years with other servers. Does anyone know the solution to this problem?

Thanks!

pds2

What JDBC driver are you using?

The exception "Codepage 932 is not supported by the Java environment." doesn't sound like it's coming from SQL Server so the driver is likely raising it based on server configuration.

Try checking the database collation on SQL Server. That may have changed.

If this new SQL Server is running on a different machine is it possible that the Windows OS is running with a different locale?

Hope this helps,

Vaughn

|||

Hi,

The Microsoft SQL Server 2005 JDBC Driver relies on nio Charset support in the JVM to map from CHAR/VARCHAR/TEXT values with SQL collations to Java String instances. To do that, it needs to have charsets.jar, provided by your JVM vendor, installed and accessible via your application's classpath. Some JVM vendors choose not install charsets.jar, depending on what languages are supported by the host operating system at the time when the JVM is installed. So you may need to install charsets.jar separately.

For further information, please refer to:

http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html

If you have charsets.jar installed and are still seeing this issue, please reply to this thread and I'll attempt to diagnose the issue further.

Thank you,

--David

|||

This fixed the problem! Many thanks!

pds2

|||

Hi David,

I have same error message from running agent on Domino server 7 tried to connect to SQL 2005 as:

java.lang.NoClassDefFoundError:java/nio/charset/Charset

at com.microsoft.sqlserver.jdbc.SQLCollation.readCollation

at com.microsoft.sqlserver.jdbc.SQLCollation.<init>

at com.microsoft.sqlserver.jdbc.IOBuffer.processEnvChange

at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets

at com.microsoft.sqlserver.jdbc.SQLServerConnection.processLogon

...

at java.sql.DriverManager.getConnection(DriverManager.java:539)

at java.sql.DriverManager.getConnection(DriverManager.java:211)

...

And I had installed j2sdk1.4.2_13 from Sun, and checked the charsets.jar is in place in c:\j2sdk1.4.2_13\jre\lib,

All the code with old three jar files were running well with SQL 2000 server before, after the harware failure on that server, we are now with SQL 2005 server, all the agents connected to it changed to new JDBC driver and new jar - sqljdbc.jar are not working at all becuase of this problem...

I had sqljdbc.jar in classpath too, here we are in US (enu). I don't know what else I 've under looked?

Thanks for your help.

Evelyn

|||

Instead of using MS JDBC driver1.1, downloaded jTDS jdbc driver solved the problem!

CmdExec jobs run in non-admin Windows accounts

I am attempting to tighten the security of our MSSQL environment in a number
of ways and one of these is to run scheduled CmdExec jobs via a non-admin
Windows account. Alas, I cannot get this to work correctly.
I created a credential "abc_job" based on a non-admin Windows domain account
"dom01\abc" in a global group.
I assigned permission for "log on as a batch job" to the global group.
I created a proxy "abc_prox", assigned it to the credential and set it to
active for CmdExec.
I gave access to the proxy for a MSSQL account "xyz" (non sysadmin).
I created a test job and gave ownership of the job to the "xyz" MSSQL account.
The job only has one step and the step runs as proxy "abc_prox".
The job is one line: g:\hjk\test.bat > g:\hjk\test.out
The batch file consists of 5 lines:
chdir /D g:\hjk
whoami
net time
ping gh234test
dir
When I start the job, only the chdir and dir commands succeed. The other 3
lines return "access is denied". However when I remote term to the SQL
Server machine as "dom01\abc" and run the batch file in a command prompt
window it succeeds.
What am I missing?forgot to mention, I also assigned the "xyz" MSSQL account to the
SQLAgentUserRole in the msdb database.

CmdExec jobs run in non-admin Windows accounts

I am attempting to tighten the security of our MSSQL environment in a number
of ways and one of these is to run scheduled CmdExec jobs via a non-admin
Windows account. Alas, I cannot get this to work correctly.
I created a credential "abc_job" based on a non-admin Windows domain account
"dom01\abc" in a global group.
I assigned permission for "log on as a batch job" to the global group.
I created a proxy "abc_prox", assigned it to the credential and set it to
active for CmdExec.
I gave access to the proxy for a MSSQL account "xyz" (non sysadmin).
I created a test job and gave ownership of the job to the "xyz" MSSQL accoun
t.
The job only has one step and the step runs as proxy "abc_prox".
The job is one line: g:\hjk\test.bat > g:\hjk\test.out
The batch file consists of 5 lines:
chdir /D g:\hjk
whoami
net time
ping gh234test
dir
When I start the job, only the chdir and dir commands succeed. The other 3
lines return "access is denied". However when I remote term to the SQL
Server machine as "dom01\abc" and run the batch file in a command prompt
window it succeeds.
What am I missing?forgot to mention, I also assigned the "xyz" MSSQL account to the
SQLAgentUserRole in the msdb database.

CmdExec jobs run in non-admin Windows accounts

I am attempting to tighten the security of our MSSQL environment in a number
of ways and one of these is to run scheduled CmdExec jobs via a non-admin
Windows account. Alas, I cannot get this to work correctly.
I created a credential "abc_job" based on a non-admin Windows domain account
"dom01\abc" in a global group.
I assigned permission for "log on as a batch job" to the global group.
I created a proxy "abc_prox", assigned it to the credential and set it to
active for CmdExec.
I gave access to the proxy for a MSSQL account "xyz" (non sysadmin).
I created a test job and gave ownership of the job to the "xyz" MSSQL account.
The job only has one step and the step runs as proxy "abc_prox".
The job is one line: g:\hjk\test.bat > g:\hjk\test.out
The batch file consists of 5 lines:
chdir /D g:\hjk
whoami
net time
ping gh234test
dir
When I start the job, only the chdir and dir commands succeed. The other 3
lines return "access is denied". However when I remote term to the SQL
Server machine as "dom01\abc" and run the batch file in a command prompt
window it succeeds.
What am I missing?
forgot to mention, I also assigned the "xyz" MSSQL account to the
SQLAgentUserRole in the msdb database.

CmdExec and Environment

Unfortunately several of my sql users need tot run cmdexe jobs
(dts-packages). To keep them from totally destroying my server I
configured a proxy account with not to much rights on the files system.
For each virtual server I created a separate temp dir for the proxy user.
when a cmdexec job is run the %temp% %tmp% point to the tempdir which
belong to the cluster service account. Now I noticed a Environment
REG_MULTI_SZ key for the sql and sqlagent services (\hkey local
machine\...\/services\mssql$instance). This key contains a full set of
environment vars, but is not wel documented (no hits on google).
Is this, a standard reg key for services, or something special for sql
and sqlagent or something special for a clustered sql and sqlagent
service? I want to temper with the %temp% and %tmp%.
Hans
Hans de Bruin wrote:
> Unfortunately several of my sql users need tot run cmdexe jobs
> (dts-packages). To keep them from totally destroying my server I
> configured a proxy account with not to much rights on the files system.
> For each virtual server I created a separate temp dir for the proxy user.
> when a cmdexec job is run the %temp% %tmp% point to the tempdir which
> belong to the cluster service account. Now I noticed a Environment
> REG_MULTI_SZ key for the sql and sqlagent services (\hkey local
> machine\...\/services\mssql$instance). This key contains a full set of
> environment vars, but is not wel documented (no hits on google).
> Is this, a standard reg key for services, or something special for sql
> and sqlagent or something special for a clustered sql and sqlagent
> service? I want to temper with the %temp% and %tmp%.
>
This is something special for clustering. Just before the sqlserver or
sqlserver agent service starts ResrcMon writes the envrionment to this
key. Any manual made changes are overwriten.
When DTSRun can't write to the \documents and
setting\clusterserviceaccount\local\temp it tries to write in
c:\winows\temp.
Hans
|||When using the Proxy Account both CmdExec and xp_cmdshell call the Win32 API
LogonUser
http://msdn.microsoft.com/library/de.../logonuser.asp
As dwLogonType it uses LOGON32_LOGON_BATCH
As dwLogonProvider is uses LOGON32_PROVIDER_DEFAULT
After which they call the Win32 API CreateProcessAsUser
http://msdn.microsoft.com/library/de...cessasuser.asp
However CreateProcessAsUser does not load the specified user's profile into
the HKEY_USERS registry key. Therefore, to access the information in the
HKEY_CURRENT_USER registry key and if the lpEnvironment parameter is NULL,
the new process inherits the environment of the calling process.
CreateProcessAsUser does not automatically modify the environment block to
include environment variables specific to the user represented by hToken.
For example, the USERNAME and USERDOMAIN variables are inherited from the
calling process if lpEnvironment is NULL. It is your responsibility to
prepare the environment block for the new process and specify it in
lpEnvironment.
So what you get is the enviroment of the service account.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Hans de Bruin" <invalid@.invalid> wrote in message
news:1120486047.358052@.aquila.amc.uva.nl...
> Hans de Bruin wrote:
> This is something special for clustering. Just before the sqlserver or
> sqlserver agent service starts ResrcMon writes the envrionment to this
> key. Any manual made changes are overwriten.
> When DTSRun can't write to the \documents and
> setting\clusterserviceaccount\local\temp it tries to write in
> c:\winows\temp.
> --
> Hans

ClusterService Log On Account and SQL2000

It is my understanding that this Active Directory account takes on the
role(s) of SQL's BuiltIn Administrator in a clustered environment.
Should the ClusterService Log On account password be reset in AD, without
reseting in the properties tab for the service on the physical nodes cluster
fail overs can still occur because the ClusterService has already been
started. BUT, what activity in SQL2000 could the AD account be doing on
behalf of the SQL BuiltIn Administrator account that would affect the
cluster and initiate a failover if it could not authenticate on the Domain?
Dave
That is not right. By default (God, I hate Microsoft's defaults), the
Cluster Service MUST BE a member of the Local Administrators group on each
cluster node, by which it gains access to the SQL Server installations
through the default BUILTIN\Administrators membership to the SQL Server
system admin default server role.
If you follow the security best practices, and you should, you will remove
the BUILTIN\Administrators group for the installation; however, the Cluster
Service account will still need access to run the resource monitor "Is
Alive" check, which, in the case for the SQL Server resource, is nothing but
the SELECT @.@.SERVERNAME query; thus, the Cluster Service account merely
needs access to the installation, but no special rights beyond this, as the
guest database user in the master database has permissions to execute this
query.
Sincerely,
Anthony Thomas

"David Currie" <decurrie@.rogers.com> wrote in message
news:%23aT3qmQBHHA.204@.TK2MSFTNGP04.phx.gbl...
> It is my understanding that this Active Directory account takes on the
> role(s) of SQL's BuiltIn Administrator in a clustered environment.
> Should the ClusterService Log On account password be reset in AD, without
> reseting in the properties tab for the service on the physical nodes
cluster
> fail overs can still occur because the ClusterService has already been
> started. BUT, what activity in SQL2000 could the AD account be doing on
> behalf of the SQL BuiltIn Administrator account that would affect the
> cluster and initiate a failover if it could not authenticate on the
Domain?
> Dave
>

Clustering with W2K3 and SQL 2005 (64bit) - best practice setup

Hi
I'm a little confused how best to setup a new 2005 deployment. I'm
moving from a 2000 environment, which used Legato's AAM software to
support failover. The new environment will use MS clustering.
The 2000 setup has multiple instances on each node, and each instance
can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
instance has to have it's own 'virtual server'. So, in this setup,
named instances seem a bit redundant, since you can name the virtual
server. EG Why use Server1\Inst1, Server2\Inst2, when
Server1\<default>, Server2\<default> is just as informative
So, my questions are: 1) is it good practice to use named instances in
a clustered setup;
and 2) what is the rationale behind restricting a virtual server to a
single instance
Thanks.
You only get one default instance per cluster, not per virtual server.
Personally, I only use named instances to avoid name style confusion.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"steve" <stevester@.freeuk.com> wrote in message
news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
> Hi
> I'm a little confused how best to setup a new 2005 deployment. I'm
> moving from a 2000 environment, which used Legato's AAM software to
> support failover. The new environment will use MS clustering.
> The 2000 setup has multiple instances on each node, and each instance
> can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
> instance has to have it's own 'virtual server'. So, in this setup,
> named instances seem a bit redundant, since you can name the virtual
> server. EG Why use Server1\Inst1, Server2\Inst2, when
> Server1\<default>, Server2\<default> is just as informative
> So, my questions are: 1) is it good practice to use named instances in
> a clustered setup;
> and 2) what is the rationale behind restricting a virtual server to a
> single instance
> Thanks.
|||On 3 Dec, 14:23, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> You only get one default instance per cluster, not per virtual server.
> Personally, I only use named instances to avoid name style confusion.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
> "steve" <steves...@.freeuk.com> wrote in message
> news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
>
>
>
>
> - Show quoted text -
Thanks Geoff. So I can't use deafult instances with each additional
virtual server.
I'm still puzzled why you can only have one instance per virtual
server tho. - seems overly restrictive.
|||It has to do with how SQL organizes binaries for different instances. Or
mor accurately, how multiple instances were handled in SQL 2000.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"steve" <stevester@.freeuk.com> wrote in message
news:1a8e02f1-ca6b-44b3-84ee-b0589802b2c8@.j20g2000hsi.googlegroups.com...
> On 3 Dec, 14:23, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Thanks Geoff. So I can't use deafult instances with each additional
> virtual server.
> I'm still puzzled why you can only have one instance per virtual
> server tho. - seems overly restrictive.
|||"steve" <stevester@.freeuk.com> wrote in message
news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...

> The 2000 setup has multiple instances on each node, and each instance
> can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
> instance has to have it's own 'virtual server'. So, in this setup,
> named instances seem a bit redundant, since you can name the virtual
> server. EG Why use Server1\Inst1, Server2\Inst2, when
> Server1\<default>, Server2\<default> is just as informative
Each virtual server must be an instance. You can only have one default
instance per cluster and the rest have to be named instances.

> So, my questions are: 1) is it good practice to use named instances in
> a clustered setup;
You should only used named instances in a cluster. There are some known
issues around patching that can cause problems, for example, if you service
pack a named instance before the default.

> and 2) what is the rationale behind restricting a virtual server to a
> single instance
Each instance requires its own resources, thus, each requires its own
virtual server.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Dec 10 - 13 in Denver
Jan 18 - 31 in Denver
|||Thanks for your answers - very helpful.
Steve

Clustering Virtual vs Instance

I successfully installed a SQL Virtual Server and a SQL Instance on a
Clustered Environment. Is there a limitation as to the number of additional
Vitual or Instances I can add. Also, what would be considering best
practice? Virtual or Instance?
Thank You in Advance!
Drake Teran
In a cluster, Virtual Server = Instance. YOu create a enw instance, you
create the Virtual Server to install it into. They are one and the same in
a cluster. You get up to 16 instances in a cluster.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Admiral" <admiral@.blackopsplatoon.com> wrote in message
news:u62RalJ5FHA.3388@.TK2MSFTNGP11.phx.gbl...
>I successfully installed a SQL Virtual Server and a SQL Instance on a
>Clustered Environment. Is there a limitation as to the number of
>additional Vitual or Instances I can add. Also, what would be considering
>best practice? Virtual or Instance?
> Thank You in Advance!
> Drake Teran
>
|||When creating the Virtual Server/ Instance. I was able to call it a single
name "ExampleSQL", but the next instance created I had to name it
"ExampleSQL2/SQL". For all SQL vitual servers/instances creating from this
point forward require the "ExampleSQL2/SQL" convention?
Thanks in Advance
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:e2qJJAK5FHA.1464@.tk2msftngp13.phx.gbl...
> In a cluster, Virtual Server = Instance. YOu create a enw instance, you
> create the Virtual Server to install it into. They are one and the same
> in a cluster. You get up to 16 instances in a cluster.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "Admiral" <admiral@.blackopsplatoon.com> wrote in message
> news:u62RalJ5FHA.3388@.TK2MSFTNGP11.phx.gbl...
>
|||Correct. Each cluster can handle up to 16 instances - 1 default plus 15
named or 16 named (no default).
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Admiral" <admiral@.blackopsplatoon.com> wrote in message
news:uYW4WbK5FHA.1420@.TK2MSFTNGP09.phx.gbl...
> When creating the Virtual Server/ Instance. I was able to call it a
> single name "ExampleSQL", but the next instance created I had to name it
> "ExampleSQL2/SQL". For all SQL vitual servers/instances creating from
> this point forward require the "ExampleSQL2/SQL" convention?
> Thanks in Advance
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
> news:e2qJJAK5FHA.1464@.tk2msftngp13.phx.gbl...
>
|||Thank You!
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uYZ5FlK5FHA.3544@.TK2MSFTNGP09.phx.gbl...
> Correct. Each cluster can handle up to 16 instances - 1 default plus 15
> named or 16 named (no default).
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Admiral" <admiral@.blackopsplatoon.com> wrote in message
> news:uYW4WbK5FHA.1420@.TK2MSFTNGP09.phx.gbl...
>

Clustering SQL Servers in a Workgroup

I have setup a couple of SQL Server 2 node clusters in the past and was
always in a domain environment. I now have to setup a 2 node cluster in a
none domain workgroup environment if anyone has any tips I would appreciate
the advice.
Thanks,
Andrew
It's not supported. You need a domain.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"chabotwvu" <chabotwvu@.discussions.microsoft.com> wrote in message
news:C64FA1A9-86BC-4438-9A66-809EF466883B@.microsoft.com...
I have setup a couple of SQL Server 2 node clusters in the past and was
always in a domain environment. I now have to setup a 2 node cluster in a
none domain workgroup environment if anyone has any tips I would appreciate
the advice.
Thanks,
Andrew

Clustering or log shipping MS SQL 2000?

Our current SAP production environment consists of a window 2000 advanced
server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
server which contains an exact copy of the production database which is
up-to-date all the time during the day.
I started looking into log shipping but it appears there will be some down
time when the transaction logs are shipped from one sql server to the second
sql server. If the second sql server takes 10 minutes to apply the
transaction logs then the database is unavailable for that time period. Are
there any other options? What are other Basis admins doing? Are they using
Microsoft Clustering services to replicate the database? Or using SAN
imaging technology to replicate the data to another server?
Please advise,
Clustering won't get you there...its a high-availability solution, not
distributed processing.
The requirement of near-time data pretty much says you are looking at
transactional replication, or a 3rd party utility.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Chris,
There are several SAN Solutions that accomplish exactly what you want. This
is probably the way to go, although expensive.
-- Bill
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||replication is ideal for this. Some SAN solutions allow you to do this sort
of a thing but they tend to be very expensive.
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
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
> Our current SAP production environment consists of a window 2000 advanced
> server and MS SQL 2000 with SAP 4.7. We would like to setup a reporting
> server which contains an exact copy of the production database which is
> up-to-date all the time during the day.
>
> I started looking into log shipping but it appears there will be some down
> time when the transaction logs are shipped from one sql server to the
> second sql server. If the second sql server takes 10 minutes to apply the
> transaction logs then the database is unavailable for that time period.
> Are there any other options? What are other Basis admins doing? Are they
> using Microsoft Clustering services to replicate the database? Or using
> SAN imaging technology to replicate the data to another server?
>
> Please advise,
>
|||Would Transactional Replication that is built into SQL 2000 work for this?
Or is this log shipping?
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
> replication is ideal for this. Some SAN solutions allow you to do this
> sort of a thing but they tend to be very expensive.
> --
> 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
>
> "Chris T." <tatroc@.donotspam.gmail.com> wrote in message
> news:%23X3FDSCMHHA.5104@.TK2MSFTNGP06.phx.gbl...
>
|||Transactional repl.
Log shipping is not going to give you the up to date you are looking for AND
the ability to use it as a reporting server. Either one, not both
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message
news:OH%23EOy0MHHA.1252@.TK2MSFTNGP02.phx.gbl...
> Would Transactional Replication that is built into SQL 2000 work for this?
> Or is this log shipping?
>
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23U3jCBNMHHA.448@.TK2MSFTNGP04.phx.gbl...
>

Clustering H.E.L.P.

Hi,
I want to test the clustering environment before implementing the same on
production servers. The resources i have with me are high end ( p4 2G ,
512MB RAM ) personal computers. I can install 2k3 on two systems .. what do
i use for "shared storage".. can i use the shared drive of another desktop
computer on the same network as "shared disk array"... please help me out as
i have to give a presentation regarding the same...
Regards,
Navket Singh Naru
DBA
To be supported, a cluster has to be sold as a cluster solution. You cannot
just put pieces together as a cluster and have it supported as a cluster by
Microsoft.. With that said, the shared dirve will have to be a physical
drive that can be shared between the computers. It cannot be the shared
drive on a remote computer. The drive will have to be seen as an attached
drive byt the cluster service or it will not use it.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi,
I am going to start with "putting the pieces" together and making them work before i can go ahead and play around with our on site production servers. OFF SITE i have to come up with some contraptions that "works" as a cluster solution. and by doing this
i become more familiar with the steps.
So is there an other way to set up clustering .. by putting the Pieces Together ... the problem is what pieces ?
Navket Singh
|||If all you are looking for is a demo or training aid, you can build a
CheapCluster(TM).
Take any two machines P-II 400 or better, plug an extra NIC and a SCSI
adapter into each. Connect a SCSI drive or two in an external storage
array, load the OS, configure as a cluster and go. It won't be very stable
and it is completely unsupported, but it makes a great training and demo
tool. Do NOT attempt to run any real work on such a system.
Some people use VMWare to build a virtual cluster, but I haven't tried that
myself.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"DBA76" <navket.naru@.sdiindia.com> wrote in message
news:06A2D787-8415-4D60-BB03-814091D4F756@.microsoft.com...
> Hi,
> I am going to start with "putting the pieces" together and making them
work before i can go ahead and play around with our on site production
servers. OFF SITE i have to come up with some contraptions that "works" as a
cluster solution. and by doing this i become more familiar with the steps.
> So is there an other way to set up clustering .. by putting the Pieces
Together ... the problem is what pieces ?
> Navket Singh
|||You may wish to register for the Virtual Server 2005 Beta program. With this product you can simulate a W2K3 Server Cluster. Although it isn't a replacement for hardware in a production environment it may help you get a better understanding off what har
dware devices you'll need and how clustering works. You can run it on almost any PIII/PIV/Xeon single or multi-processor server.
http://www.microsoft.com/windowsserv...r/default.mspx
|||"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:OtvOymcPEHA.3476@.tk2msftngp13.phx.gbl...
> If all you are looking for is a demo or training aid, you can build a
> CheapCluster(TM).
> Take any two machines P-II 400 or better, plug an extra NIC and a SCSI
> adapter into each. Connect a SCSI drive or two in an external storage
> array, load the OS, configure as a cluster and go. It won't be very
stable
> and it is completely unsupported, but it makes a great training and demo
> tool. Do NOT attempt to run any real work on such a system.
>
I've done exactly this for training. Two P-II 400 systems, 2 Nics in each,
Adaptec 2940 in each and a bunch of 4GB disks in an external box connected
to both adapters. Just have to be careful about powering up nodes until the
clustering software is setup.

> Some people use VMWare to build a virtual cluster, but I haven't tried
that
> myself.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "DBA76" <navket.naru@.sdiindia.com> wrote in message
> news:06A2D787-8415-4D60-BB03-814091D4F756@.microsoft.com...
> work before i can go ahead and play around with our on site production
> servers. OFF SITE i have to come up with some contraptions that "works" as
a
> cluster solution. and by doing this i become more familiar with the steps.
> Together ... the problem is what pieces ?
>
|||For training, demo, support purposes, one could setup a cluster using Virtual Server 2005. You are in luck as recently a whitepaper to setup a cluster using Virtual Server
2005 is published. Here is the link
Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node Microsoft Windows Server 2003 Cluster
http://www.microsoft.com/technet/pro...y/cvs2005.mspx
On my laptop that has Windows XP Pro, I have a Win2K3 DC and two Win2K3 member servers configured as a two node cluster using Virtual Server 2005. Yeah, Virtual
Server 2005 is not supported on XP but I am using for testing and not production. Infact I was able to install SQL Server 2000 clustered instance and SP3a on the virtual
cluster without any issues.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Clustering and SA Role

Sorry for the re-post.
In a clustered SQL Server 2005 environment you must assign SQL Server, Agent
and Full Text Search to domain groups. These groups then appear in the Sys
Admin fixed role. With that, anyone who can add members to groups in the
domain can also become SQL Server SAs. How can this be prevented? I don't
think anyone with ability/access to add members to groups (even domain
admins) should be allowed to automatically make him/herself a SQL SA be
inheritance.
Hi
It comes down to processes within your organization and also how you secure
your AD.
You can grant someone to only manage objects in a certain tree, so not
giving them rights to the SQL Server accounts that should be in their own
tree would be the correct way of doing it.
Do you trust the same person not to give themselves Enterprise Admin rights
in the domain?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jay" <msnews.microsoft.com> wrote in message
news:uf6d0$L6FHA.1148@.tk2msftngp13.phx.gbl...
> Sorry for the re-post.
> In a clustered SQL Server 2005 environment you must assign SQL Server,
> Agent
> and Full Text Search to domain groups. These groups then appear in the
> Sys
> Admin fixed role. With that, anyone who can add members to groups in the
> domain can also become SQL Server SAs. How can this be prevented? I
> don't think anyone with ability/access to add members to groups (even
> domain admins) should be allowed to automatically make him/herself a SQL
> SA be inheritance.
>
>
|||I guess the issue is that in SQL2000 one could remove local admin group from
the sysadmin role, thus preventing the server admin from easily and
legitimately getting into SQL Server. So why can't we have that in SQL2005?
In practice, of course, I bet in many places one would find that the
accounts of the DBAs are placed into a group and that group is granted
access to SQL Server. So if a server admin really wants, he can add himself
to that group, thus gaining full access to SQL Server. So in the end, it
does come down to trust. Trust for sure simplifies management in many
scenarios. Without trust, one would have to go to excessive length to get
things down or prevent things from happening. And in most places, I'd say if
you don't have trust, you have a bigger problem than keeping the server
admin out of SQL Server.
Nevertheless it's nice to, at least, have the option available to keep the
server admin out, if necessary. Unfortunately, the cluster domain groups
required in SQl2005 are not thoroughly documented in current SQL2005 BOL. I
underdstand that the December BOL refresh will have more materials on these
groups. I hope it can shed some light on the issue being discussed here.
Linchi
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:Ok%23Y3jN6FHA.2816@.tk2msftngp13.phx.gbl...
> Hi
> It comes down to processes within your organization and also how you
> secure your AD.
> You can grant someone to only manage objects in a certain tree, so not
> giving them rights to the SQL Server accounts that should be in their own
> tree would be the correct way of doing it.
> Do you trust the same person not to give themselves Enterprise Admin
> rights in the domain?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Jay" <msnews.microsoft.com> wrote in message
> news:uf6d0$L6FHA.1148@.tk2msftngp13.phx.gbl...
>
|||You do have to remember too that Domain Admins, Enterprise Admins, User
Admins, and OU Admins have the ability to reset the passwords to user
accounts in the AD as well as add users to Global and Resource (Domain
Local?) Groups. So, again, it comes down to trust . . . and audits.
It helps if your Domain/Enterprise Administrators, Server Administrators,
Security Administrators, AD Administrators, Exchange Administrators, Web
Server Administrators, Application Server Administrators, Message Queue
Administrators, and SQL Server Administrators, etc., etc., etc., all be
managed by separate groups by managers of equal rank, all with elevated
privileges, all auditing the activities of the other groups: peer review,
within and throughout the organization to provide checks and balances to the
Change Control Process.
Sincerely,
Anthony Thomas

"Linchi Shea" <linchi_shea@.NOSPAMml.om> wrote in message
news:u3MQcxN6FHA.2888@.tk2msftngp13.phx.gbl...
> I guess the issue is that in SQL2000 one could remove local admin group
from
> the sysadmin role, thus preventing the server admin from easily and
> legitimately getting into SQL Server. So why can't we have that in
SQL2005?
> In practice, of course, I bet in many places one would find that the
> accounts of the DBAs are placed into a group and that group is granted
> access to SQL Server. So if a server admin really wants, he can add
himself
> to that group, thus gaining full access to SQL Server. So in the end, it
> does come down to trust. Trust for sure simplifies management in many
> scenarios. Without trust, one would have to go to excessive length to get
> things down or prevent things from happening. And in most places, I'd say
if
> you don't have trust, you have a bigger problem than keeping the server
> admin out of SQL Server.
> Nevertheless it's nice to, at least, have the option available to keep the
> server admin out, if necessary. Unfortunately, the cluster domain groups
> required in SQl2005 are not thoroughly documented in current SQL2005 BOL.
I
> underdstand that the December BOL refresh will have more materials on
these[vbcol=seagreen]
> groups. I hope it can shed some light on the issue being discussed here.
> Linchi
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:Ok%23Y3jN6FHA.2816@.tk2msftngp13.phx.gbl...
own[vbcol=seagreen]
the[vbcol=seagreen]
SQL
>

Clustering

Can any one give me some idea regarding the major difference between working
in Clustering environment and Non Clustering environment with respect of SQL
SERVER.
Thanks
Joh hi,
The major difference is that you are able to run SQL in the second node,
even if the first had an enormous hardware error.
You can read in BOL the topic "Creating a Failover Cluster" as well as the
http://support.microsoft.com/default...b;en-us;260758 article
HTH
Andreas
"Joh" wrote:

> Can any one give me some idea regarding the major difference between working
> in Clustering environment and Non Clustering environment with respect of SQL
> SERVER.
> Thanks
>
>
|||Thanks Andreas,
one more question I have a two systems and I want to implement the
clustering so can you guide me like step by step installation as well as
which software I have to used for ... I am totally new in clustering.
Thanks
"Andreas Mavrogenis" <AndreasMavrogenis@.discussions.microsoft.com> wrote in
message news:12145165-29BC-4C66-A138-46E8598A72C4@.microsoft.com...[vbcol=seagreen]
> Joh hi,
> The major difference is that you are able to run SQL in the second node,
> even if the first had an enormous hardware error.
> You can read in BOL the topic "Creating a Failover Cluster" as well as the
> http://support.microsoft.com/default...b;en-us;260758 article
> HTH
> Andreas
> "Joh" wrote:
working[vbcol=seagreen]
SQL[vbcol=seagreen]
|||Hi, Joh
You will have lots of hours reading! Also there are specific training
courses for that reason.
http://www.microsoft.com/learning/training/default.asp
White Paper: Windows Server 2003 Server Cluster Architecture
http://www.microsoft.com/windowsserv...ercluster.mspx
Microsoft Cluster Service Installation Resources
http://support.microsoft.com/default...b;en-us;259267
Installation order for SQL Server 2000 Enterprise Edition on Microsoft
Cluster Server
http://support.microsoft.com/default...b;en-us;243218
HTH
Andreas
"Joh" wrote:

> Thanks Andreas,
> one more question I have a two systems and I want to implement the
> clustering so can you guide me like step by step installation as well as
> which software I have to used for ... I am totally new in clustering.
> Thanks
> "Andreas Mavrogenis" <AndreasMavrogenis@.discussions.microsoft.com> wrote in
> message news:12145165-29BC-4C66-A138-46E8598A72C4@.microsoft.com...
> working
> SQL
>
>
|||Thanks Andreas
"Andreas Mavrogenis" <AndreasMavrogenis@.discussions.microsoft.com> wrote in
message news:54E16DAB-F178-4195-BC09-73757E224BB9@.microsoft.com...
> Hi, Joh
> You will have lots of hours reading! Also there are specific training
> courses for that reason.
> http://www.microsoft.com/learning/training/default.asp
> White Paper: Windows Server 2003 Server Cluster Architecture
>
http://www.microsoft.com/windowsserv...ervercluster.m
spx[vbcol=seagreen]
> Microsoft Cluster Service Installation Resources
> http://support.microsoft.com/default...b;en-us;259267
> Installation order for SQL Server 2000 Enterprise Edition on Microsoft
> Cluster Server
> http://support.microsoft.com/default...b;en-us;243218
> HTH
> Andreas
>
> "Joh" wrote:
in[vbcol=seagreen]
node,[vbcol=seagreen]
the[vbcol=seagreen]
respect of[vbcol=seagreen]

Clustered Replication - Whose IP is It

I have a data warehouse transactional replication environment in which
we have muliple Publisher/Distributors(100+) and a single subscriber.
All Publishers and subscribers are SQL 2000.
We recently converted the subscriber box to a Win2003
Cluster.(Publishers are Win2K for the most part, there may be a couple
remaining NT machines)
The publishers are on a very large WAN and are replicating to a central
location. Because of the large WAN environment, there are a number of
network filters in place and traffic management is of the highest
concern.
Replication IS working. However, there is one anomoly that I would
like to know about (How to control/change).
Before the Cluster, replication was moving to the DNS IP of the single
subscriber. (lets call it .14)
When the cluster was installed the SQL Cluster was given the same IP
(.14). Each of the nodes were given an IP, .72 & .70 (.72 is the active
node)
Now as replication and snapshots occur it is happening between the
publisher and the .72 node.
Why is this happening and is there a way to control this?
Thanks Rum63
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Snapshots are running to a UNC file share based on the host node. You will
need to either snapshot to a clustered instance of a file share OR snapshot
to an FTP server (clustered or not is your choice).
Geoff N. Hiten
Microsoft SQL Server MVP
"rum63" <nospam@.devdex.com> wrote in message
news:eoS2N$WKFHA.3640@.TK2MSFTNGP12.phx.gbl...
>I have a data warehouse transactional replication environment in which
> we have muliple Publisher/Distributors(100+) and a single subscriber.
> All Publishers and subscribers are SQL 2000.
> We recently converted the subscriber box to a Win2003
> Cluster.(Publishers are Win2K for the most part, there may be a couple
> remaining NT machines)
> The publishers are on a very large WAN and are replicating to a central
> location. Because of the large WAN environment, there are a number of
> network filters in place and traffic management is of the highest
> concern.
> Replication IS working. However, there is one anomoly that I would
> like to know about (How to control/change).
> Before the Cluster, replication was moving to the DNS IP of the single
> subscriber. (lets call it .14)
> When the cluster was installed the SQL Cluster was given the same IP
> (.14). Each of the nodes were given an IP, .72 & .70 (.72 is the active
> node)
> Now as replication and snapshots occur it is happening between the
> publisher and the .72 node.
> Why is this happening and is there a way to control this?
> Thanks Rum63
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!