I am starting a new project for a client that is a little bit of a different environment for me, and I need direction.



Typically all development takes place in our office on our equipment for eventual deployment on site. In this instance I am developing using my workstation but the SQL Server is a new installation on my customers network I will be accessing via VPN. It has to be this way. So my questions are these:



1) I will need to install the Strataframe databases to this fresh SQL Server correct? How without installing SF?

2) In the DDT, can I add another "Strataframe Data Store", that uses this new customer SQL server to keep "their" DDT projects seperate from mine?



Eventually they will be purchasing their own SF licenses to work on the project, but not yet and I need to get going.



Thanks guys.




Keith Chisarik

I punted and did what I thought was reasonable, please tell me if I was wrong.



I exported the Strataframe database and restored it to my clients SQL Server. I then defined a new "Strataframe Data Store (customer name)" and that seemed to do the trick.



I just have to remember to flip flop back and forth, right?

Keith Chisarik

Unexpected results.



When I select my old "Strataframe Data Store" in the DDT I see all my "old" DDT profiles and not the new one I defined using the new data store. - Expected



When I select the new "Strataframe Data Store (customer name)" I see all my old profiles as well as the new one I defined - Not Expected. I thought I would just see the one I defined using the new database connection to my customers server.



Thoughts?



I don't want to go much further in case I have this all wrong.

Keith Chisarik

LOL, never mind of course they are there since I exported the database



How can I get rid of the ones I don't need?



Or better yet how to start with a clean SF database? that is what I couldn't figure out, I tried to run the install but there was no "install just databases" option (would be nice).

Keith Chisarik

I just deleted them in the DDT, that worked fine.



For the future, I guess the only question that remains is how to install a clean copy of the SF database.

Keith Chisarik

OK....let me catch up here.   Is there some reason you cannot use a single SQL Server instance since you have a VPN setup between the two locations?  This would be the best solution so that you would not run into merge situations later on if you have the need for them to co-exist in the same database.

Restoring the database to the other server will work...as you learned....but your data will then start drift apart and if you have the need to merge them later...well...it ain't that easy if you know what I am saying

Next, I guess I am confused as to why you need the StrataFrame database at a location which will not even have SF installed and you are developing from your location.  I am sure that you have your reasons, but I am just not following you just yet.

Simply put, because that is how the customer wants it. No other reason.

Keith Chisarik

Understood

If you want to install a clean copy of the SF database, you can use the DDT from a laptop or across the VPN and open any profile (yeah, any profile) and choose to deploy it to the server.  When the deployment wizard opens up, you can change the *.pkg file that will be deployed and instead choose the StrataFrame.pkg file from the C:\Program Files\Common Files\MicroFour\StrataFrame\ folder.  The password is "framework" and just run through the deployment like normal... that will dump a clean copy of the SF database where ever you want it.

You can, of course, rig a quick app to use the DBEngine DLL to do the same thing if you don't have a working DDT install that can reach your target server.  I think that one of the samples might even do it for you, too.

Perfect Ben, thank you!

Keith Chisarik