Organize these notes: West Division whole team right yeah I think Megan that ticket has been updated so I believe what we did is we were only you know we were able to create a view in the I think it was best the general views so in order to kind of address immediate need that's what we have done you know since it was just one object so it would shouldn't be a major issue so that's what you know that that's what we get so the object is created in the W general use as of today and the users can access yeah so that's the update from church so drew just to confirm we didn't go with the DB to DB right I mean we just replicated the view kind of yeah the reason was I believe Sean yeah we could not replicate DB2DB access for query grid views that's right so that was the technical issue what they faced so pat and team we just went ahead and created that view in the West channel views as of today hope that helps it looks like that was from Friday I don't know if we ever got confirmation from caitlin's team if that's working for them because the ticket currently close this closed yes so from a standpoint I think I mean that works in the one view instance did we check all views then that are needed for this is that the only one we need for this or if there are others what is the plan for those so the ticket I think opened only for this object if you scroll up this is just for one definitely definitely agree because it's the first one we ran across but again the DB DB access solves for all of the ones we'll run across I don't know how many we're gonna run across maybe this is the only one that we're good but you know which the suggestion here is to change the way we're doing Business Today so we need to be able to maintain the same stuff that we're doing today so if we run across more we will be opening tickets for those if that happens I I don't know if we can forecast which ones we need and so maybe we can go back to Stephanie and Dan and team and say hey can we assess if there's others but if we run across the others what is the protocol is it another ticket or you know I'm trying to solve again get back to that same state same state that we talked about in September that we're not at today and and so now we're doing work arounds to try to do that so we just need a protocol going forward if we run across this again yeah I think my put on that pat would be since it sounds like the team had to do create a respective view um to to replicate the DB access we probably would want to wait and see if there's any other ones that pop up like this before we go and and do that um just to minimize the kind of duplicate views there but that that would be my my put I don't know if there's a better way on our side or on your side where if we could figure out which ones might need that type of access and and do it proactively um I don't know if anyone on the DX side has thoughts on that or yeah I think uh pattern team So what we can do is we this is just the beginning right so we can so this is kind of we solve the issue we will also see if there is another alternative for like you know TB to TB which is not kind of as of today it's not happening for the query grid views because it has a foreign server and it has to talk to you know from across the platforms if if there is anything else comes up you will let us know probably we can take the similar method approach as of today but I don't think you know it should be uh like a major concern or something right in the sense if you have say for example this RSP user base hist is called within the some of the other procedure or within the other views in the WD journal is it can still refer to that as the WD channel use RSP user base hist since its resides in the same database as of today right that say that again So what I meant is uh so we created the view in the WD channel views right so you created the one view and deputy journal views correct yes so that should suffice in a sense if you're if you're a another view within the WD journal views is calling this view then that needs to be changed to point W channel views because the RSP user base list is now called within that so that's the kind of only approach that we are seeing or in the procedure if you have it Dan Yep I guess it's the only one for now yeah if I'm understanding your question question question correctly but we haven't gone through all of them right we haven't gone through everyone where as we go through and we're opening the tickets so yes this meets the need for the if you're asking does this does this resolve for the one for the one I guess it's our our main question this is kind of goes back is how do we how do we write route tickets appropriately how do how do you want to see those because you know as as they come in as we discover issues you know how do we route them how do we get them in front of the right people as quickly as possible for this so if this issue comes up again do we just create the ticket and then CC Megan but Megan and you guru now like I guess kind of what's what's that protocol the protocol then it should be the same in the sense you can see that you know the ticket was opened to 8250 B it should be the same approach and yes you can on top of that you can also e-mail us OK alright the best stand because that's probably the quickest way to get the ticket info entered in the ticket for what needs to be provided and then you know pinging guru and if it's an access thing like this then we can work with the team to get it done quickly OK how that works I mean that that works for us I mean as we find issues and if it becomes more widespread then I think we can regroup and then get something more global in place but if it's just a one off and we're good then we're good OK alright thank you so I guess we'll just check with Caitlin that this is all working for her it looks like we closed the ticket out before we did that so I can send her a a note just to check that everything's good and then I think this one will be closed and then if anything similar pops up we'll follow that process and and provide access quickly for you guys that's good OK alright anything else access related before we change topics did we go back and confirm that all the access for individual IDs was complete I know we were running into some of those early I don't know if we've all worked those out but I know Dan had a number of access ask and those were on items or on AD's that were previously submitted for access grants do do we clear all that up yeah that's a good question pat so I looked back at some of those tickets and what I noticed was it looked like the PII views where where people were having issues so I think we just need to confirm that their access got added for both the regular and the PII views um guru shine maybe that's something you can help me follow up on I don't think I heard back from the team that that double check was done yeah we can check on that uh for the Pi views you know typically we have to get approval right so that might have been pending and that's why I don't know I don't have the ticket numbers in front of me to check so OK I'll forward my e-mail to you it has all that info because we did like a batch of mixed list of service accounts and and TI's for access to to the query grid views including the PII views so which it should have all gone gotten through and approved already but I just wanted to do a double check like pat was saying because we had a couple cases where it looked like it was around the Pi views so I'll I'll forward that over to you Sean if you weren't on it and you can help me just double check that sure I think we've got all the ones that tickets were submitted for resolved but we just want to make sure there's not any other stragglers out there that we're going to run into yeah I'll check from my side too if there's any pending um access tickets open OK thank you thanks but that's a good good question anything else access related the only kind of question I had is this view that we've created are duplicated in West's database so is it being accessed by ad hoc users like NTD's and such or is it service accounts or that's a question for pat and Dan in general no yeah in general nor what WD journal use spaces in general used either by a processing or be the teams that build the the the data products to process it's not hitting by like individual data analysts but the same people that would be hitting it over in query reviews or the same person people hitting it at WD journal views this is by design so again goes back to the question back in the day of like this is the same same as we're doing today but yeah no it's the people building the processes or the process in it itself alright that's good that's I wanted to confirm that because you know NTID users should be going through very fabricating the object directly OK it's anything else access related OK I think we'll switch over to the other topic then which was related to the data type issues so manos you want to give the team an overview of what fix we're putting in place for that yeah sure so yeah hello so pattern team so I know like in last one or two weeks we got many tickets where you know one of the major issue was that there's a discrepancy between the data type what we have in query grid versus existing W journal views so we went back we internally discussed that I mean idea was to retain the same retrieve which is coming from the data lake so that we are single source of truth but we understand it's impacting the division so we we we decided to keep the exact same digit type in query grid what is there in NW so last 2-3 days we did this apple to apple comparison we are testing those query grid view in the temp database everything has been verified and ensuring that whatever data type you see today in new general views we have the same data type in query grid so testing is done and earlier we were thinking we will be deploying that tomorrow but to avoid that any any issue during this Thanksgiving so we thought of we will be deploying those views again on Monday and the only change here is we are just typecasting the data type to same as they are in blue but otherwise rest all logic remains same so with this change I mean we have tested with all the queries what we have got from the division but we are hoping since you will have the exact same data type most of your query you know or I would say all of your query should work without any issue you know where you were seeing earlier you were seeing some issue related to the reader type discrepancy so hopefully that Monday once deployment is done we'll we'll let this group know and I think you should not see any discrepancy on any of the view yeah so I think just to kind of summarize some of the data type issues that have come up from both your teams and and some of the other division teams is like the the issue with the space and having to add the trim function so that should be going away with this change um I think there is also like the character type to to varchar type that should be also being changed with us as well I think there was a couple other specific things right that we've seen Manish I mean yeah in short like we are just doing apple to apple comparison if it's in N.W.A it's defined at car 16 and you know earlier it was where cat 1024 in query grid view but now with this change we are making sure it's defined as care 16 in category view as well so you'll have the same exact same data type what is there in current W table or view do you guys have any thoughts or concerns with this III hopefully this is going to help you guys out but have you guys implemented any workarounds so far that that your concern may be impacted I think what we've talked through with some of the other teams is likely anything that's been added as a workaround should should still work but is there anything that you guys think may be impacted that you want us to take a look at before we deploy no I think this is great I think it'll work perfect OK and do you know of anything else on your teams no and stuff I think you put that ticket you I think I remember that they space thing right that time we were talking about OK let's use this compared with this space and also all that won't be needed now I think every should everything will work as without any change as expected right OK yes agree we said hey ready state let's go that was on like 920 where we all said hey we're good with the 12:15 we're at 1121 and we're still not in a ready state from our perspective so the delay is already been experienced right it it's not what's coming it's what's what's gone past so I mean we'll take a look at it nick shut up you're competing now with the AD account migration right it's the same team doing both changes so we have to we can only focus on one at a time and that's why the 90 days was called out for both of those so now we're in a place where can you shut up trying to figure out which one gets to get missed right something's gonna not get done by the 15th and from our perspective AD is more important than the CSG if we can do both great but I mean we're already at a point now where if we're at 10% on CSG and we got this time to go you know I think the timing aspect is like hey let's we have to pick one to focus on I'm assuming everybody would agree that the AD account because that's a security finding right that's a that's a compliance thing that is the thing that has to be done if something's gonna slip by national exception couldn't slip I don't know if this group knows of what's going on with the national exception but that couldn't slip that had to be done by yesterday and so that was the first priority right AD is the second priority CSG's third on the list all of those are happening within 25 days of each other so we're just saying that if something's gotta move was we've had 20 we've attempted 27 or something like that we have 21 tickets in and we held six of them that I mean that's going to be a significant push so let's hope the Monday thing works in in apples apples resolves everything right that would be the best case and and then they you know I think we're only going by to the end of the year right just finishing it up after AD account OK that's good yeah yeah it goes fast when it's apples to apples because all you do is change a reference recompile and test right that's that's really what we were hoping for is hey it says CS journal views RSB user base right and then you just make that CS query reviews and hit go recompile the process test it works that's the perfect state right that's what everybody's expecting and just what's happening is replace throws an error whereas the air coming in we have to research where the air is coming in is it with the initial couriers at downstream right and so that takes let's go that's taking it from 30 minutes per process and that's being gracious right it might be like 15 minutes and turn it into 4 to 8 hours for process while you wait for tickets and stuff so yeah hopefully Monday we have changed everything this is apple to apple across all the tables is something that we can do yeah we we can do that so much because we have the validation script where when we run it it compare the data type and it tell you OK as so fail so we can even share those results as well OK I think our plan is our plan is when we do the deployment after that we are going to run that validation as well which will kind of confirm the data type 100% that's it OK with that we'll give some confidence as well for your team OK awesome.