Help! - I need to make 2 DBs talk to each other
-
We are building a new database driven website and also buying an e-commerce package where we will not be able to make modifications to the DB inside the e-commerce.
So,.... we are going to be building our own database separate from e-commerce and then trying to merge the data together so our customers don't know the difference. Are we nuts?
I know you can do sycning or stored procedures and pass the data back and forth, but I don't fully understand how syncing works, and from my experience with it, it seems unreliable. I was thinking we would just create tables in our DB that would have a foreign key, say customer number, and use that as the "link." But it's not really a foreign key is it, because it's 2 different DBs. Help!!!!!
I just really want to talk with someone who has ANY experience at all with this type of situation.
We haven't purchased the e-commerce software yet, so if there is a product out there that will let us customize the DB inside their product (yeah, right) that would be great, but I think that's probably a pipe dream.
We don't have time to build the e-commerce ourselves, not right now. We need something powerful not just some rinky dink thing, and anything at that level is probably something they will not want to share, unless we buy the source code. So, I feel kind of backed into a corner.
Please, if you know anything at all about this topic, I would appreciate your input.
My DB experience is PHP and MySQL and we are going to be using ASP.NET and SQL Server which I'm just learning (and love, so far, by the way)
Thanks!
Z
-
This is a bigger topic than the question suggests, but in a nutshell...
You won't be able to manipulate the database of the 3rd party app. Assume that. If it's wrong, yay, but I've seldom seen it.
So, the question is, how to get their data. You can do cross-database queries, pulling from their tables and joining them with yours in the code. You can selectively move their data into yours using SSIS or stored procs or an app on a scheduled basis. You can set up transactional replication so that all or part of their data is moved as it gets updated.
There are probably other options, but these should get you started.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning -
Thanks!
I guess this would be easier to get up and running than building our own e-commerce from scratch. I would like to do that eventually, but we need the commerce portion to be operational in 4-6 months, and we only have 2 SQL developers.
It's encouraging to hear that there are ways to work around and accomplish what we need to do.
-
go ahead and buy the off the shelf e-commerce solution and make sure you can see all the objects, like SPs code and views and so on.
Then create your app around it. Use the same standards and naming conventions. Prefix your new objects to differentiate from the originals. Make sure your customization will not void your rights to free support and future upgrades.
Do not re-invent the wheel, save the money and time.
Need help with development?, send me a private msg and we can talk.
Good Luck.
-
Thanks so much! I appreciate the advice and offer of help.
-
Sorry. What is SPs code? Having trouble googling it.
-
Oh! Stored Procedures.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply