Advice on exploring/ understanding / profiling a database with SQL?

  • So I've got decent experience in relational databases via power bi and report building. But I'm starting to dive into SQL for one things and to better understand some of the databases that I work with. The hard part is my work has been TERRIBLE at documenting things like keys and schemas. So I end up diving in and searching for common keys and building joins and testing filters to get an understanding before moving back into power bi to build the actual report.

    The hard part is that the database I'm working with has tables that can join in multiple ways, require a primary and secondary key to properly join (figured that out) and there's this one table I would love to pivot, but it's all non-numerical data and has around 58 possible headings that I have identified. So I can't agregate the data.

    On top of that I've got duplicate measurements taken as a QC assurance system and only the first one is considered the valid result. I have yet to find the official flag marking that second result as a QC test.

    So what are some good methods to start profiling a database? And then starting to build filters, but verifying they're not dropping results I need. If I can get this figured out it will help a lot of my team members.

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • Quick questions:

    1. Excuse my ignorance, but what does QC stand for?
    2. Have you looked at the sys.dm_sql_referencing_entities and sys.dm_sql_referenced_entities views?
    3. Do you need to profile the data or is this all on schema level?

    😎

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply