How log a Bug case?

Does Microsoft have a website (or phone number) to log a bug case?
I'm not sure if this should be filed under SQL Server or ACT5.0.
The problem we stumbled across was that the ACT5.0 install creates a
Version table in the master database. This kept our Desktop
Integration group from using ACT when we did a server switch from one
SQL Server to it's standby server.
It was only though a vague reference from a internet search that we
found a mention of this table in the master database.
I believe this to be a bug, probably in ACT50, that the install is
doing this.
Any help would be great.
Thanks,
JoeyDYes, that sounds like a problem with ACT5.0. Logically, if it knows about a
standby server, it should make sure it has relevant objects in that server.
How is SQL Server supposed to know about the application's needs?
"JoeyD" <joeydba@.gmail.com> wrote in message
news:b9f5e14c-bc11-4aba-a34b-5c21c5235c9f@.k13g2000hse.googlegroups.com...
> Does Microsoft have a website (or phone number) to log a bug case?
> I'm not sure if this should be filed under SQL Server or ACT5.0.
> The problem we stumbled across was that the ACT5.0 install creates a
> Version table in the master database. This kept our Desktop
> Integration group from using ACT when we did a server switch from one
> SQL Server to it's standby server.
> It was only though a vague reference from a internet search that we
> found a mention of this table in the master database.
> I believe this to be a bug, probably in ACT50, that the install is
> doing this.
> Any help would be great.
> Thanks,
> JoeyD
>
>|||The place to report bugs for Microsoft products is Connect:
http://connect.microsoft.com/
Roy Harvey
Beacon Falls, CT
On Mon, 28 Apr 2008 13:40:00 -0700 (PDT), JoeyD <joeydba@.gmail.com>
wrote:
>Does Microsoft have a website (or phone number) to log a bug case?
>I'm not sure if this should be filed under SQL Server or ACT5.0.
>The problem we stumbled across was that the ACT5.0 install creates a
>Version table in the master database. This kept our Desktop
>Integration group from using ACT when we did a server switch from one
>SQL Server to it's standby server.
>It was only though a vague reference from a internet search that we
>found a mention of this table in the master database.
>I believe this to be a bug, probably in ACT50, that the install is
>doing this.
>Any help would be great.
>Thanks,
>JoeyD
>|||Roy - thank you very much. That is what I was looking for.
Have a good day.
JoeyD|||> Roy - thank you very much. That is what I was looking for.
> Have a good day.
So you're going to file a bug in Connect, against SQL Server, that ACT
doesn't properly initialize its standby database?|||Wait, is ACT the Application Compatibility Toolkit, or the contact
management tool from www.act.com?
"JoeyD" <joeydba@.gmail.com> wrote in message
news:8817ebba-1fca-4005-87f0-c269a6cc702a@.m44g2000hsc.googlegroups.com...
> Roy - thank you very much. That is what I was looking for.
> Have a good day.
> JoeyD|||On Tue, 29 Apr 2008 09:32:39 -0400, "Aaron Bertrand [SQL Server MVP]"
<ten.xoc@.dnartreb.noraa> wrote:
>Wait, is ACT the Application Compatibility Toolkit, or the contact
>management tool from www.act.com?
My guess was the Application Compatibility Toolkit simply because it
seems to be at release 5.0.
Roy Harvey
Beacon Falls, CT|||> My guess was the Application Compatibility Toolkit simply because it
> seems to be at release 5.0.
Even still, is there a connect area for that tool? Certainly its
shortcomings are not a SQL Server problem. :-)|||Hi All - I'll log the bug against ACT (Application Compatibility
Toolkit).
It's just never ceases to amaze me how the left hand doesn't know what
the right hand is doing. In this case, both are MS products, and for
decades I've been taught, instructed,..., that we should not be
putting users tables into any of the systems databases.
thank you all for your help and suggestions.
JoeyD|||On Tue, 29 Apr 2008 10:19:15 -0400, "Aaron Bertrand [SQL Server MVP]"
<ten.xoc@.dnartreb.noraa> wrote:
>> My guess was the Application Compatibility Toolkit simply because it
>> seems to be at release 5.0.
>Even still, is there a connect area for that tool? Certainly its
>shortcomings are not a SQL Server problem. :-)
No, but it sounds like at least one shortcoming might become a SQL
Server DBA's problem!
Roy Harvey
Beacon Falls, CT