Hello,
I thought I had successfully configured a second (2nd) test database on our testing sql server instance but I was wrong. I can have either connection configured but not both at the same time and it has to do with the 'securecheck'. When I run this script and change the database name to the instance I want to log into it works.
USE impresario
GO
SP_revokedbaccess 'securecheck'
SP_droplogin 'securecheck'
CREATE LOGIN securecheck
WITH PASSWORD = 'securecheck',
CHECK_POLICY = OFF
SP_grantdbaccess 'securecheck', 'securecheck'
SP_addrolemember 'securelogin', 'securecheck'
but if I run it and change the name of the DB it will deny me access to the other database. one db is named impresario and one is named impresario2.
I looked at the store procedures it is running but I don't know what, if anything I can do about it.
Can I have two instances on Tessitura running on one sql server? We need to have a dev one and test one.
Any information is appreciated.
thanks, Gretchen
I was under the impression that for the time being, database names other than impresario were not supported (but that this was a roadmap item). The alternative is to install a second SQL server instance on your test server, so that both databases can be named impresario, but will be accessed separately.
Just to make sure the terminology is clarified — your windows server has a hostname, for example: sql01. When you install SQL Server, you can elect to install the "default instance" or a "named instance", for example tessitest01. This means when configuring your database connection, you can connect to the default instance just with the hostname sql01, but you would connect to the named instance as sql01\tessitest01. Each instance of SQL server has its own user logins, agent jobs, and databases, like impresario and impresario_cci. You can use instances to simulate having multiple SQL servers without needing to maintain separate windows servers or pay extra for SQL Server licensing, but this is NOT recommended for production servers, since SQL Server will not coordinate resource usage between multiple instances.
So to summarize: to have multiple tessitura databases for dev and test, you can have one Windows server, with two instances of SQL server installed, each with their own impresario database and logins.
What Nick is describing is consistent with our experience. We currently have about four instances of SQL Server running on a single test database server for the purpose of supporting multiple dev/test environments. It will be very nice when we can get away from that approach, but it works.
Thanks Nick and David. That does make sense, it's just that I am not familiar with that configuration. Our SQL server instance is the default MSSQLSERVER.
Sounds like I will have to run the SQL Server installer to create another named instance. Then then go through the TIM steps to set up Tessitura TEST2.
Are there instructions for this configuration? (other than what you gave me?) :)
siide Note: I was able to make it work by creating or rather renaming the securecheck login on impressario2 and then configuring the SQL Login 'securecheck' to the impressario database. But I will change course and configure a named instance on our windows server.
Thank You, Gretchen