StrataFrame Forum
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      


««12

DDT EvaluationExpand / Collapse
Author
Message
Posted 02/19/2009 8:39:38 AM
StrataFrame Team Member

StrataFrame Team Member

Group: StrataFrame Developers
Last Login: 07/23/2010 11:23:08 AM
Posts: 352, Visits: 715
The priority is required, but it should not be deployed with a null value. The default priority for stored procedures is 10, and should be at least 1 if edited, so it set to NULL after deployment it is an erroronious state.  Try deleting the erronious stored procedure via SQL management studio and see how that affects the deployment.

If you can create a package using the new beta build that consistently deploys a sproc with a null value then by all means attatch it here, I'd like to be able to get in and give you a more specific answer. As it stands however, I can't deploy the package you sent to Trent for the reasons I already listed. We can't deploy a DDT package created on versions of Strataframe prior to the current beta build due to structure changes in the package file. Sending me the old package file does no good as I can't deploy it on my side.

My guess is that the deployment failed in the past and left the orphaned sproc out there which is giving you the problems, but I can't confirm this based soley on log files.

Post #22025
Posted 02/20/2009 3:26:08 AM
StrataFrame Novice

StrataFrame NoviceStrataFrame NoviceStrataFrame NoviceStrataFrame NoviceStrataFrame NoviceStrataFrame NoviceStrataFrame NoviceStrataFrame Novice

Group: StrataFrame Users
Last Login: 07/22/2010 8:19:42 AM
Posts: 119, Visits: 616
Dustin Taylor (02/19/2009)
The priority is required, but it should not be deployed with a null value. The default priority for stored procedures is 10, and should be at least 1 if edited, so it set to NULL after deployment it is an erroronious state. Try deleting the erronious stored procedure via SQL management studio and see how that affects the deployment.


No, the pre-exsiting stored procedures are not created using DDT. They are created using CREATE PROCEDURE command, which maintain by us before using DDT. Beside, I found that, the priority field is extended property added by DDT, and not standard SQL Server field. Therefore, any SP deployed previously (not using DDT) would not have any value on it. That is the reason for the error. Do you think this is a "limitation", which need to be enhanced? Or, do you think DDT would not support to deploy any SP which previously not deployed using DDT?

Please advice. Thank you
Post #22040
« Prev Topic | Next Topic »

««12

Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: Trent L. Taylor, Steve L. Taylor, Dustin Taylor

PermissionsExpand / Collapse

All times are GMT -6:00, Time now is 11:26am

Powered by InstantForum.NET v4.1.4 © 2010
Execution: 0.078. 9 queries. Compression Enabled.
Site Map - Home - My Account - Forum - About Us - Contact Us - Try It - Buy It

Microsoft, Visual Studio, and the Visual Studio logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.