Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Adding tables to the TS database - cons?
System
We are needing to create a new table in an Oracle database to write some vendor data we receive during one of our workflow processes - this data will be used for reporting purposes. It will be a standalone table - no relationship to any other tables.
We don't want to use our application (website) database because it takes an act of **** to update that database in production, and this data will be used by our team only to provide a report to our marketing users. We can't create a new database because our DBAs are a weird bunch and denied that request.
That leaves us with wanting to add this table to our TS database. Has anyone done anything like this? I realize we may lose a bit of support if we mess with that database, but are there any other reasons why this would be a bad idea?
Find more posts tagged with
Comments
Adam Stoller
Presumably the table(s) you would be using for your own purposes would not, in any way, conflict with the tables that TeamSite uses in those databases - right?
If that's the case, I think the Support violation is negligible - but if you ever need to drop and re-create those databases, or perhaps in an upgrade [?] it is possible you might lose your custom data.
Of course that's just my guess / opinion...
Migrateduser
Correct - the new table has no dependency on any of the existing tables and vice-versa. I had thought of the possibility that we might lose the table during an upgrade, but I think we'd be smart enough to tabe a snapshot of the DB beforehand. I think.
Thanks for the response - I was hoping it wouldn't be anything worse than what you said.
Rick Poulin
Seconding fish's response. Have put custom tables in that schema before, for similar reasons. In the worst case, A/I would require dropping the user and recreating it, so you just need to have a way to export/import the custom objects and data and you're fine (just don't create your objects with the same prefixes that iwov tends to use, obviously
)
2.png
Garth McMillan
I've also added custom tables as well as adding addition columns to existing tables.
I've not had any issues myself, but as others mention, there are obvious risks.
Migrateduser
We have multiple tables in the shared database which is used by Teamsite. We upgraded the Teamsite system from 7.2.1 -> 7.3.2 -> 7.4.1 on development environment without any problems (We took proper backups of the tables but nothing went wrong with database.). Things are stable for us dev servers.
OS : Solaris-10
Database : Oracle 10g