|
| | | 
StrataFrame Beginner
 
Group: StrataFrame Users
Last Login: Yesterday @ 9:34:59 AM
Posts: 35, Visits: 231 |
| | Chaps, Been working with the beta's since you put them out. I have a sproc, that is throwing an unknown column on deployment. PRobelm is I have over 200 sprocs and no idea which one of them is causing the issue. Now, I haven't downloaded the very latest beta yet, but there was talk that you were going to make this info available as to the name of the sproc that was causing the problem. Has there been any movement on this? thanks Geoff. |
| |
| | | 
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Yesterday @ 3:24:00 PM
Posts: 3,733, Visits: 3,926 |
| | Download the latest update...I am willing to bet that you have an object name history record that is deleting the column. We have a new check that when the package is created (so you will want to re-create your package file once you install the update), a verification is run and warns you of any damage that may be dealt due to the object name history and live databases, tables, and fields. |
| |
| | |
StrataFrame Beginner
Group: StrataFrame Users
Last Login: Yesterday @ 9:34:59 AM
Posts: 35, Visits: 231 |
| | Hi Trent, THanks for the response. Managed to get the update, but still no idea what proc is causing the issue. I don't get any other errors reported. I let the installer install the strataframe db so I am at a bit of a loss. Thanks in advance for any ideas you can push my way. regards Geoff |
| |
| | |
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Yesterday @ 3:24:00 PM
Posts: 3,733, Visits: 3,926 |
| | Did you see the new screen that shows the verification process and checking of the object name history? If not, then you may not have the latest version. This sounds REALLY suspect to me....the fact that the column is not there usually aludes to an object history item removing the column...you would see a warning in this case, so you would want to go back and remove the object history item that was shown in the warning. Past that, you could look at the log. If SQL Server is not providing any details then it does make it more difficult. We use SMO (SQL Server Management Objects) to deploy, so anytime an error occurs, it should provide enough information coming back from the server to figure out where the point of failure may be. You might just open up the logs to see if there is something in them instead of what you see on the screen....the logs are going to be in the same location as the PKG file if you are deploying through the DDT itself. |
| |
|
|