I updated to 1.6.5 beta. Apparently there are some changes to the security tables and I need to propagate those changes to my security dbs. Except I forgot how to do this. I know how to update changes that I make in the DDT, but I forgot how to make changes when they start in the db. So, I assume I need to some how update the DDT profile with the new changes, then after that I can figure it out.



Thanks!

I guess that after a while trying to understand "what this Brazilian is saying now?!", Trent developed a way to automaticaly translate everyting into his brains real-time.

LOL. Most of the time I understand just fine, Ivan (well, except when you are typing in Portuguese).



OK, I'm having a problem deploying the new security stuff. I updated the security tables with the new package you sent Trent. That seemed to go fine. I'm not sure what else has changed, but there is now a us_displayname field in the SFSUsers table.



However, when I go to create the package, I get an exception (see attachment).



Any ideas? This is causing some grief as I can't test any security features...

When and how are you getting this error message?

Almost as soon as I click on the create package button.

OK, Greg. Let's see if you really understand me...

Regarding the exception, would you like trying to delete your Security Data Deployment package from the DDT and adding them back again?

See? When I say Data Deployment, I mean Deployment Data, Trent wouldn't even notice the mistake...

So, what I tried to say is to delete all the Secuity packages from the Deployment Data group, and use the Wizard to add them back again. I have faced this before, I think. I changed the structure of a table that I had a Deployment Data package created for.

Wow, I did understand you...subliminally. Alas, see the previous post for the results.

Well....I'm not sure what you mean by Security Data Deployment package. I tried deleting the data packages I had. I then attempted to import the Security Tables again, it prompted me to do an upgrade, which I did...this time when I did that a browser opened with this message:





I have no idea if the process completed or in fact fubared by security tables



In any case...it's looking like I need some remedial Ivanese. (I don't use the DDT very much, just for these security tables...I'm using a separate security db. Otherwise, I use scripts and tool called DbGhost)

Hmm, with this name I would say you've got a haunted problem.

I've never seen this "upgrade" question. Did you delete all of your Security packages from the Deployment Data on DDT? On mine they are 6 packages.

I deleted them all....I only had 3 as I had previous deleted some...I didn't understand the ignore/merge/overwrite options well then.

OK...so did you get it going?  If not, then I would just delete all of the security tables and views and re-import them.  The only other thing that I can think of would the the deployment data, as Ivan mentioned, coming in wrong.

If I delete them (the security tables)...won't all the data be gone? Like all the permissions and roles?



It did not work and I'm fubared at the moment. The newest part of the app only works with admins (as their permissions aren't checked).

Hey Greg.

I think he meant from the DDT.

Woah....yeah, I meant JUST from your DDT profile...NOT the server!!! 

Yeah, during my morning constitutional, the light bulb went off (mind clears in these moments). Tough day yesterday. I'm about to attempt removing them from the DDT. I'll let you know how it turns out.

OK, I removed all the SFS tables and views from my DDT profile. I then add security tables back in. There were no data packages listed at all. I was then able to create a package. I then attempted to deploy it to my dev server (thank god).



It removed ALL the SFS tables (bad), and SFS views. It then didn't add them back, and started pucking because there were no tables for the relationships or views.



Oh, I'm having fun....



I've attached the log file.

I'm not sure how this got so mangled.  Just for grins, if you deploy this to a new database instead of trying to update an existing one, does it get created?

Hi Greg.

Before deploying them all back again, did you clear your DDT "Object Name History"?

Arg...those pesky history items (and I knew about that...really I did ). There they were, in all their glory...all the entries for deleting the security tables. I removed them and it's working now Good catch Ivan!



I have one more issue, which is one of my views not being distributed. I'm not sure why yet, but I can't figure it out...I'll be back!

LOL...sounds good

Okey dokey...After looking at the DDT, the missing view on another SQL Server...I could see nothing wrong. So, I just deployed again...and it worked.



Mercury is probably in retrograde or something!



Thanks for you help guys!

Is this some horoscope thing?

Yeah



You've obviously never lived in California*



This is when the apparent motion of Mercury appears to be going backwards, i.e. the opposite direction as the motion of the other planets. You have to view it for a night or two to see this. In astrology, if I remember correctly, it is a time when things are turned upside down in your life. For me it is more of a catchy phrase. When I wrote it, I didn't realize that Mercury is actually in retrograde right now!



Do a quick search on Google for more info





* OK, I'm overstating/generalizing the state of mind of those living in the beautiful state of California...and it is beautiful. But there are lots of opened minded people there and this is were I learned about Mercury in retrograde, so there