Re: Can CRM be made to use SQL Server non default instance?

[Peter Lynch]

Interesting. Please provide link to a Microsoft page that strongly
recommends not running any default instances of SQL server for security
reasons

Thanks

"Robert E. Spivack" <RobertE...@discussions.microsoft.com> wrote in
message news:70DF662F-9879-4EE3...@microsoft.com...
> The docs say that the SQL server used by CRM cannot be a non-default
> instance
> so we installed it per the docs.
>
> However, SQL server management and best practices security procedures that
> we have been following from Microsoft strongly recommend not running any
> default instances of SQL server.
>
> Is there a way (registry setting?) to make CRM use a non-default instance
> of
> SQL Server? This seems like such a trivial thing that I don't understand
> why
> CRM omitted support for non-default instance.

[Daniel Tan]

Try doing a search on the newsgroup. Remember reading a posting on that.
With the mean of using an 'alias' to workaround.

Do note that it's not supported by Microsoft CRM 3.0

[Daniel Tan]

Search for the subject "SQL instance".

[Robert E. Spivack]

I just found this on the "Mid Atlantic Microsoft CRM" blog. I do not know
what "partnersource" is? (yet another thing to sign-up for??) Can someone
simply post the solution? - It sounds like a registry hack to bypass the
installer checks:

http://blogs.msdn.com/midatlanticcrm/archive/2006/06/23/Name_your_Instance_SQL_Instance_that_is_in_Microsoft_CRM_3.aspx

"Name your Instance (SQL Instance that is)
Yesterday, June 23, 2006, 6:00:00 PM | Ben Vollmer
The CRM Product Group has completed test certification of Microsoft CRM v3.0
using SQL Named Instances, and CRM Customer Support even agreed to officially
support it. This does conflict with what is in the current Impllementation
Guide, which specifies it in the has to be installed in the default instance
only. (Yes, I am relatively certain that the documentation will be updated
soon.)

If you want to install CRM in a Named Instance, your best bet (only bet) is
to call or submit a ticket via PartnerSource. The process is documented, they
just want to walk you through it as it bypasses the Environmental Diagnostics
Wizard (EDW) at the beginning of the setup process.

No additional hot fixes or service packs are required, but we you to call in
so that we limit the number of customers bypassing the EDW. The EDW is a
powerful tool to diagnose potential deployment problems, and should always be
used when setting up against a SQL Default Instance.

Thanks to the Product Group, Test and Sustained Engineering and Support for
listening to customers and partners! This rocks!"

[Matt Parks]

You should be able to submit the support ticket through any channel, not
just ParterSource. PartnerSource is just the method that the Dynamics
partners do it and some of the reps forget that there are multiple ways now.

Given the nature of the writeup, they shouldn't be charging you for this
support ticket, so I don't see the downside to going the official route.

--

Matt Parks
MVP - Microsoft CRM

"Robert E. Spivack" <RobertE...@discussions.microsoft.com> wrote in

message news:504C5240-8788-4BD2...@microsoft.com...

[Traci]

I have the same problem and have submitted a support ticket to both the
official route and partnersource and it's still unresolved. I have been
routed to VOICE and still no response.
Can you provide me with a specific url or email address to contact?

[Matt Parks]

I have been told by my contacts on the support team that this should not be
a charged incident. The technique is to bascially disable the EDW during
the install via a registry change, but I'm not sure the exact registry
setting to use. If you are not getting a response from your trouble ticket,
then ask your support engineer to escalate the ticket as they are not
provbiding the help you need.

--

Matt Parks
MVP - Microsoft CRM

"Traci" <Tr...@discussions.microsoft.com> wrote in message
news:3B7A0B71-5F79-4C27...@microsoft.com...