Changing Collation SQL 2000 sp4

Hello
We just upgraded to SQL server 2000 sp3a from sp4 . Could the
collation
change upgrading to SP4 (from SQL_Latin1_General_CP1_CS_AS to
SQL_Latin1_General_CP1_CI_AS. Or can that only be changed on the
initial installation.
ThanksHi
"jsully79" wrote:

> Hello
> We just upgraded to SQL server 2000 sp3a from sp4 . Could the
> collation
> change upgrading to SP4 (from SQL_Latin1_General_CP1_CS_AS to
> SQL_Latin1_General_CP1_CI_AS. Or can that only be changed on the
> initial installation.
> Thanks
I have not know the collation change when applying the service pack. To do
for the whole system would have required alot of work. Are you asking about
a
specific database/column/setting?
John

Changing Collation SQL 2000 sp4

Hello
We just upgraded to SQL server 2000 sp3a from sp4 . Could the
collation
change upgrading to SP4 (from SQL_Latin1_General_CP1_CS_AS to
SQL_Latin1_General_CP1_CI_AS. Or can that only be changed on the
initial installation.
ThanksHi
"jsully79" wrote:
> Hello
> We just upgraded to SQL server 2000 sp3a from sp4 . Could the
> collation
> change upgrading to SP4 (from SQL_Latin1_General_CP1_CS_AS to
> SQL_Latin1_General_CP1_CI_AS. Or can that only be changed on the
> initial installation.
> Thanks
I have not know the collation change when applying the service pack. To do
for the whole system would have required alot of work. Are you asking about a
specific database/column/setting?
John

Changing Collation SQL 2000 sp4

Hello
We just upgraded to SQL server 2000 sp3a from sp4 . Could the
collation
change upgrading to SP4 (from SQL_Latin1_General_CP1_CS_AS to
SQL_Latin1_General_CP1_CI_AS. Or can that only be changed on the
initial installation.
Thanks
Hi
"jsully79" wrote:

> Hello
> We just upgraded to SQL server 2000 sp3a from sp4 . Could the
> collation
> change upgrading to SP4 (from SQL_Latin1_General_CP1_CS_AS to
> SQL_Latin1_General_CP1_CI_AS. Or can that only be changed on the
> initial installation.
> Thanks
I have not know the collation change when applying the service pack. To do
for the whole system would have required alot of work. Are you asking about a
specific database/column/setting?
John

Changes to Master/Target Server Configurations

I've installed SQL Server 2000 and applied SP3a. I see SP4 is available and fixes a lot of things. The only bit I am unsure about is section '5.3.2 Changes to Master/Target Server Configurations'

http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_5464_sql_server_agent_enhancements_705

"Before you apply SP4, you must complete several steps to upgrade your SQL Server 2000 master/target server configuration. The changes that are introduced with SP4 are not compatible with SQL Server 7.0 target servers, or with any servers not running SP3 or later. This is a change from the original SQL Server 2000 functionality. "

As I'm just starting out I don't even know what 'Master/Target Server' is. I'm only installing to my PC which is XP Pro SP2. Can I ignore this step and apply the patch or do I need to do as it states?

Thanks

SQL Server 2000 service pack 3 and 3a are twenty five .sql files Windows uses as needed, I have used them for all existing operating systems with minor problems with Windows 2000 standard server. I would say just run it and in SQL Server 2000 and below ignore most questions only answer those relevant to your situation and you will not run into problems with SQL Server. Hope this helps.

Changed Version of SQL Server

I have Windows 2000 Advanced Server with SQL Server 2000
with SP3A in a Active\Active Cluster.
When I loaded Windows 2000 SP4 on the server it changed
SQL Server 2000 version to "Microsoft SQL Server 2000 -
8.00.194 (Intel X86)".
If the Active (Node A)\ Active (Node B) cluster was moved
from original location could this change the SQL Server
version number. (Move Node A to Node B)
What could cause the version number to change within SQL
Server 2000. If the version is wrong is there away to
determine the version by SQL Server file dates?
Please help me resolve this issue.
Thanks,
Mark
weird normally the best way is to type the query below in Query Analyzer
which is determined by the version of SQLServr.exe.
SELECT @.@.VERSION
http://support.microsoft.com/default...b;en-us;321185
Although ocasionally (as with build 819 from
http://support.microsoft.com/default...b;en-us;826161) the real
version is not reflected as SQLServr.exe is not updated. In this case check
the registry @. HKLM\SOFTWARE\Microsoft\MSSQLServer\Hotfixes\0819
regards,
Andy.
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:024a01c48aea$87d32a80$a601280a@.phx.gbl...
>
> I have Windows 2000 Advanced Server with SQL Server 2000
> with SP3A in a Active\Active Cluster.
> When I loaded Windows 2000 SP4 on the server it changed
> SQL Server 2000 version to "Microsoft SQL Server 2000 -
> 8.00.194 (Intel X86)".
> If the Active (Node A)\ Active (Node B) cluster was moved
> from original location could this change the SQL Server
> version number. (Move Node A to Node B)
>
> What could cause the version number to change within SQL
> Server 2000. If the version is wrong is there away to
> determine the version by SQL Server file dates?
>
> Please help me resolve this issue.
> Thanks,
> Mark

Change the Delimiters

Does anyone know how to change the delimiters on SQL Server 2000 SP4 Client
software?
From " " to [ ] ?
For example:
"dbo"."myTable"
to
[dbo].[mytable]
Running the Client tools on Windows XP.
John
John;
Are you asking whether there is a tool to change the double quotation mark
delimiters used in a T-SQL script to the square bracket delimiters?
I'm not aware of any native SQL Server client tool for doing this. If I were
to do it, I'd just write a script to parse the T-SQL text and do the
replacement. Now, in its most general case, the problem may not be as
straightforward as it may appear. Consider the case where you have double
quotation marks embedded in a string constant and the case where you have
double quotation marks embedded in a delimited identifier.
But your particular situation could be very straightforward without any of
the annoying cases mentioned above, and thus a simple text editor
search/replace may suffice.
Linchi
"John Smith" <john9877798@.hotmail.com> wrote in message
news:lVC4f.5075$ns3.172063@.news20.bellglobal.com.. .
> Does anyone know how to change the delimiters on SQL Server 2000 SP4
> Client software?
> From " " to [ ] ?
> For example:
> "dbo"."myTable"
> to
> [dbo].[mytable]
> Running the Client tools on Windows XP.
> John
>
|||Of course, I should add that in my previous post, by 'text editor
search/replace', I was referring to doing this manually unless you have a
text editor that supports regular expression search and replace.
If you are interested, I can email you offline a Perl script that uses
recursive descent parsing to find all the delimiters in most general case.
The script can be easily modified to do the kind of replacement you want.
Again, if you are lucky that don't need to deal with any embedded double
quotation marks, you can write a much simpler script to look for pairs of
double quotation marks and do the replacement accordingly. This can be done
with a trivial regular expression.
Linchi
"Linchi Shea" <linchi_shea@.NOSPAMml.om> wrote in message
news:%23sVEr2s0FHA.1252@.TK2MSFTNGP09.phx.gbl...
> John;
> Are you asking whether there is a tool to change the double quotation mark
> delimiters used in a T-SQL script to the square bracket delimiters?
> I'm not aware of any native SQL Server client tool for doing this. If I
> were to do it, I'd just write a script to parse the T-SQL text and do the
> replacement. Now, in its most general case, the problem may not be as
> straightforward as it may appear. Consider the case where you have double
> quotation marks embedded in a string constant and the case where you have
> double quotation marks embedded in a delimited identifier.
> But your particular situation could be very straightforward without any of
> the annoying cases mentioned above, and thus a simple text editor
> search/replace may suffice.
> Linchi
> "John Smith" <john9877798@.hotmail.com> wrote in message
> news:lVC4f.5075$ns3.172063@.news20.bellglobal.com.. .
>

Change SQL 2000 Server 64bit collation

Please point me to the procedure for changing the collation sequence on 64bit
installation of SQL Server 2000 (SP4). I can't find anything in KB or BOL.
Thanks,
Tom
Hi
Collations are a different levels, so there is not one place you will need
to change it. Changing the Collation of 64bit SQL Server is no different to
changing it on 32bit SQL Server. If this is a fresh install and you don't
have any databases to change then the best option is probably to re-install.
You can use rebuildm.exe to change the master database with a different
collation. Each database can have the collation changed using the ALTER
DATABASE command, this will not change the collation of existing columns that
have been set to the original collation. To do that you will need to run a
script that uses the ALTER TABLE command. If you the column are indexes or a
primary key, or have Foreign Keys pointing to them, the constraint will need
to be dropped. There are many threads on this for example
http://tinyurl.com/ky3q
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
Other links that may be useful:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
John
"T Morris" wrote:

> Please point me to the procedure for changing the collation sequence on 64bit
> installation of SQL Server 2000 (SP4). I can't find anything in KB or BOL.
> Thanks,
> Tom
|||Since I didn't find Rebuildm.exe in the binn folder for the 64bit
installation I thought there might be a different procedure.
But per your email, I use the same procedure. And I must find the
rebuildm.exe program.
Am I correct?
Thanks,
Tom
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Collations are a different levels, so there is not one place you will need
> to change it. Changing the Collation of 64bit SQL Server is no different to
> changing it on 32bit SQL Server. If this is a fresh install and you don't
> have any databases to change then the best option is probably to re-install.
> You can use rebuildm.exe to change the master database with a different
> collation. Each database can have the collation changed using the ALTER
> DATABASE command, this will not change the collation of existing columns that
> have been set to the original collation. To do that you will need to run a
> script that uses the ALTER TABLE command. If you the column are indexes or a
> primary key, or have Foreign Keys pointing to them, the constraint will need
> to be dropped. There are many threads on this for example
> http://tinyurl.com/ky3q
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
> Other links that may be useful:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
> John
> "T Morris" wrote:
|||Hi
I usually favour re-install rather than rebuildm.exe and on the 32 bit
version it is in the ...\80\tools\binn directory.
John
"T Morris" wrote:
[vbcol=seagreen]
> Since I didn't find Rebuildm.exe in the binn folder for the 64bit
> installation I thought there might be a different procedure.
> But per your email, I use the same procedure. And I must find the
> rebuildm.exe program.
> Am I correct?
> Thanks,
> Tom
> "John Bell" wrote:

Change SQL 2000 Server 64bit collation

Please point me to the procedure for changing the collation sequence on 64bi
t
installation of SQL Server 2000 (SP4). I can't find anything in KB or BOL.
Thanks,
TomHi
Collations are a different levels, so there is not one place you will need
to change it. Changing the Collation of 64bit SQL Server is no different to
changing it on 32bit SQL Server. If this is a fresh install and you don't
have any databases to change then the best option is probably to re-install.
You can use rebuildm.exe to change the master database with a different
collation. Each database can have the collation changed using the ALTER
DATABASE command, this will not change the collation of existing columns tha
t
have been set to the original collation. To do that you will need to run a
script that uses the ALTER TABLE command. If you the column are indexes or a
primary key, or have Foreign Keys pointing to them, the constraint will need
to be dropped. There are many threads on this for example
http://tinyurl.com/ky3q
http://msdn.microsoft.com/library/d...y/en-us/arch...
Other links that may be useful:
http://msdn.microsoft.com/library/d...y/en-us/arch...
John
"T Morris" wrote:

> Please point me to the procedure for changing the collation sequence on 64
bit
> installation of SQL Server 2000 (SP4). I can't find anything in KB or BOL.
> Thanks,
> Tom|||Since I didn't find Rebuildm.exe in the binn folder for the 64bit
installation I thought there might be a different procedure.
But per your email, I use the same procedure. And I must find the
rebuildm.exe program.
Am I correct?
Thanks,
Tom
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Collations are a different levels, so there is not one place you will need
> to change it. Changing the Collation of 64bit SQL Server is no different t
o
> changing it on 32bit SQL Server. If this is a fresh install and you don't
> have any databases to change then the best option is probably to re-instal
l.
> You can use rebuildm.exe to change the master database with a different
> collation. Each database can have the collation changed using the ALTER
> DATABASE command, this will not change the collation of existing columns t
hat
> have been set to the original collation. To do that you will need to run a
> script that uses the ALTER TABLE command. If you the column are indexes or
a
> primary key, or have Foreign Keys pointing to them, the constraint will ne
ed
> to be dropped. There are many threads on this for example
> http://tinyurl.com/ky3q
> http://msdn.microsoft.com/library/d...y/en-us/arch...
> Other links that may be useful:
> http://msdn.microsoft.com/library/d...y/en-us/arch...
> John
> "T Morris" wrote:
>|||Hi
I usually favour re-install rather than rebuildm.exe and on the 32 bit
version it is in the ...\80\tools\binn directory.
John
"T Morris" wrote:
[vbcol=seagreen]
> Since I didn't find Rebuildm.exe in the binn folder for the 64bit
> installation I thought there might be a different procedure.
> But per your email, I use the same procedure. And I must find the
> rebuildm.exe program.
> Am I correct?
> Thanks,
> Tom
> "John Bell" wrote:
>

Change sort order for SQL 7 SP4

Is their a way to change the sort order. I have a backup
i need to restore, but it says the sort order is not
correct.
Thanks
RickRick,
With SQL 7, I think you'd have to re-install the server & specify the
appropriate sort-order during installation. I assume that you're restoring
to a different server than that from which the backup was taken, hence the
error message.
If you need to transfer a database to a server that you can't re-install,
with different language, sortorder, case sensitivity etc, I think you may
need to do the transfer using DTS or similar.
HTH
--
--
Kind Regards,
Robert A. Ellis, MCSD
Software Developer
"Rick" <rhollis@.fmtsd.com> wrote in message
news:18c501c35dd9$adfb9ba0$7d02280a@.phx.gbl...
> Is their a way to change the sort order. I have a backup
> i need to restore, but it says the sort order is not
> correct.
> Thanks
> Rick|||Hi Rick and Robert,
Actually you need to rebuild the master database (using rebuildm utility)
to change sort order in SQL Server 7.0. Doing this in effect will have a
newly built master database, so all your references to user databases,
logins etc will be lost.
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Change service account with SQL server 2000 sp4

I have secured our SQL 2000 server on a Windows 2003 server.
I deleted the builtin administrator as systemadminstrator.
Then changed to a new serviceaccount that is administrator on the machine.
It is a AD domain account.
I then changed all SQL jobs to the new account. Restarted the services.
After that I got the failure
"The job failed. Unable to determine if the owner (domain\username) of job
testjob has server access (reason: Could not obtain information about Window
s
NT group/user 'domain\username'. [SQLSTATE 42000] (Error 8198)). "
It is only the SQL jobs that fails.
any idea?
If I use a SQL admin account as sa the jobs works. But I want to have a
doaimn account for this.
We are running mixed mode and SP4 with latest hotfix.
Kind regards.your SQL Agent service is running under a local account ?
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:4783465E-2B9B-4D6E-83F4-D4346BAC1D36@.microsoft.com...
>I have secured our SQL 2000 server on a Windows 2003 server.
> I deleted the builtin administrator as systemadminstrator.
> Then changed to a new serviceaccount that is administrator on the machine.
> It is a AD domain account.
> I then changed all SQL jobs to the new account. Restarted the services.
> After that I got the failure
> "The job failed. Unable to determine if the owner (domain\username) of job
> testjob has server access (reason: Could not obtain information about
> Windows
> NT group/user 'domain\username'. [SQLSTATE 42000] (Error 8198)). "
> It is only the SQL jobs that fails.
> any idea?
> If I use a SQL admin account as sa the jobs works. But I want to have a
> doaimn account for this.
> We are running mixed mode and SP4 with latest hotfix.
> Kind regards.
>
>