What was said
What this says
Current to 13 Oct 26After the demo, Nikhil Rao sent five short questions on roles, production writes, load timing, schema changes and audit documentation. He will grant nothing by email. Hannah Lowe is to answer in writing.
Ask: Nikhil wants a dedicated role that reads source schemas and writes only to its own schema. He wants loads to run after his overnight loads, and documentation an auditor can follow.
Customer view: cautious and process-led. Access goes through the change process and nothing moves on a Friday.
Next: Hannah to answer in writing. Siân Pritchard has not yet said which teams she wants in the first wave.
The thread
Updated 9 Oct 26Messages
- Tom Ashdown 2 Oct 2024 14:50Hi Siân, hi Nikhil, Thanks for your time earlier. Good to see so many of the key-account, collections and complaints people on the call, and I thought the questions were sharp. A quick recap of where we got to, so we are all working from the same page: - The brain would run inside your own Snowflake account, so your data stays where it is today. - The first sources we talked about were the CRM, the call recorder, the helpdesk and the billing data, with more to follow once the first set is stable. - Nikhil had a handful of questions on access and load timing that Hannah did not want to answer from memory. She will put the answers in writing. Nikhil, if you can send me the questions as you would like them answered (roles, schemas, load windows, whatever matters most to you), Hannah will turn them round properly rather than us guessing on a call. No drama if they are rough. Siân, from your side I would like to understand which teams you would want in the first wave, so we can think about what a sensible first phase looks like. Let's get something in the diary for the next step once you have had a think. Best, Tom Tom Ashdown Account Executive, BB-Demo
- Nikhil Rao 3 Oct 2024 14:26Tom, Questions below. Short on purpose. 1. Which role has access? We want a dedicated role for the brain, read on the source schemas and write only to its own schema. Please confirm that is how it is built. 2. Does anything need to write to existing production schemas? If so, which objects. 3. Load timing. Our overnight loads finish before the morning, and I want yours to run after them, not alongside. What is the refresh sequence and when is it finished by? 4. Schema changes. We change source schemas from time to time. What happens to your connectors when a column moves or is renamed? I checked the load history on a similar change last month and it was the downstream tools that broke, not the loads. 5. Documentation. I need something an auditor can follow: which objects are created, which roles, which grants. I will not grant anything by email. Access goes through our change process, and nothing moves on a Friday. Nikhil On 2 Oct 2024, at 14:50, Tom Ashdown wrote: > Nikhil, if you can send me the questions as you would like them answered (roles, schemas, load windows, whatever matters most to you), Hannah will turn them round properly rather than us guessing on a call.