Resolving duplicates entries in table among 10 databases

Hi

Our product uses MS-SQL Server 2000. One of our customer has 10
installations with each installation stroring data in its own database.
Now the customer wants to consolidate these databases into one and we
already have plan for that by consolidating one DB at a time. But first
they want to find how many unique or duplicate entries they have across
all the 10 databases

Assumptions:
1. All the databases reside on the same server. (This is just an
assumption, not the real environment at customer site)
2. Databases can not be merged before it is found how many unique or
duplicate rows exist.

Table under consideration:
Message
(
HashID PK,
...
)

# of rows in Message table in each of databases: 1 Million

Here is my question: How can I find how many unique or duplicate
entries they have across all the 10 databases. I easily find unique
rows for two databases with a query like this:

SELECT COUNT(A.HasID) FROM db1.dbo.Message A LEFT OUTER JOIN ON
db2.dbo.Message B ON A.HashID = B.HashID WHERE B.HashID IS NULL

How can I do this for 10 databases. This will require factorial of 10
queries to solve this problem.

I will appreciate if someone can provide hint on this.

Regards
AK> Here is my question: How can I find how many unique or duplicate
> entries they have across all the 10 databases.

The following will list the count of unique values (Duplicates = 0) as well
has the non-unique values grouped by the number of duplicates (1-9).

SELECT
Duplicates,
(Duplicates + 1) * COUNT(*) AS TotalHashIDCount
FROM (
SELECT HashID, COUNT(*) - 1 AS Duplicates
FROM (
SELECT HashID FROM db1.dbo.Message
UNION ALL SELECT HashID FROM db2.dbo.Message
UNION ALL SELECT HashID FROM db3.dbo.Message
UNION ALL SELECT HashID FROM db4.dbo.Message
UNION ALL SELECT HashID FROM db5.dbo.Message
UNION ALL SELECT HashID FROM db6.dbo.Message
UNION ALL SELECT HashID FROM db7.dbo.Message
UNION ALL SELECT HashID FROM db8.dbo.Message
UNION ALL SELECT HashID FROM db9.dbo.Message
UNION ALL SELECT HashID FROM db10.dbo.Message
) AS Messages
GROUP BY HashID) AS HashIDCounts
GROUP BY Duplicates
ORDER BY Duplicates

--
Hope this helps.

Dan Guzman
SQL Server MVP

"AK" <ambkh@.yahoo.com> wrote in message
news:1139679057.443925.49210@.g44g2000cwa.googlegro ups.com...
> Hi
> Our product uses MS-SQL Server 2000. One of our customer has 10
> installations with each installation stroring data in its own database.
> Now the customer wants to consolidate these databases into one and we
> already have plan for that by consolidating one DB at a time. But first
> they want to find how many unique or duplicate entries they have across
> all the 10 databases
> Assumptions:
> 1. All the databases reside on the same server. (This is just an
> assumption, not the real environment at customer site)
> 2. Databases can not be merged before it is found how many unique or
> duplicate rows exist.
> Table under consideration:
> Message
> (
> HashID PK,
> ...
> )
> # of rows in Message table in each of databases: 1 Million
> Here is my question: How can I find how many unique or duplicate
> entries they have across all the 10 databases. I easily find unique
> rows for two databases with a query like this:
> SELECT COUNT(A.HasID) FROM db1.dbo.Message A LEFT OUTER JOIN ON
> db2.dbo.Message B ON A.HashID = B.HashID WHERE B.HashID IS NULL
> How can I do this for 10 databases. This will require factorial of 10
> queries to solve this problem.
> I will appreciate if someone can provide hint on this.
> Regards
> AK|||Thank you Dan. This is exactly what I needed (in fact more than what I
needed :)

Regards
AK

Dan Guzman wrote:
> > Here is my question: How can I find how many unique or duplicate
> > entries they have across all the 10 databases.
> The following will list the count of unique values (Duplicates = 0) as well
> has the non-unique values grouped by the number of duplicates (1-9).
> SELECT
> Duplicates,
> (Duplicates + 1) * COUNT(*) AS TotalHashIDCount
> FROM (
> SELECT HashID, COUNT(*) - 1 AS Duplicates
> FROM (
> SELECT HashID FROM db1.dbo.Message
> UNION ALL SELECT HashID FROM db2.dbo.Message
> UNION ALL SELECT HashID FROM db3.dbo.Message
> UNION ALL SELECT HashID FROM db4.dbo.Message
> UNION ALL SELECT HashID FROM db5.dbo.Message
> UNION ALL SELECT HashID FROM db6.dbo.Message
> UNION ALL SELECT HashID FROM db7.dbo.Message
> UNION ALL SELECT HashID FROM db8.dbo.Message
> UNION ALL SELECT HashID FROM db9.dbo.Message
> UNION ALL SELECT HashID FROM db10.dbo.Message
> ) AS Messages
> GROUP BY HashID) AS HashIDCounts
> GROUP BY Duplicates
> ORDER BY Duplicates
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "AK" <ambkh@.yahoo.com> wrote in message
> news:1139679057.443925.49210@.g44g2000cwa.googlegro ups.com...
> > Hi
> > Our product uses MS-SQL Server 2000. One of our customer has 10
> > installations with each installation stroring data in its own database.
> > Now the customer wants to consolidate these databases into one and we
> > already have plan for that by consolidating one DB at a time. But first
> > they want to find how many unique or duplicate entries they have across
> > all the 10 databases
> > Assumptions:
> > 1. All the databases reside on the same server. (This is just an
> > assumption, not the real environment at customer site)
> > 2. Databases can not be merged before it is found how many unique or
> > duplicate rows exist.
> > Table under consideration:
> > Message
> > (
> > HashID PK,
> > ...
> > )
> > # of rows in Message table in each of databases: 1 Million
> > Here is my question: How can I find how many unique or duplicate
> > entries they have across all the 10 databases. I easily find unique
> > rows for two databases with a query like this:
> > SELECT COUNT(A.HasID) FROM db1.dbo.Message A LEFT OUTER JOIN ON
> > db2.dbo.Message B ON A.HashID = B.HashID WHERE B.HashID IS NULL
> > How can I do this for 10 databases. This will require factorial of 10
> > queries to solve this problem.
> > I will appreciate if someone can provide hint on this.
> > Regards
> > AK|||Better too much than too little :-)

--
Hope this helps.

Dan Guzman
SQL Server MVP

"AK" <ambkh@.yahoo.com> wrote in message
news:1139936166.210532.262820@.g43g2000cwa.googlegr oups.com...
> Thank you Dan. This is exactly what I needed (in fact more than what I
> needed :)
> Regards
> AK
> Dan Guzman wrote:
>> > Here is my question: How can I find how many unique or duplicate
>> > entries they have across all the 10 databases.
>>
>> The following will list the count of unique values (Duplicates = 0) as
>> well
>> has the non-unique values grouped by the number of duplicates (1-9).
>>
>> SELECT
>> Duplicates,
>> (Duplicates + 1) * COUNT(*) AS TotalHashIDCount
>> FROM (
>> SELECT HashID, COUNT(*) - 1 AS Duplicates
>> FROM (
>> SELECT HashID FROM db1.dbo.Message
>> UNION ALL SELECT HashID FROM db2.dbo.Message
>> UNION ALL SELECT HashID FROM db3.dbo.Message
>> UNION ALL SELECT HashID FROM db4.dbo.Message
>> UNION ALL SELECT HashID FROM db5.dbo.Message
>> UNION ALL SELECT HashID FROM db6.dbo.Message
>> UNION ALL SELECT HashID FROM db7.dbo.Message
>> UNION ALL SELECT HashID FROM db8.dbo.Message
>> UNION ALL SELECT HashID FROM db9.dbo.Message
>> UNION ALL SELECT HashID FROM db10.dbo.Message
>> ) AS Messages
>> GROUP BY HashID) AS HashIDCounts
>> GROUP BY Duplicates
>> ORDER BY Duplicates
>>
>> --
>> Hope this helps.
>>
>> Dan Guzman
>> SQL Server MVP
>>
>> "AK" <ambkh@.yahoo.com> wrote in message
>> news:1139679057.443925.49210@.g44g2000cwa.googlegro ups.com...
>> > Hi
>>> > Our product uses MS-SQL Server 2000. One of our customer has 10
>> > installations with each installation stroring data in its own database.
>> > Now the customer wants to consolidate these databases into one and we
>> > already have plan for that by consolidating one DB at a time. But first
>> > they want to find how many unique or duplicate entries they have across
>> > all the 10 databases
>>> > Assumptions:
>> > 1. All the databases reside on the same server. (This is just an
>> > assumption, not the real environment at customer site)
>> > 2. Databases can not be merged before it is found how many unique or
>> > duplicate rows exist.
>>> > Table under consideration:
>> > Message
>> > (
>> > HashID PK,
>> > ...
>> > )
>>> > # of rows in Message table in each of databases: 1 Million
>>> > Here is my question: How can I find how many unique or duplicate
>> > entries they have across all the 10 databases. I easily find unique
>> > rows for two databases with a query like this:
>>> > SELECT COUNT(A.HasID) FROM db1.dbo.Message A LEFT OUTER JOIN ON
>> > db2.dbo.Message B ON A.HashID = B.HashID WHERE B.HashID IS NULL
>>> > How can I do this for 10 databases. This will require factorial of 10
>> > queries to solve this problem.
>>> > I will appreciate if someone can provide hint on this.
>>> > Regards
>> > AK
>sql

Requirements for installing this product on a W2003 server?

I wanted to try a test drive of the product on my new web server, but I get
a warning that it won't install. Warning is worthless because it says that
something isn't present, but fails to mention what that is. No # to cross
reference.
So what do you need to have on a fresh install of W2003 ?
This is a web box only, and my SQL boxes all have no IIS installed.
TIA
__StephenSystem requirements can be found at
http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx
Hope this helps
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"__Stephen" wrote:
> I wanted to try a test drive of the product on my new web server, but I get
> a warning that it won't install. Warning is worthless because it says that
> something isn't present, but fails to mention what that is. No # to cross
> reference.
> So what do you need to have on a fresh install of W2003 ?
> This is a web box only, and my SQL boxes all have no IIS installed.
> TIA
> __Stephen
>
>

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.

Request for feedback - Aliases have been deprecated for some time and will be removed soon

As documented in SQL Server BOL, aliases have been deprecated for some time and we are planning to remove them from the product in the next release.

We will greatly appreciate any feedback or comments regarding this change. We would like to know how our customers will be affected by this change and analyze if there is anything we can do to help you to make the transition easier.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

We are also planning on removing the following stored procedures in the next release:

sp_addgroup, sp_dropgroup, sp_changegroup, sp_helpgroup

Thanks,
Jack Richins
SDE
SQL Server Engine

|||Removing entirely from the SQL server may not be an option, will there be any documentation or MS article released to enable the new users to understand the 'new' concept in addition to BOL .|||

Alias were superseded by roles in SQL Server 2000, for more information you can visit the following BOL pages:

· Deprecated Database Engine Features in SQL Server 2005 (under “Features Not Supported in the Next Version of SQL Server” ): http://msdn2.microsoft.com/en-us/library/ms143729.aspx

· Create User (TSQL): http://msdn2.microsoft.com/en-us/library/ms173463.aspx

· Create role (TSQL): http://msdn2.microsoft.com/en-us/library/ms187936.aspx

Hopefully these links will help on the migration process to use roles, and it will also help to clarify the nature of the planned change in the next release of SQL Server.Thanks a lot, for your feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||Raul
Appreciate your links in this case, I will ask my users to understand to have more information and post back if any further details are required.

Thanks.|||

Raul

Have you had any feedback in this regard, would like to know more about it.

|||We have not recieved any additional comments with regard to the removal of aliases.|||I haven't run across a customer using aliases for a VERY long time. I don't see any issues with removing them as far as any of my customers are concerned.|||

I have not seen aliases in a very long time - I would have to go back to my SQL Server 6.5 days. I look after 70+ production SQL Server (6.5,7, 2000, & 2005) and will lose no sleep on this.

|||

I haven't seen them at any site in the past few years at least.

-Sue

|||So they will be removed in next release of SQL or service pack?|||

They will be removed on the next release.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Removal would be a good thing as I get too many questions from junior developers about what I should and should not be using.

|||I am fine with the change|||Agreed. No issues here with removing them from Katmai.