21

Okay let me attempt to give you some answers, basically a lot you are asking is all internal knowledge of the database and core, so actually none of it should be relevant or useful to you (other than just having the knowledge, which is useful I agree ;o). Please keep in mind that the CM database is off limits unless you get instructed by Customer Support to ...


16

The purge tool is just another client of the API. It doesn't touch database tables. It uses standard API calls to clear the histories out. Deleting records from the database will make the system "unsupported", meaning that Tridion support will then have the option of refusing to help you with it in the future. Don't ever do anything to take a production ...


14

Unless it's a really big DLL you are trying to upload, I would expect the database is not well maintained, things like statistics not up to date, which can make it slow upon saves. You can try to increase the query timeout values in the MMC snap-in, but I would check database maintenance first. Does it work after updating the statistics (exec sp_updatestats ...


12

You need two DB Broker DB - It is configured in httpUpload and your Delivery website Session Preview DB - it will be used by Session preview service and this service is consumed by XPM. No separate db for XPM. This db will also configured in storage config of your website. HttpUpload and Odata.svc would be separate websites


10

Best scenario is always to take an "offline" backup, which means: shutdown all SDL Tridion services (also on other servers in case of an outscaled scenario) shutdown IIS (or at least the CMS website) backup the database following MS SQL Server documentation, use a full database backup In case you are doing the backup as part of your standard maintenance ...


10

Apart from Pankaj's reasons, also consider the following: In a production (live) environment, you wouldn't want the CM database running on the front end for security reasons. The usual setup is that the back end system, in this case the Tridion CM is running completely behind a firewall and in a different network than your front end servers, which need the ...


10

For anyone else stuck with this, here's the solution. Oracle 12c introduces multitenancy. With this architecture the Tridion Content Delivery database must be set up in the pluggable database rather than the container database that is the default when you first connect via sqlplus. To switch to the pluggable database you will need to log in "sys as sysdba" ...


9

The safest way is to just schedule purging every once in a while. It's never good idea to do something on the database directly, becides you will lose your support if you will delete something from the database.


9

Having a Tridion CM server connect to a CM DB on a different machine is a very common scenario. Also having multiple CM servers connect to the same CM DB is a supported architecture and we use this to scale out an implementation. As to where you specify the CM DB - on your CM server, access the SDL Tridion Content Manager configuration link located in Start ...


9

You have to unblock the Tridion.Database.Management.dll as described in the documentation (bullet 6, login required)


9

Direct queries are not future proof, In future upgrade your queries might not work, extra effort will go to resolve those. using Select queries You have to understand the DB structure, if you are fine and getting expected results with it, logically i don't see any issue using that. But Core service is SDL recommended approach for all. Never, ever run update ...


9

Changing (or adding) an index may not seem like a big deal (and I would agree with this view) except that it will very likely break the database upgrade scripts whenever you decide to move to a future version. I have had this exact scenario recently where we had to remove the extra indices that were added before being able to successfully run the upgrade. ...


8

It might be easier to use the installation scripts to generate a new UGC database and simply drop (backing up first of course :)) the old db all together?


8

As Nuno says, this feature is not in there. I've not tried using the old Content Porter. An alternative approach using Excel and the CoreService is described here by Ryan Durkin: http://blog.building-blocks.com/creating-custom-pages-using-the-core-service-in-sdl-tridion-2011 This involves a lot more code than your previous approach with Content Porter ...


8

Have you upgraded this code from a lower version? If this error is really occurring when you publish, this error (component.save) implies your templates are trying to perform a write action. This was disabled by default in SDL Tridion 2011. I think you will need to override this new security feature. Scan to the bottom of this post http://www....


8

What are those pages? In Tridion 2013 you can call ICoreService2013.DecommissionPublicationTarget method which will quickly mark everything that was published with particular publication target as unpublished. You can then write a script to delete the pages through any public API. Manipulating the database directly will give you way more troubles than you ...


8

There is no dependency between your CM and CD database other than the version of SDL Tridion, so provided you are using a supported database and client version, you are good to go. The only differences between using Oracle and MS SQL server I have seen in the past was ordering of characters. I remember once that on a production server we were using Oracle ...


7

Only one user needs database access, and that's the "TCMDBUSER" account. The MTSUser account does not need any database permissions. In Tridion CM in 2011, you'll have just one user account (default: TCMDBUSER) and in CD you may have multiple users depending on number of databases. None of these users is a "Tridion user", they're purely DB users. You will ...


7

Your assessment of the dependency of CM on Distributed transactions is 100% correct. It's not only that SDL doesn't support Cloud databases - it will not work. I've heard rumors of people being able to run CM on Oracle RDS, but I can guarantee that at some point (especially if you use add-ons like Translation Manager) you will run into trouble. Regarding ...


7

SQL? The databases are, in principle, off-limits since we may (and do) change the database design regularly and can't guarantee backwards compatibility with anything you do directly on the database. Regarding the log database, this has disappeared a few releases ago - all log events are in the Windows event logs now.


7

The best way forward is to contact SDL Customer Support, propose the changes and see what their thoughts are. Indices are not changing the structure of the data, but you don't want future product upgrades to be blocked either if your indices are in the way of database changes. So to be on the safe side: check with Customer Support or evaluate if the change ...


6

From your description it sounds like when a publication is deleted, Tridion probably wraps all the data changes in a single transaction. For the publication you were deleting, the transaction resulted in the log filling up which caused it to fail AND for the tranaction to be rolled back. Because the transaction was rolled back it was removed from the ...


6

I finally managed to delete the publication, but only by deleting the majority of the content in it first, presumably this made the transaction to delete a small enough size that it managed to push it through. It doesnt answer the question fully, but might be useful for others...


6

You can just Truncate logs. there is a script for truncating the logs. But just confirm that will truncate log effect Your License Support from Tridion, I am not sure about that. here is the link for script TruncateLog


6

EDA_ITEMS_UPDATE is a CM-side stored procedure, so your error is not on the delivery side. I would: Try rendering the same component with a different template Try rendering a different component with the same template And then try to derive some conclusions from those results. Potentially create a new template with the same TBBs and try rendering that? It ...


6

It completely depends on what kind of performance you are looking for, how many concurrent publishing of items will you be doing and what all are your performance benchmarks. Let me tell you a practical example, We so far have done all the implementation (moderately big and huge) where we have kept CD database on the same server as that of CM database and ...


6

As was described in the previous question, there is a valid reason why you can't move those pages. The impact of fiddling with published states is (top of my head): You might not be able to unpublish these pages later on If you republish the page to the same target after you move them, you are effectively moving them on the Content Delivery side too, ...


6

The answers are basically already given, but allow me to summarize in my own view. The separation of the CM and CD database is there for the following reasons: security, you don't want your CM database server to be in a location where it can be exposed to the internet. In the disastrous event that your CD database server is ever compromised, you will at ...


6

Reasons to use Core Service over SQL queries You do not need access to the database server to run Core Service. Often an issue in production environments. Data manipulation - Depending on your requirements it is easy to manipulate/format data as you wish using C#, whether it be save as Excel or Email to a group. Core Service, if built into web application, ...


6

Session Preview is a feature of Experience Manager that allows editors to make, and then view, updates to content across multiple pages without having to continually check-in and republish the content. It also ensures that if Editor B updates (a different piece of content on) the same page that Editor A is working on, then this is also reflected in what ...


Only top voted, non community-wiki answers of a minimum length are eligible