We have a client that would like to create custom tables within one of the Sitecore content databases, either master or web. Is that a good or bad idea? My own opinion is that is a bad idea, for reasons of security, backup and compatibility.
Add a comment
|
1 Answer
If you really do need just custom tables then yet generally this is a bad idea as it complicates upgrades and maintenance. Usually you'd create an separate database to store the custom tables and data. Use your own DAL and then piggy back of Sitecore's caching so that your custom data is refreshed along with Sitecore's data.
Please provide more information on the data you/the client trying to store. It's pretty rare there is a need for this these days with how flexible Solr/Azure and xDB is for storing this data and connections to custom data via xConnect & Data Connectors etc.
answered Aug 17, 2020 at 21:30
-
This is custom forms data that the Sitecore forms can't handle well, and will have multiple records attached to a form submission. Sounds like the structured data in XConnect is a good fit. Aug 17, 2020 at 21:53
-
Great, hopefully that will work for you. I've not used Sitecore forms much yet to suggest alternatives but it's pretty flexible from what I've seen so you shouldn't have much trouble getting something working. Aug 18, 2020 at 8:30
-
It's possible to create a custom hidden field for Sitecore Forms to store things like the user's IP address, UserAgent, referrer url, etc. alongside with the form data in the forms database. horizontal.blog/2018/11/06/…– TxRegexOct 4, 2022 at 16:14