Adding New Geo Areas to TR_Geo_Area?

My museum needs to start distinguishing between Connecticut patrons and out of state patrons. I want to add CT as a Geo Area option, so that when I filter in Analytics on our "Top 5 Zips by Ticket Count" it will just give me Connecticut. From previous answers in the forums it seems like I have to go into SSMS first and then add it to the TR_Geo_Area system table. IS that the case, or can I just add the new line directly into the table? I have never touched anything in Geo Area before so I have no idea where to begin. 

Thanks!

Parents
  • From previous answers in the forums it seems like I have to go into SSMS first and then add it to the TR_Geo_Area system table.

    Rows can be added to TR_GEO_AREA in System Tables, via the client. You'll need SSMS or the like to apply that geo area ID to the T_ADDRESS table. 

  • So I can go into Imresario, add "Connecticut" to the TR_Geo_Area System Table, and then the ID attached to that will have to be put into SSMS? Where and exactly how do I do that? I have access to SSMS, but the first time I opened it I immediately closed it because it looked like gibberish. 

  • It would be a simple update, but something you should try in your Test environment first, if you have any hesitation about updating T_ADDRESS in live.

    It could be as simple as updating all addresses with state = 'CT' to the new geo_area, but, are any of those already assigned a geo_area? Think about whether or not you want to replace the existing value with a new one, if yes. (Each address in T_ADDRESS can have only one geo_area.)

  • Ok, I will try it in TEST first. We haven't done a LIVE to TEST copy in a while, but there should be enough data in there for me to test it. 

    My other problem is I don't know how to get to the T_Address table. It's not listed in System Tables anywhere, and like I said SSMS is gibberish to me. 

  • T_ADDRESS isn't a system table, so you won't find it there. It contains a row for every address in your database, i.e. likely thousands of rows.

    In a new query window in SSMS connected to your Test environment, execute "select count(*) from T_ADDRESS" to see how many. Or, "select distinct geo_area from T_ADDRESS where state = 'CT"" to see if any CT addresses already have a geo_area.

Reply
  • T_ADDRESS isn't a system table, so you won't find it there. It contains a row for every address in your database, i.e. likely thousands of rows.

    In a new query window in SSMS connected to your Test environment, execute "select count(*) from T_ADDRESS" to see how many. Or, "select distinct geo_area from T_ADDRESS where state = 'CT"" to see if any CT addresses already have a geo_area.

Children