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

Dedicated Database Connection

We are looking at ways to optimize our process for retrieving primary keys.
Currently, we are creating a new database call to get each ID we need. We
are considering the idea of keeping a database connection open with a single
responsibility of retrieving a new primary key. Can you provide me a
response to the following questions?:
Are there any timeouts on open connections to the database from within SQL
Server?
Can you think of negative impacts this could have on the database to have a
consistent open connections?newie wrote:
> We are looking at ways to optimize our process for retrieving primary
> keys. Currently, we are creating a new database call to get each ID
> we need. We are considering the idea of keeping a database
> connection open with a single responsibility of retrieving a new
> primary key. Can you provide me a response to the following
> questions?:
> Are there any timeouts on open connections to the database from
> within SQL Server?
> Can you think of negative impacts this could have on the database to
> have a consistent open connections?
Conistent open connections are the standard for many client-server
applications. Even something like IIS would likely use connection
pooling and keep a certain number of connections open. There is no
problem with an open connection. In fact, in most cases it can improve
application performance.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||take a look at connection pooling
http://sqlservercode.blogspot.com/
"newie" wrote:
> We are looking at ways to optimize our process for retrieving primary keys.
> Currently, we are creating a new database call to get each ID we need. We
> are considering the idea of keeping a database connection open with a single
> responsibility of retrieving a new primary key. Can you provide me a
> response to the following questions?:
> Are there any timeouts on open connections to the database from within SQL
> Server?
> Can you think of negative impacts this could have on the database to have a
> consistent open connections?
>sql

Dedicated Database Connection

We are looking at ways to optimize our process for retrieving primary keys.
Currently, we are creating a new database call to get each ID we need. We
are considering the idea of keeping a database connection open with a single
responsibility of retrieving a new primary key. Can you provide me a
response to the following questions?:
Are there any timeouts on open connections to the database from within SQL
Server?
Can you think of negative impacts this could have on the database to have a
consistent open connections?
newie wrote:
> We are looking at ways to optimize our process for retrieving primary
> keys. Currently, we are creating a new database call to get each ID
> we need. We are considering the idea of keeping a database
> connection open with a single responsibility of retrieving a new
> primary key. Can you provide me a response to the following
> questions?:
> Are there any timeouts on open connections to the database from
> within SQL Server?
> Can you think of negative impacts this could have on the database to
> have a consistent open connections?
Conistent open connections are the standard for many client-server
applications. Even something like IIS would likely use connection
pooling and keep a certain number of connections open. There is no
problem with an open connection. In fact, in most cases it can improve
application performance.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||take a look at connection pooling
http://sqlservercode.blogspot.com/
"newie" wrote:

> We are looking at ways to optimize our process for retrieving primary keys.
> Currently, we are creating a new database call to get each ID we need. We
> are considering the idea of keeping a database connection open with a single
> responsibility of retrieving a new primary key. Can you provide me a
> response to the following questions?:
> Are there any timeouts on open connections to the database from within SQL
> Server?
> Can you think of negative impacts this could have on the database to have a
> consistent open connections?
>

Dedicated Database Connection

We are looking at ways to optimize our process for retrieving primary keys.
Currently, we are creating a new database call to get each ID we need. We
are considering the idea of keeping a database connection open with a single
responsibility of retrieving a new primary key. Can you provide me a
response to the following questions?:
Are there any timeouts on open connections to the database from within SQL
Server?
Can you think of negative impacts this could have on the database to have a
consistent open connections?newie wrote:
> We are looking at ways to optimize our process for retrieving primary
> keys. Currently, we are creating a new database call to get each ID
> we need. We are considering the idea of keeping a database
> connection open with a single responsibility of retrieving a new
> primary key. Can you provide me a response to the following
> questions?:
> Are there any timeouts on open connections to the database from
> within SQL Server?
> Can you think of negative impacts this could have on the database to
> have a consistent open connections?
Conistent open connections are the standard for many client-server
applications. Even something like IIS would likely use connection
pooling and keep a certain number of connections open. There is no
problem with an open connection. In fact, in most cases it can improve
application performance.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||take a look at connection pooling
http://sqlservercode.blogspot.com/
"newie" wrote:

> We are looking at ways to optimize our process for retrieving primary keys
.
> Currently, we are creating a new database call to get each ID we need. We
> are considering the idea of keeping a database connection open with a sing
le
> responsibility of retrieving a new primary key. Can you provide me a
> response to the following questions?:
> Are there any timeouts on open connections to the database from within SQL
> Server?
> Can you think of negative impacts this could have on the database to have
a
> consistent open connections?
>

debugging a Custom Data Processing Extension

How do I go about debugging a Custom Data Processing Extension written in VB
or C#? How do I tell the debugger which process to attach to?
--
-PeterPlease check RS books online:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_extend_dataproc_9plu.asp?frame=true
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"jpstewart" <jpstewart@.discussions.microsoft.com> wrote in message
news:F42133CD-B143-4E63-8461-0E6785EE8F5B@.microsoft.com...
> How do I go about debugging a Custom Data Processing Extension written in
> VB
> or C#? How do I tell the debugger which process to attach to?
> --
> -Peter
>