All,
We are upgrading to V11 in about 2 weeks. I would like to create a brand new v11 database and I just need to know if I use the TIM utility to create a new DB then restore from backup. We have been using a "cloned" test copy in a virtual network and I would like a brand new copy for the production upgrade.
Thanks
John Brandt
John,
If you are upgrading from V10 then you would want to make a new copy of your V10 database and go through the data migration and upgrade steps outlined in the upgrade documents. That is how you get your data to V11. The migration is done outside of TIM. You go to TIM after that is done to enable SQL Notifications and install the other service components.
Let me know if I have misinterpreted what you are wanting to do.
Ron
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of John BrandtSent: Monday, August 20, 2012 2:03 PMTo: Ron WilsonSubject: [Tessitura Next Generation Forum] Creating new v11 database
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
Ron,
We are migrating from V10 to V11 however, after attending the tess conference, many users created a brand new database in v11 and restored from backup their version 10 database and repointed T_defaults and websites. The benefit of this is that it allowed the V10 to remain completely untouched in the event of a rollback if needed instead of restoring from backup. I found the install document and I am building a new tess server so we can test connectivity and functionality and on the day of the migration move the v10 to the new database and keep the v10 unsullied to cover all of our bases. It is a lot more work on the back end but it mitigates the risk of a failed restore. Let me know your ideas.
John
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Ron Wilson Sent: Tuesday, August 21, 2012 8:35 AM To: John Brandt Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of John Brandt Sent: Monday, August 20, 2012 2:03 PM To: Ron Wilson Subject: [Tessitura Next Generation Forum] Creating new v11 database
This sounds almost exactly the same as what we’re doing.
I have a brand new v11 environment to test with – a second SQL instance on the same Windows server as our v10 Test environment.
I can backup my Live v10 DB, and restore to v10 Test. I can then restore to v11 Test and run through the migration steps. So all three DB’s are then current. I plan to do the Live to v11 Test migration several times during our testing processes over the next several weeks. Hopefully I’ll get really good at it!
On the day we go live, I will migrate the Live v10 DB to v11. Of course, a full backup will be taken beforehand! The Live DB therefore will stay on the same Windows server in the same SQL instance as it is now.
…Dave
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of John Brandt Sent: Tuesday, August 21, 2012 10:59 AM To: Vivino, David Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
That’s what I have been doing except we have separate virtual servers for test and live. Did your extractions work? What did you name your test instance in the SQL database? We talked about this at the conference and it was mentioned that extractions may not function properly.
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of David Vivino Sent: Tuesday, August 21, 2012 1:46 PM To: Joe Giambalvo Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
I think John’s talking about building out a brand new Live database, fully configured for v.11, that on go-live you restore from Live V.10. In theory, it ought to make your go-live window shorter, because all the configuration is done beforehand. I think it’s a terrific idea and I’d love to do that, but someone else was saying that the Transcend database gets cranky if you go this way. I’d love to hear experiences from those who did this, as I had enough trouble with my Transcend database when I built my new Test v.11 environment (I eventually created a new Transcend database, since in Test it doesn’t matter, but needless to say, I don’t want to have to do this in Live).
If anyone has any experiences they could offer, I’d love to hear them.
Thanks,
Jeanne DeVore
Technology Manager
Chicago Shakespeare Theater
jdevore@chicagoshakes.com
312 595-5603
www.chicagoshakes.com
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of David Vivino Sent: Tuesday, August 21, 2012 2:48 PM To: Jeanne DeVore Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
Yes the IT managers said that there was a lot of work behind the scenes but the go live date is smooth. I had to create a new transcend database in test as well with a loop back so charges register as valid but never leave the system. Our V10 Transcend is on the same server as Tess (I inherited the setup) and I want to move it out to a separate instance. I would rather work like a mule beforehand and redirect the web site and t_defaults than be down longer than needed.
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Jeanne DeVore Sent: Tuesday, August 21, 2012 2:13 PM To: John Brandt Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
Dave, we took a similar approach. We took a backup then migrated our live v10 database to v11 (after a lot of testing of course). The migration went smoothly for us.
Jeanne, we were able to move our Transcend database (both test and live) from an old SQL Server 2005 server to a newer SQL Server 2008 R2 without running into trouble. I think I took good notes on it and could post what we did if that would be helpful.
David
_______________________________________________________ David Frederick Database Applications Analyst Segerstrom Center for the Arts 600 Town Center Drive, Costa Mesa, CA 92626 T (714) 556-2122 x 4067 E DFrederick@SCFTA.org
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Jeanne DeVore Sent: Tuesday, August 21, 2012 1:17 PM To: David Frederick Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
Good to know, David, and I’d love whatever notes you’ve got!
Jeanne
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of David Frederick Sent: Tuesday, August 21, 2012 4:21 PM To: Jeanne DeVore Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
Me too
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Jeanne DeVore Sent: Tuesday, August 21, 2012 3:30 PM To: John Brandt Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
Hi Jeanne,
I obtained the following from Intrix, which I used when moving the Transcend databases:
· How to Guide - Move TPAU DB to 2008 SQL.pdf document – this also works for SQL Server 2008 R2
· RunAfterDBmoves.sql
· Manage_transaction_log.sql
There are links in the how to document to obtain the SQL scripts mentioned above.
Here are the steps I took:
1. Stop Transcend services.
2. Intrix’s how-to document mentions removing logins and schemas related to Transcend from the old database server, but I didn’t do that as I wanted to make it easy to roll back in case of a problem.
3. Detach TPAU and TPAUARCHIVE databases from the current (old) database server. I used SSMS to do this and selected both the Drop Connections and Update Statistics options.
4. Copied the tpau*.mdf and tpau*.ldf files from the old server to their appropriate location on the target database server.
5. Using SSMS pointing to the target database server, attach both TPAU and TPAUARCHIVE databases. I had to correct the location of the LDF files as it didn’t come up properly automatically.
6. Execute RunAfterDBmoves.sql
7. Execute manage_transaction_log.sql
8. Execute this statement in both the TPAU and TPAUARCHIVE database contexts – this ensures the SQL login is linked up properly with the database users:
EXEC sp_change_users_login ‘Auto_Fix’, ‘TPAU_ROCKS’;
(As a side note, the above command is very handy when scripting things like Tessitura test database refreshes – it is much easier than other methods I’ve seen for resolving the link between SQL logins and database users.)
9. On the server where your Transcend services are running, update the TPAU System DSN to point to the target database server.
10. Start Transcend services.
The above worked well for us in both test and live environments.
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Jeanne DeVore Sent: Tuesday, August 21, 2012 2:34 PM To: David Frederick Subject: RE: [Tessitura Next Generation Forum] Creating new v11 database
The issue we discussed with Extractions is only if you are using one instance for multiple databases. If you are using a separate SQL instance then there should be no issue.
Best,
Anna