Default Collate Codes for SQL 7 and 2000

I am in the process of building a new sql 2000 server and will be transfering
a 2G database from a sql 7 server. I have already done this in development
and come across the collate problem where the 2000 version had a different
collate code than version 7, but both were installed with the default
settings.
I would like to know that the best options are, I assume I only have 2.
1. Make sure that the 2000 server is installed with the same collate code as
the sql 7 version.
2. Change all the collate codes when the sql 7 database has been restored.
Please can someone tell me which is the best option, and why the default
collate settings for the 2 versions are different, which causes all these
problems.
Many thanks - Richard
"Richard Badge" <Richard Badge@.discussions.microsoft.com> wrote in message
news:BC784CC8-6DAF-43AA-8116-D05E2D51A9BA@.microsoft.com...
> 1. Make sure that the 2000 server is installed with the same collate code
> as
> the sql 7 version.
You can do an upgrade in place and it will pick the same collation as 7.0.

> 2. Change all the collate codes when the sql 7 database has been restored.
> Please can someone tell me which is the best option,
The best is whichever your business needs say is the best. By moving to the
new collation, you will have better support for more things.
Read up on the collations and what they have to offer in the BOL. This
should help you with your decisions.

> and why the default collate settings for the 2 versions are different,
> which causes all these
> problems.
I can't speak for Microsoft, however, the new features and additions that
can be found in the newer collations give you more flexibility. If you go
all the way back to early versions of SQL Server, the default sequence was
code page 437 (US English). This was very limited in it's support for
other languages etc.
HTH
Rick Sawtell
MCT, MCSD, MCDBA

Default Collate Codes for SQL 7 and 2000

I am in the process of building a new sql 2000 server and will be transferin
g
a 2G database from a sql 7 server. I have already done this in development
and come across the collate problem where the 2000 version had a different
collate code than version 7, but both were installed with the default
settings.
I would like to know that the best options are, I assume I only have 2.
1. Make sure that the 2000 server is installed with the same collate code as
the sql 7 version.
2. Change all the collate codes when the sql 7 database has been restored.
Please can someone tell me which is the best option, and why the default
collate settings for the 2 versions are different, which causes all these
problems.
Many thanks - Richard"Richard Badge" <Richard Badge@.discussions.microsoft.com> wrote in message
news:BC784CC8-6DAF-43AA-8116-D05E2D51A9BA@.microsoft.com...
> 1. Make sure that the 2000 server is installed with the same collate code
> as
> the sql 7 version.
You can do an upgrade in place and it will pick the same collation as 7.0.

> 2. Change all the collate codes when the sql 7 database has been restored.
> Please can someone tell me which is the best option,
The best is whichever your business needs say is the best. By moving to the
new collation, you will have better support for more things.
Read up on the collations and what they have to offer in the BOL. This
should help you with your decisions.

> and why the default collate settings for the 2 versions are different,
> which causes all these
> problems.
I can't speak for Microsoft, however, the new features and additions that
can be found in the newer collations give you more flexibility. If you go
all the way back to early versions of SQL Server, the default sequence was
code page 437 (US English). This was very limited in it's support for
other languages etc.
HTH
Rick Sawtell
MCT, MCSD, MCDBA

Default Collate Codes for SQL 7 and 2000

I am in the process of building a new sql 2000 server and will be transfering
a 2G database from a sql 7 server. I have already done this in development
and come across the collate problem where the 2000 version had a different
collate code than version 7, but both were installed with the default
settings.
I would like to know that the best options are, I assume I only have 2.
1. Make sure that the 2000 server is installed with the same collate code as
the sql 7 version.
2. Change all the collate codes when the sql 7 database has been restored.
Please can someone tell me which is the best option, and why the default
collate settings for the 2 versions are different, which causes all these
problems.
Many thanks - Richard"Richard Badge" <Richard Badge@.discussions.microsoft.com> wrote in message
news:BC784CC8-6DAF-43AA-8116-D05E2D51A9BA@.microsoft.com...
> 1. Make sure that the 2000 server is installed with the same collate code
> as
> the sql 7 version.
You can do an upgrade in place and it will pick the same collation as 7.0.
> 2. Change all the collate codes when the sql 7 database has been restored.
> Please can someone tell me which is the best option,
The best is whichever your business needs say is the best. By moving to the
new collation, you will have better support for more things.
Read up on the collations and what they have to offer in the BOL. This
should help you with your decisions.
> and why the default collate settings for the 2 versions are different,
> which causes all these
> problems.
I can't speak for Microsoft, however, the new features and additions that
can be found in the newer collations give you more flexibility. If you go
all the way back to early versions of SQL Server, the default sequence was
code page 437 (US English). This was very limited in it's support for
other languages etc.
HTH
Rick Sawtell
MCT, MCSD, MCDBA

Decoded values in report

Hi,
I have a report generated from a dataset which has the state and county
codes. I have some other general purpose datasets which have the correspoding
county/state codes and descriptions. How do I link these to the report so
that I can see the descriptions instead of the code? I tried to drag the
description field onto the report, but it only pulls up the first value.
For example,
Folder (fldr) State (n_cd)
1234 2
4444 3
(Decode Dataset)
State Cd (n_cd) Description (n_desc)
2 FL
3 WA
When I drop n_desc onto the n_cd field of dataset 1, I get FL for all rows,
since it is picking up only the first row.
Please help.
Thanks,
ArshadMake sure it says =Fields!n_desc and not =First(Fields!n_desc)
regards,
Stas K.|||I did that and it gives the message: "....Report item expressions can only
refer to fields within the current data set scope, or if inside an aggregate,
the specified data set scope."
Thanks,
Arshad
"Sorcerdon" wrote:
> Make sure it says =Fields!n_desc and not =First(Fields!n_desc)
> regards,
> Stas K.
>|||Mr. Syed,
It is not possible to merge/link 2 datasets in a single report control
or lookup a value across datasets.
Ideally, you'd create a single dataset where the translation/decoding
of the state code to a description happens via a join between tables.
Andy Potter|||Thanks to all for your help. They need to make this more explicit in the
documentation!
"Potter" wrote:
> Mr. Syed,
> It is not possible to merge/link 2 datasets in a single report control
> or lookup a value across datasets.
> Ideally, you'd create a single dataset where the translation/decoding
> of the state code to a description happens via a join between tables.
> Andy Potter
>

Debugging T-SQL Codes

Hi,
How can I use query analyzer to debug my codes and stored procedures. I need
something like debug tools of VB(watching line by line execution). Are such
tools available for SQL server?
Thanks,
AminYes, for stored procedures., In Query Analyzer, Object Browser, right-click
the procedure and you'll find the debugger.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Amin Sobati" <amins@.morva.net> wrote in message
news:%23gTTEiECEHA.3788@.TK2MSFTNGP10.phx.gbl...
> Hi,
> How can I use query analyzer to debug my codes and stored procedures. I
need
> something like debug tools of VB(watching line by line execution). Are
such
> tools available for SQL server?
> Thanks,
> Amin
>|||In Query Analyzer, open the object browser. In the object
browser, go down to the stored procedures in a database,
select a stored procedure, right click and select debug.
-Sue
On Fri, 12 Mar 2004 19:12:08 +0430, "Amin Sobati"
<amins@.morva.net> wrote:

>Hi,
>How can I use query analyzer to debug my codes and stored procedures. I nee
d
>something like debug tools of VB(watching line by line execution). Are such
>tools available for SQL server?
>Thanks,
>Amin
>