Problems implementing BCM with a remote SQL DB

[Marc Gordon]

Using the MS document "Deploying Outlook 2007 with Business Contact Manager
in a Remote Database Configuration" (bcm_sql.doc) I was able to implement
BCM2007 and a connection to a server-based (SQL Server 2005 Express) db, but
had problems and these comments:

1. No one except administrator could connect to the db until I gave each
user the sysadmin role in SQL. I couldn't find a more granular permission
set that worked.

2. Bcm_sql.doc is really helpful but buggy. Is there an update? Want my
notes?

3. It would be helpful to add a section itemizing the steps to add a new
user, as will be necessary routinely.

4. On the client side, BCM installs SQL Express even if you have no
intention of using it. Necessary? I intend to just disable the service,
but the install would be faster and the footprint smaller if client side SQL
service could be bypassed entirely.

Thanks.

 

[Luther]

Inline.

Using the MS document "Deploying Outlook 2007 with Business Contact Manager
in a Remote Database Configuration" (bcm_sql.doc) I was able to implement
BCM2007 and a connection to a server-based (SQL Server 2005 Express) db, but
had problems and these comments:

1. No one except administrator could connect to the db until I gave each
user the sysadmin role in SQL.  I couldn't find a more granular permission
set that worked.

SQL has sproc for this, sp_grantlogin:
http://msdn2.microsoft.com/en-us/library/ms173449.aspx

Which runs the SQL command CREATE LOGIN:
http://msdn2.microsoft.com/en-us/library/ms189751.aspx

Those are for users connecting to a server.

To handle user permission for specific databases, SQL has the GRANT
command:
http://msdn2.microsoft.com/en-us/library/ms178569.aspx

I include all the above because when you add a user with BCM, I expect
it is running some variation of those commands, so you may be able to
figure what's wrong in your installation.

2. Bcm_sql.doc is really helpful but buggy.  Is there an update?   Want my
notes?

Note that this is a public newsgroup, and not something run by
Microsoft. You should report bugs directly to Microsoft, as they may
not read this message.

3. It would be helpful to add a section itemizing the steps to add a new
user, as will be necessary routinely.

The BCM database sharing wizard handles adding and removing users.

4. On the client side, BCM installs SQL Express even if you have no
intention of using it.  Necessary?   I intend to just disable the service,
but the install would be faster and the footprint smaller if client side SQL
service could be bypassed entirely.

It's not necessary to have sql installed on a client that will only
ever connect to a shared database on a server, but it is easier for
most users if setup automatically installs everything necessary to run
BCM. You can remove sql from a client if you don't need it.

 

[Bigmoe]

I had successfully deployed BCM Database 2007 on a SBS 2003 my first try, but
have not been able to duplicate the deployment on a similar SBS 2003. The
Database appears have been created with out errors, but when I run the first
slqcmd to configure the database I get repeated errors about missing object
‘ir_setActivityProperties’. The object will still be created. This repeats
many time until the following missing object errors also come up
: ‘BeginWriteTransactio’, ‘ir_DeleteSharedUser’, ‘ir_FlipEaa’,
ir_TurnOffEaa’, TrimChangeQueue’,dbo.MarkContactChangeedMinimally’,
‘ChampaignNameChanged’ ‘ir_AddUserAssignedToPickList’,
ir_DeleteUserAssignedToPicklist’, ‘DeleteAssignedToâ€,
ir_GetCampaignRecipients’. The remaining three sqlcmds run with out error.

I can view the database with SQL Server Management Studio and it looks
normal. I am using the script from a BCM installation on a Vista with MS
Outlook 2007. The last script I used was from an XP Pro OS with MS Outlook
2007 is there a difference?

I am trying to convert a Small business from ACT 7 to BCM, so any help you
can give me would be greatly appreciated.

Thank you,

Paul Moreno