Development on new server


Author
Message
Keith Chisarik
Keith Chisarik
StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)StrataFrame VIP (2.4K reputation)
Group: StrataFrame Users
Posts: 939, Visits: 40K
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
Reply
StrataFrame Team
S
StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
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.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search