By Jeff Pagley - 8/28/2008
Hi SF Team,I am using DDT for the first time. I'm using version 1.6.5.3. After importing the database (SQL Server 2005), there are several stored procedures that are missing. What am I doing wrong? Thanks, Jeff
|
By Greg McGuffey - 8/29/2008
Jeff,
You should consider downloading the latest beta (don't let the beta scare you...MicroFour (SF parent company) uses it in production with their medical software and many of us also use their betas in production (I'm using I believe the 8/1 beta it in production myself and currently building on the 8/17 beta...about to release that into production). Typically, their betas are very stable. There have been a lot of improvements/changes/fixes to the DDT since 1.6.5.3.
It would also be of great help if you provided some detail as to what you attempted.
Finally, if you don't get a response in a day or so, you can "bump" the post by posting a followup, something like "Any ideas?".
|
By Jeff Pagley - 8/29/2008
Hi Greg,
You should consider downloading the latest beta Where do I get the latest beta to download?
It would also be of great help if you provided some detail as to what you attempted. There were no details to give. Like I said. Using the DDT for the first time, all I did was import an existing database and then view the results and notice many of the stored procedures were missing. I will try the beta once I know where to download it from. Thanks, Jeff
|
By Greg McGuffey - 8/29/2008
Hi Jeff!
On the main forum page, the very first forum is "Posted Releases". There is typically a post for each beta, with the most recent being for the current beta. The last post in that thread is the latest beta. The easiest way to get there is to just click link under the date that starts with "In:...". For you convenience, here is the link to the latest:
http://forum.strataframe.net/FindPost18786.aspx
I'd definitely get this installed and try it before we ("we" meant very loosely, as I'm not a big expert on the DDT  ) attempt to solve any problems...that may not actually exist anymore!
However, if it still doesn't work, you might start thinking along these lines:
Is there anything common about the missing sprocs? Like a common naming convention? Schema that is different from others that did import (i.e. the dbo did import but a custom schema like "AppUser" didn't)?
|
By Jeff Pagley - 9/2/2008
On the main forum page, the very first forum is "Posted Releases". There is typically a post for each beta, with the most recent being for the current beta. The last post in that thread is the latest beta. The easiest way to get there is to just click link under the date that starts with "In:...". For you convenience, here is the link to the latest: http://forum.strataframe.net/FindPost18786.aspx
I downloaded the latest release and during installation I got the error below. What do I need to do to correct this? 
|
By Dustin Taylor - 9/2/2008
Could you post your most recent install log? It should have the full exception text and stack trace so we can better diagnose what is going on here.Thanks 
|
By Jeff Pagley - 9/2/2008
Where do I find the log?
|
By Dustin Taylor - 9/2/2008
You should be able to find it at:c:\program files\common files\MicroFour\StrataFrame\StrataFrame_ResultsX.log Where "X" is an incrimenting number (one for each install). You want the highest number (most recent log).
|
By Jeff Pagley - 9/2/2008
I have attached the latest log.
|
By Dustin Taylor - 9/2/2008
Do you have the correct server name supplied?You can test the connection settings in SQL management studio to ensure it all lines up as you are expecting it to from your development machine.
|
By Jeff Pagley - 9/3/2008
Do you have the correct server name supplied? You can test the connection settings in SQL management studio to ensure it all lines up as you are expecting it to from your development machine. Hi Justin, On the second or third screen of the setup wizard it verifies that the connection to the SQL Server Instance name I supplied is good before going to the next screen. This happens before this error occurs. So I am not sure why you are asking this question?!?!? However, I work with this database and develop against it everyday using Strataframe so I know it is good.
|
By Jeff Pagley - 9/4/2008
What is the status? Please keep in mind that what started all of this is the DDT failed to import over half of the stored procedures in my database. Following the suggestions, I downloaded the latest release and tried to install it and that is when I encounter another problem with the installation failing. I need to get both problems resolved.Thanks, Jeff
|
By Dustin Taylor - 9/4/2008
Hi Jeff,You are deploying this to your SQL 2005 server, correct? I just had Ben in here looking at the source of the Database Migrator class to get to the bottom of your issue, but we couldn't see any issues in the code itself. Something is preventing the retireval of stored procs and UDFs from your SQL 2005 server where it works fine on ours (and all of the other DDT users'). Could you go into SQL Management studio, and take a screenshot of the Options page of the database properties for the StrataFrame databse. Go ahead and maximize it first so that we can see all of the options. Hopefully that will shed some light as to why your server is behaving differently than ours. Thanks!
|
By Jeff Pagley - 9/4/2008
Hi Dustin,I was not sure what problem you are referring to - DDT or installation? So included the Strataframe database options and the my production database options. Thanks, Jeff
|
By Jeff Pagley - 9/5/2008
What is the status on both issues (DDT Import and Installation)?Thanks, Jeff
|
By Dustin Taylor - 9/5/2008
Do you have a SQL Server 2005 Express instance that you can put the StrataFrame database on? It looks as though the SF database is trying to be exist in SQL 2000 compatibility mode, which could be the issue. Could you move that over to a fresh SQLExpress instance and retry the install? That should give us a clean state rather than going back and forth trying to determine the differences in environment.
|
By Jeff Pagley - 9/9/2008
Hi Justin,I moved the Strataframe database to a new SQLExpress install on another machine. I attempted to run the strataframe installation on the machine with new SQLExpress install and I get the same error!  I have attached the Strataframe.mdf and ldf files for your inspection. I figure the next logical step is for you guys to look at the database to see why it is failing. Obviously I need to get this resolve, before I can run the DDT to import an existing database which was failing to import all of my stored procedures which started this support thread to begin with several days ago. I am anxious to get this fix so that I can start using DDT I purchased a couple of weeks ago for a current project I am working on. Thanks for you prompt attention to this matter. Jeff
|
By Trent L. Taylor - 9/9/2008
Jeff,What is the error that you are getting? I would like to have any exceptions, etc. before looking at the attachment so that I have all of the facts in hand...thanks.
|
By Jeff Pagley - 9/9/2008
I have already sent you the Stratafame_results15.txt file on a previous post on this thread. http://forum.strataframe.net/FindPost18934.aspxThanks, Jeff
|
By Trent L. Taylor - 9/10/2008
Well, Dustin actually gave you the answer you needed back on 9/5/2008. We attached your database to our local SQL Express and deployed and it failed with the sname error...so we went in to verify that you had set the DB to 2005 compatability mode and it worked. To fix it do the following:- Open up SQL Server Management Studio
- Right-Click on the Select the StrataFrame database
- Click on Properties
- Go to Options
- Set the Compatability Level to SQL Server 2005
- Click OK
- Now attempt to install again and the structures will update properly
|
By Jeff Pagley - 9/12/2008
That solved the problem. Now what about the DDT import issue that started this thread to begin with. The DDT does not import all of my stored procedures. I did take a look at them to see if there is any common characteristics among them that might stop them from importing in and I did not notice anything.As always thank you for the great support! Jeff
|
By Trent L. Taylor - 9/12/2008
Honestly Jeff, I don't know what your issue would be on the stored procs if you are on the most recent version of the 1.6.6 beta. All seems to be imported as it should on this side. Make sure that you are on the most recent build and if the problem persists then I guess let us have the mdf and ldf of the database your are trying to import and we will try it on this side.
|
By Jeff Pagley - 9/12/2008
I apologize that it seems to be just me having these issues. As I said, I purchased the DDT to start using on this project and I am trying to use it for the first time. I have attached my database and the strataframe database for your testing.You guys do a great job in supporting your products and I truly appreciate your patience in helping me through this problem. Thank You, Jeff
|
By Jeff Pagley - 9/17/2008
Hi SF Team,What is the status on my DDT import issue? In my previous post I attached my database and the strataframe database for your testing as suggested. You will see my database is simple and small. Thanks, Jeff
|
By Trent L. Taylor - 9/17/2008
This was a very strange scenario, but I have posted a fix. We are already starting to roll out new product for the 1.6.7 build, but since this was such a minor change and will not affect everyone, I thought I would just post the fix here. Here was the issue:To improve performance, the DDT would exit when enumerating stored procedures and UDFs when the first system object was found as system objects to not need to be imported. However, under certain, very rare circumstances, legitimate sprocs or UDFs may appear within the collection AFTER the system objects. This is highly unusual, but so as not to have this issue creep up again in the future and since the import is a process in which a developer does not live (as this is generally only done once per database) the lengthier process will be implemented. At any rate, download the attached file and just overwrite your existing databasedtk.exe file. This should be located in the c:\program files\MicroFour\StrataFrame folder.
|
By Jeff Pagley - 9/17/2008
Hi Trent,I am sure glad it was not me doing something wrong causing you guys a lot of unnecessary work and grief. Secondly, the patch worked!  Thank you, Jeff
|
By Trent L. Taylor - 9/17/2008
No problem....just glad it got you going.
|