Goldmine Curtaining stinks I'd rather use Sql to do the job.

[sk8ology]

Goldmine is a sales tool we use. Its data comes from Sql Server. Goldmine’s security and user views are very bad. I am trying to do something as basic as not letting user1 see user2’s data. There is a long step process that when completed still doesn’t work right. Whenever user2 needs a list of contacts added the entire process needs to be duplicated for all other users. If I have 10 users then that can become a pain.

Sql Server however should be able to handle this much better allowing for mass updates. I’m trying to avoid 1 db per user as. Then the admins would constantly have to switch db’s and data won’t be in sync for reports.

I was thinking of making 1 db that’s an admin db with some type of replication or something like log shipping so the user’s db automatically updates the admin db. I still have multiple db’s but at least the admin db would have data from all other user’s db and reports would be in sync.

Any suggestions?

 

[mrdenny]

That would be replication. Setup transaction replication from each of the users databases to the admin database. Make sure to modify the default behavor of the articles so that that snapshot doesn't try to drop the tables.

Then script out the tables and add them to the admin database, and subscribe it to all the subscriptions from all the users database.

If done correctly it should work fine for you.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[sk8ology]

Awesome! It sounds like it could work.

Thanks for the reply.

 

[philhege]

That may or may not work. Goldmine's user and security info are not stored in SQL; there are a couple of tables in the GM directory that handle it.

Phil Hegedusich
Senior Programmer/Analyst
IIMAK

http://www.iimak.com

-----------
Not NULL-terminated yet.

 

[sk8ology]

The reason why I think it will is this;

I work for a company that merged with another company. We have 2 databases for each company. Right now users from company1 can see the calendar and availability of company2 users and vise versa, but can't see the contact record and other relevant data. There is one database that houses the calendar and other system files. The other databases just house contact records. Basically I will use this same scheme. If I add a database for each user it will act the same as company1 and company2, but user1 and user2, etc. I will then merge the data from all databases to the main database for the supervisors and the report creators. When it comes time to add data to a particular database, I will just add it to the users database the data intended for and the replication will take care of adding it to the admin database.

Does this sound like it would work?

 

[mrdenny]

From the SQL Side yes it does sound like it will work.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com