Removing Field Creation Limitations in a BCM SQL Database

I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
Premium Server with SQL 2005.
Whenever I try to add more than 40 User-Defined Fields in BCM I get an error
message stating I can't create more than 40 User-Defined Fields. That's a
huge limitation. Is there a way I can remove that limitation in SQL Server
2005 or at least increase the number?
Thank you.
Hi Rich
I think this is a limit imposed by BCM and not SQL Server as there are 1,024
columns per base table allowed in SQL Server to a maximum row size of 8,060
bytes
John
"Rich" wrote:

> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
> Premium Server with SQL 2005.
> Whenever I try to add more than 40 User-Defined Fields in BCM I get an error
> message stating I can't create more than 40 User-Defined Fields. That's a
> huge limitation. Is there a way I can remove that limitation in SQL Server
> 2005 or at least increase the number?
> Thank you.
|||Actually in 2005 the row size is really not limited to 8060 bytes any more.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...[vbcol=seagreen]
> Hi Rich
> I think this is a limit imposed by BCM and not SQL Server as there are
> 1,024
> columns per base table allowed in SQL Server to a maximum row size of
> 8,060
> bytes
> John
> "Rich" wrote:
|||Hi
You could argue that with Text datatype the limit does not exist in SQL
2000, so it was conditional anyhow, but Books online still gives it as the
limit in SQL 2005.
It still doesn't explain why there is a seemingly arbitrary limit imposed by
BCM.
John
"Andrew J. Kelly" wrote:

> Actually in 2005 the row size is really not limited to 8060 bytes any more.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
>
|||If BCM is dependent on SQL 2005 then I would think that there is a way to
increase the limit. Could the SQL database have code in it that commands it
to have a limit in BCM?
If a Microsoft engineer could help put some light on this I would greatly
appreciate it.
Thank you.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could argue that with Text datatype the limit does not exist in SQL
> 2000, so it was conditional anyhow, but Books online still gives it as the
> limit in SQL 2005.
> It still doesn't explain why there is a seemingly arbitrary limit imposed by
> BCM.
> John
>
> "Andrew J. Kelly" wrote:
|||I don't see any BCM MSDN group. Because this isn't a break/fix issue I can't
post it to the Microsoft Support Managed Newsgroup. I've tried that and they
said to post in the MSDN Newsgroup.
"Tibor Karaszi" wrote:

> I suggest you ask this in a BCM group, since the limit is in the application (BCM), not in SQL
> Server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:4DA60BC0-5942-45EA-A668-DF2D412FF791@.microsoft.com...
>

Removing Field Creation Limitations in a BCM SQL Database

I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
Premium Server with SQL 2005.
Whenever I try to add more than 40 User-Defined Fields in BCM I get an error
message stating I can't create more than 40 User-Defined Fields. That's a
huge limitation. Is there a way I can remove that limitation in SQL Server
2005 or at least increase the number?
Thank you.Hi Rich
I think this is a limit imposed by BCM and not SQL Server as there are 1,024
columns per base table allowed in SQL Server to a maximum row size of 8,060
bytes
John
"Rich" wrote:
> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
> Premium Server with SQL 2005.
> Whenever I try to add more than 40 User-Defined Fields in BCM I get an error
> message stating I can't create more than 40 User-Defined Fields. That's a
> huge limitation. Is there a way I can remove that limitation in SQL Server
> 2005 or at least increase the number?
> Thank you.|||Actually in 2005 the row size is really not limited to 8060 bytes any more.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
> Hi Rich
> I think this is a limit imposed by BCM and not SQL Server as there are
> 1,024
> columns per base table allowed in SQL Server to a maximum row size of
> 8,060
> bytes
> John
> "Rich" wrote:
>> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
>> Premium Server with SQL 2005.
>> Whenever I try to add more than 40 User-Defined Fields in BCM I get an
>> error
>> message stating I can't create more than 40 User-Defined Fields. That's
>> a
>> huge limitation. Is there a way I can remove that limitation in SQL
>> Server
>> 2005 or at least increase the number?
>> Thank you.|||Hi
You could argue that with Text datatype the limit does not exist in SQL
2000, so it was conditional anyhow, but Books online still gives it as the
limit in SQL 2005.
It still doesn't explain why there is a seemingly arbitrary limit imposed by
BCM.
John
"Andrew J. Kelly" wrote:
> Actually in 2005 the row size is really not limited to 8060 bytes any more.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
> > Hi Rich
> >
> > I think this is a limit imposed by BCM and not SQL Server as there are
> > 1,024
> > columns per base table allowed in SQL Server to a maximum row size of
> > 8,060
> > bytes
> >
> > John
> >
> > "Rich" wrote:
> >
> >> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
> >> Premium Server with SQL 2005.
> >>
> >> Whenever I try to add more than 40 User-Defined Fields in BCM I get an
> >> error
> >> message stating I can't create more than 40 User-Defined Fields. That's
> >> a
> >> huge limitation. Is there a way I can remove that limitation in SQL
> >> Server
> >> 2005 or at least increase the number?
> >>
> >> Thank you.
>|||If BCM is dependent on SQL 2005 then I would think that there is a way to
increase the limit. Could the SQL database have code in it that commands it
to have a limit in BCM?
If a Microsoft engineer could help put some light on this I would greatly
appreciate it.
Thank you.
"John Bell" wrote:
> Hi
> You could argue that with Text datatype the limit does not exist in SQL
> 2000, so it was conditional anyhow, but Books online still gives it as the
> limit in SQL 2005.
> It still doesn't explain why there is a seemingly arbitrary limit imposed by
> BCM.
> John
>
> "Andrew J. Kelly" wrote:
> > Actually in 2005 the row size is really not limited to 8060 bytes any more.
> >
> > --
> > Andrew J. Kelly SQL MVP
> > Solid Quality Mentors
> >
> >
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
> > > Hi Rich
> > >
> > > I think this is a limit imposed by BCM and not SQL Server as there are
> > > 1,024
> > > columns per base table allowed in SQL Server to a maximum row size of
> > > 8,060
> > > bytes
> > >
> > > John
> > >
> > > "Rich" wrote:
> > >
> > >> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
> > >> Premium Server with SQL 2005.
> > >>
> > >> Whenever I try to add more than 40 User-Defined Fields in BCM I get an
> > >> error
> > >> message stating I can't create more than 40 User-Defined Fields. That's
> > >> a
> > >> huge limitation. Is there a way I can remove that limitation in SQL
> > >> Server
> > >> 2005 or at least increase the number?
> > >>
> > >> Thank you.
> >
> >|||> Could the SQL database have code in it that commands it
> to have a limit in BCM?
> If a Microsoft engineer could help put some light on this I would greatly
> appreciate it.
I suggest you ask this in a BCM group, since the limit is in the application (BCM), not in SQL
Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:4DA60BC0-5942-45EA-A668-DF2D412FF791@.microsoft.com...
> If BCM is dependent on SQL 2005 then I would think that there is a way to
> increase the limit. Could the SQL database have code in it that commands it
> to have a limit in BCM?
> If a Microsoft engineer could help put some light on this I would greatly
> appreciate it.
> Thank you.
> "John Bell" wrote:
>> Hi
>> You could argue that with Text datatype the limit does not exist in SQL
>> 2000, so it was conditional anyhow, but Books online still gives it as the
>> limit in SQL 2005.
>> It still doesn't explain why there is a seemingly arbitrary limit imposed by
>> BCM.
>> John
>>
>> "Andrew J. Kelly" wrote:
>> > Actually in 2005 the row size is really not limited to 8060 bytes any more.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> > Solid Quality Mentors
>> >
>> >
>> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> > news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
>> > > Hi Rich
>> > >
>> > > I think this is a limit imposed by BCM and not SQL Server as there are
>> > > 1,024
>> > > columns per base table allowed in SQL Server to a maximum row size of
>> > > 8,060
>> > > bytes
>> > >
>> > > John
>> > >
>> > > "Rich" wrote:
>> > >
>> > >> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
>> > >> Premium Server with SQL 2005.
>> > >>
>> > >> Whenever I try to add more than 40 User-Defined Fields in BCM I get an
>> > >> error
>> > >> message stating I can't create more than 40 User-Defined Fields. That's
>> > >> a
>> > >> huge limitation. Is there a way I can remove that limitation in SQL
>> > >> Server
>> > >> 2005 or at least increase the number?
>> > >>
>> > >> Thank you.
>> >
>> >|||I don't see any BCM MSDN group. Because this isn't a break/fix issue I can't
post it to the Microsoft Support Managed Newsgroup. I've tried that and they
said to post in the MSDN Newsgroup.
"Tibor Karaszi" wrote:
> > Could the SQL database have code in it that commands it
> > to have a limit in BCM?
> >
> > If a Microsoft engineer could help put some light on this I would greatly
> > appreciate it.
> I suggest you ask this in a BCM group, since the limit is in the application (BCM), not in SQL
> Server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:4DA60BC0-5942-45EA-A668-DF2D412FF791@.microsoft.com...
> > If BCM is dependent on SQL 2005 then I would think that there is a way to
> > increase the limit. Could the SQL database have code in it that commands it
> > to have a limit in BCM?
> >
> > If a Microsoft engineer could help put some light on this I would greatly
> > appreciate it.
> >
> > Thank you.
> >
> > "John Bell" wrote:
> >
> >> Hi
> >>
> >> You could argue that with Text datatype the limit does not exist in SQL
> >> 2000, so it was conditional anyhow, but Books online still gives it as the
> >> limit in SQL 2005.
> >>
> >> It still doesn't explain why there is a seemingly arbitrary limit imposed by
> >> BCM.
> >>
> >> John
> >>
> >>
> >> "Andrew J. Kelly" wrote:
> >>
> >> > Actually in 2005 the row size is really not limited to 8060 bytes any more.
> >> >
> >> > --
> >> > Andrew J. Kelly SQL MVP
> >> > Solid Quality Mentors
> >> >
> >> >
> >> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> >> > news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
> >> > > Hi Rich
> >> > >
> >> > > I think this is a limit imposed by BCM and not SQL Server as there are
> >> > > 1,024
> >> > > columns per base table allowed in SQL Server to a maximum row size of
> >> > > 8,060
> >> > > bytes
> >> > >
> >> > > John
> >> > >
> >> > > "Rich" wrote:
> >> > >
> >> > >> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
> >> > >> Premium Server with SQL 2005.
> >> > >>
> >> > >> Whenever I try to add more than 40 User-Defined Fields in BCM I get an
> >> > >> error
> >> > >> message stating I can't create more than 40 User-Defined Fields. That's
> >> > >> a
> >> > >> huge limitation. Is there a way I can remove that limitation in SQL
> >> > >> Server
> >> > >> 2005 or at least increase the number?
> >> > >>
> >> > >> Thank you.
> >> >
> >> >
>|||Hi Rich
I believe BCM is part of the MS Office family microsoft.public.outlook.bcm,
although I would not raise your hopes by suggesting you posted to the office
news group, but it would be worth a try. There is some online help at
http://office.microsoft.com/en-gb/outlook/FX100647191033.aspx?CTT=96&Origin=CL100626971033
Any unsanctioned change may invalidate your licence agreement, therefore, if
failing to get a suitable response I can only suggest that you would need to
open an issue with product support
http://support.microsoft.com/oas/default.aspx?&gprid=8753&
John
"Rich" wrote:
> I don't see any BCM MSDN group. Because this isn't a break/fix issue I can't
> post it to the Microsoft Support Managed Newsgroup. I've tried that and they
> said to post in the MSDN Newsgroup.
> "Tibor Karaszi" wrote:
> > > Could the SQL database have code in it that commands it
> > > to have a limit in BCM?
> > >
> > > If a Microsoft engineer could help put some light on this I would greatly
> > > appreciate it.
> >
> > I suggest you ask this in a BCM group, since the limit is in the application (BCM), not in SQL
> > Server.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://sqlblog.com/blogs/tibor_karaszi
> >
> >
> > "Rich" <Rich@.discussions.microsoft.com> wrote in message
> > news:4DA60BC0-5942-45EA-A668-DF2D412FF791@.microsoft.com...
> > > If BCM is dependent on SQL 2005 then I would think that there is a way to
> > > increase the limit. Could the SQL database have code in it that commands it
> > > to have a limit in BCM?
> > >
> > > If a Microsoft engineer could help put some light on this I would greatly
> > > appreciate it.
> > >
> > > Thank you.
> > >
> > > "John Bell" wrote:
> > >
> > >> Hi
> > >>
> > >> You could argue that with Text datatype the limit does not exist in SQL
> > >> 2000, so it was conditional anyhow, but Books online still gives it as the
> > >> limit in SQL 2005.
> > >>
> > >> It still doesn't explain why there is a seemingly arbitrary limit imposed by
> > >> BCM.
> > >>
> > >> John
> > >>
> > >>
> > >> "Andrew J. Kelly" wrote:
> > >>
> > >> > Actually in 2005 the row size is really not limited to 8060 bytes any more.
> > >> >
> > >> > --
> > >> > Andrew J. Kelly SQL MVP
> > >> > Solid Quality Mentors
> > >> >
> > >> >
> > >> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > >> > news:D35CAB96-5D70-4258-AC92-C628E780B95B@.microsoft.com...
> > >> > > Hi Rich
> > >> > >
> > >> > > I think this is a limit imposed by BCM and not SQL Server as there are
> > >> > > 1,024
> > >> > > columns per base table allowed in SQL Server to a maximum row size of
> > >> > > 8,060
> > >> > > bytes
> > >> > >
> > >> > > John
> > >> > >
> > >> > > "Rich" wrote:
> > >> > >
> > >> > >> I have an Outlook 2007 Business Contact Manger Database on a SBS 2003 R2
> > >> > >> Premium Server with SQL 2005.
> > >> > >>
> > >> > >> Whenever I try to add more than 40 User-Defined Fields in BCM I get an
> > >> > >> error
> > >> > >> message stating I can't create more than 40 User-Defined Fields. That's
> > >> > >> a
> > >> > >> huge limitation. Is there a way I can remove that limitation in SQL
> > >> > >> Server
> > >> > >> 2005 or at least increase the number?
> > >> > >>
> > >> > >> Thank you.
> > >> >
> > >> >
> >
> >

Removing duplicate data

I have a table that I need to remove duplicates from and the table includes
an identity column. The table contains 12 fields but our business rules are
that only 3 of the fields can make the record a duplicate. We would like to
keep the record with the min identity column. I have done this in the past,
but it was about 5 years ago and I did not insert the dups into another
table, I did it strictly with a query. Can anybody please help me out with
some code to take care of this or any suggestions on a better way of doing
this? So something along the lines of grouping the data by the fields that
we are interested in and then deleting the records where the identity column
is greater than the min identity column.
Thanks.This is the duplicates along with the
minimum id per group
SELECT MIN(id),Col1,Col2,Col3
FROM sometable
GROUP BY Col1,Col2,Col3
HAVING COUNT(*)>1
Join this to the original table
to give the ids of the duplicates
excluding the minimum id.
SELECT a.id
FROM sometable a
INNER JOIN (
SELECT MIN(id),Col1,Col2,Col3
FROM sometable
GROUP BY Col1,Col2,Col3
HAVING COUNT(*)>1) b(id,Col1,Col2,Col3) ON b.id<>a.id
AND b.Col1=a.Col1
AND b.Col2=a.Col2
AND b.Col3=a.Col3
Put it all together to delete them
DELETE
FROM sometable
WHERE id IN (
SELECT a.id
FROM sometable a
INNER JOIN (
SELECT MIN(id),Col1,Col2,Col3
FROM sometable
GROUP BY Col1,Col2,Col3
HAVING COUNT(*)>1) b(id,Col1,Col2,Col3) ON b.id<>a.id
AND b.Col1=a.Col1
AND b.Col2=a.Col2
AND b.Col3=a.Col3
)|||Do you need to export the removed duplicates to another table?
Try something like this:
INSERT INTO RemDup (...) SELECT ... FROM MyTab AS t1 WHERE EXISTS (SELECT
NULL FROM MyTab AS t2 WHERE t1.Col1=t2.Col1 AND t1.Col2=t2.Col2 AND
t1.Col2=t2.Col2 AND t1.ID>t2.ID)
DELETE FROM MyTab AS t1 WHERE EXISTS (SELECT NULL FROM MyTab AS t2 WHERE
t1.Col1=t2.Col1 AND t1.Col2=t2.Col2 AND t1.Col2=t2.Col2 AND t1.ID>t2.ID)
HTH,
Axel Dahmen
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:32ACE9AA-67CE-454C-9711-956595CB7A8D@.microsoft.com...
> I have a table that I need to remove duplicates from and the table
includes
> an identity column. The table contains 12 fields but our business rules
are
> that only 3 of the fields can make the record a duplicate. We would like
to
> keep the record with the min identity column. I have done this in the
past,
> but it was about 5 years ago and I did not insert the dups into another
> table, I did it strictly with a query. Can anybody please help me out
with
> some code to take care of this or any suggestions on a better way of doing
> this? So something along the lines of grouping the data by the fields
that
> we are interested in and then deleting the records where the identity
column
> is greater than the min identity column.
> Thanks.|||Here's an example. This will delete all but 1 of the dupes. You will need to
change table / col name accordingly
DELETE FROM _Holding_table
WHERE EXISTS(SELECT NULL FROM _Holding_table s1
WHERE s1.PhoneNumber= _Holding_table.PhoneNumber
and s1.PK_Holding_TableID > _Holding_table.PK_Holding_TableID)
HTH. Ryan
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:32ACE9AA-67CE-454C-9711-956595CB7A8D@.microsoft.com...
>I have a table that I need to remove duplicates from and the table includes
> an identity column. The table contains 12 fields but our business rules
> are
> that only 3 of the fields can make the record a duplicate. We would like
> to
> keep the record with the min identity column. I have done this in the
> past,
> but it was about 5 years ago and I did not insert the dups into another
> table, I did it strictly with a query. Can anybody please help me out
> with
> some code to take care of this or any suggestions on a better way of doing
> this? So something along the lines of grouping the data by the fields
> that
> we are interested in and then deleting the records where the identity
> column
> is greater than the min identity column.
> Thanks.|||This is untested, perhaps you wrap this in a transaction first:
DELETE FROM SomeTable S
WHERE Idcolumn NOT IN
(
SELECT MIN(idcolumn)
FROM SOMETABLE S2
GROUP BY FirstColumn1,FirstColumn2,FirstColumn3
)
HTH, Jens Suessmeyer.