I installed SQL Server 2016, basic install, don’t know if JSON is “activated” but I’ve seen a post where it explains how to activate, so should not be a problem for DB.
However I have no experience with JSON in scripts …
It won’t be that simple.
Ticket tags I think have a single column on ticket table from memory and are stored in json. Ie a json array per ticket with all ticket tags within it
I think the table you are looking for is probably ‘Tickets’. The column that holds the ticket tags is ‘TicketTags’ and there is another one “TicketNumber”. You can check this is what you want by using the simple query
SELECT TicketNumber,TicketTags from Tickets
(depending on how many tickets you have you may like to limit the output with a WHERE clause, but that is up to you).
You will now now be able to confirm you have the correct table and you can see the structure of the ticket tags. This will vary depending on what tags you are using, in my case it is [{“TN”:“Discount Rate”,“TT”:0,“TV”:“10”}], you should see something similar. By comparing the tags on different rows you can see what is fixed by samba and what is your data. You can now modify your data making sure you don’t alter the structure of the tag and update the database using
UPDATE Tickets SET TicketTags = ‘add your modified ticket tag here with the apostrophes’ WHERE TicketNumber = ‘add your ticket number here with the apostrophes’;
Once you have tested this with one ticket and checked you get the desired result, as you have 600 rows to update with a repetitive query I suggest you build the text of the query in Excel in bits then use the & function to join the bits to give you 600 very similar queries. You can then transfer that to whatever you are using to run the query (SSMS).
Whilst the above process works, I would add the proviso that messing with the database in this way is a potentially dangerous exercise, so make sure you take a backup before you start