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.

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

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!

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

What is the status on both issues (DDT Import and Installation)?

Thanks,

Jeff

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.

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

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.

I have already sent you the Stratafame_results15.txt file on a previous post on this thread.  http://forum.strataframe.net/FindPost18934.aspx

Thanks,

Jeff

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:

1. Open up SQL Server Management Studio
2. Right-Click on the Select the StrataFrame database
3. Click on Properties
4. Go to Options
5. Set the Compatability Level to SQL Server 2005
6. Click OK
7. Now attempt to install again and the structures will update properly