Hi there.
Sorry 'bout my bad english.
Is there any possibility, to change the current server name from the stuctureview in the Enterprise Manger. I'm registering a lot of online-servers from my customers. The remote servername is fixed of course, but I want to change it local, to explain it a little bit better
(e.g. "W2KSQLSRV" -> "CustomerXY")
Can someone give me a hint, please?
Thanx.Not mentioned the version of SQL server used>
If its SQL 2K then you can use SP_DROPSERVER & SP_ADDSERVER which will take affect at the restart of SQL services.
If its version 7 then you've to run the setup again to take new changes affected.
Refer to books online about Renaming Servers topic.|||Originally posted by LuckyLights
Hi there.
Sorry 'bout my bad english.
Is there any possibility, to change the current server name from the stuctureview in the Enterprise Manger. I'm registering a lot of online-servers from my customers. The remote servername is fixed of course, but I want to change it local, to explain it a little bit better
(e.g. "W2KSQLSRV" -> "CustomerXY")
Can someone give me a hint, please?
Thanx. It sounds to me like you want to register a server, but have a completely different name show up on the screen in the Server collection. IF I understood what you wanted correctly, according to How to register a server (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servpem_7jua.asp), that can't be done.
-PatP
Showing posts with label manger. Show all posts
Showing posts with label manger. Show all posts
Monday, March 26, 2012
Wednesday, March 7, 2012
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...
>
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.
> > >> >
> > >> >
> >
> >
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.
> > >> >
> > >> >
> >
> >
Subscribe to:
Posts (Atom)