Hi,
Does anyone know how Tessitura handles local objects (that we would create) in impresario_cci? Does it follow the same guidelines as creating local database objects in impresario? Specifically,
I would like to create a local stored procedure in impresario_cci that will clean up old extractions (code was taken from another forum). I want to be sure that this is allowed and will not affect future upgrades.
Much thanks!Debbie
Since you're all discussing objects in Impresario_cci, you should probably read this Support Alert where we discuss merging the two databases in the next version of Tessitura. Which means that you will have to migrate your local procedures before upgrade. (This news will also be published in the next Network Update, coming out soon.)
Chuck, this line in the support alert you mentioned just made my day: "Windows Authentication integration, which will allow configured users to log into Tessitura with their Windows credentials, completely bypassing the Tessitura login screen." That is great news!
Glad to hear we could bring a smile to your Friday afternoon. Have a good weekend!
I am just trying to figure out if I should tell staff about this now or wait until the upgrade is a little closer to happening for us so that I do not continually get staff coming up to me asking "so when are we going to be able to do that?" as I know they will.
Hi John - yeah I understand. This has been such a frustrating issue for our team that I decided giving them hope that it will soon improve would be appreciated!
And just to be clear about what's happening here--we're still requiring that users be set up in Tessitura Security. In that app for each user you will have the option of specifying a Tessitura password OR a Windows domain username. If you set up a Tessitura user with a Windows domain name and they are authenticated with Windows at Tessitura login time, then we will skip the Tessitura login screen and log the user in with their default Tessitura user group. The user can still choose Relogin from within the app to change user groups or to log in as a different (non-Windows) Tessitura user. Tessitura users set up with a Windows domain password will attach to the database using Windows integrated security and will not have a SQL Server login or password stored in Tessitura Security. Hope that helps clarify things.
Hi Chuck - yeah, I was wondering how group selection would be handled. What you describe makes sense. Does this also mean that the 8 character username limit goes away as of v15, at least for audit fields, like created_by? Thanks!
The eight character username does not go away. You just have the option of adding a Windows domain name to the Security profile. The Tessitura username (eight characters) is still used for internal auditing.