CastorDoc and SSRS

SQL Server Reporting Services (SSRS) is a server-based report generating software system from Microsoft.

integration mockup

Why Castor x SSRS makes sense?

SQL Server Reporting Services (SSRS) is a server-based report generating software system from Microsoft. It is used for creating, deploying, and managing mobile, paginated, and interactive reports. However, managing and finding the most relevant reports and understanding the lineage between database tables and reports can be challenging. Castor, on the other hand, is designed to make it easy to find the most relevant data assets with a powerful search optimized by popularity and advanced filtering options. Castor also provides lineage between the database tables and other assets like reports or dashboards. Therefore, integrating Castor with SSRS makes sense as it will enhance the user experience by making it easier to find relevant reports quickly, understand their lineage, and ultimately trust and have visibility in the data. This will enable businesses to make better decisions faster, which is critical in today's fast-paced world.

How does Castor x SSRS integration work?

Castor ingests metadata from SSRS. This metadata is then transformed and displayed in Castor. The metadata displayed can include report names and descriptions, queries frequently run against your data, frequent users of data assets, data lineage links, data quality tests, last data table update, technical and business tags, and more. Castor organizes this metadata in an intuitive interface for both technical and business users. The ingestion process takes about 30 minutes to set up, and the metadata is available in Castor the next day. It is important to know that Castor does not access the data itself, only metadata. This ensures that your data stays safe and secure while Castor delivers as much value as possible.

API Access: if any metadata element is not available in CastorDoc's native integration, you can ingest it with our comprehensive API.

Important:  CastorDoc do not access the data itself, only metadata. This ensure that you data stays safe & secure while CastorDoc delivers as much value as possible.

What does CastorDoc help you with?

Castor enables you to scale your self-service analytics strategy without losing control. We are designed with real use-cases in mind :

🔎   You work with data you don't know

Your boss asks to build a report on "Churn for Premium Users in 2021". You need to find the relevant dataset, understand the meaning of its column, and use it fast.

✅ Reduce by 95% the time to find the right data asset (source : Lyft)

🧬   A key employee is leaving

Mike, the data engineer that built the entire data infrastructure is leaving at the end of the month. All the knowledge is in his head. He needs to write it down.

✅ 42% of the work not recovered without knowledge management (source : 360Learning)

👩🏽‍🌾  A new employee onboarding

Elsa, data analyst, arrived last week. She has no idea what data the company stores or how it is used. She spends hours asking around to gather knowledge.

✅ New hires are autonomous after day 1

💣  A data pipeline is late

Nelson, customer success analyst, refreshes the "daily active users" dashboard every two minutes. The data hasn't arrived yet. He wants to know what is happening.

✅ 5x less Slack messages on #ask_data

🗺️  No one knows where personal information are

Camila, from data governance, has to map all personal information to comply to GDPR requirements. She needs a list of all data assets and their location.

✅ 70% of employees have access to data that they shouldn’t (source)


snowflake icon
redshift icon
bigquery icon
synapse icon
postgreSQL icon
mysql icon
databricks icon
dbt icon
looker icon
tableau icon
powerbi icon
slack icon

Get in Touch to Learn More

See Why Users Love CastorDoc
Fantastic tool for data discovery and documentation

“[I like] The easy to use interface and the speed of finding the relevant assets that you're looking for in your database. I also really enjoy the score given to each table, [which] lets you prioritize the results of your queries by how often certain data is used.” - Michal P., Head of Data