Understanding SQL Server Role and Access Inspection Through a Data Model
A practical explanation of how SQL Server stores users, roles, permissions, schemas, and objects, and how to inspect database access using system views.
Practical notes on enterprise integration, Azure Integration Services, and modernization.
A practical explanation of how SQL Server stores users, roles, permissions, schemas, and objects, and how to inspect database access using system views.
Posts filtered from the Integration category.
A practical explanation of how SQL Server stores users, roles, permissions, schemas, and objects, and how to inspect database access using system views.
Azure Integration Services provides flexible options for building cloud-based integrations, from simple startup workloads to enterprise-grade platforms. Services like Logic Apps, Azure Functions, and Service Bus offer different plans, including Consumption, Standard, Basic, and Premium. The right choice depends on actual business and technical needs such as volume, security, networking, scalability, and reliability. Cost optimization is not about choosing the cheapest plan, but choosing the right plan for the right requirement.
Azure Logic Apps is excellent for orchestrating integration workflows, but some scenarios are easier to manage with code. This blog explains how Azure Functions can complement Logic Apps by handling complex validation, custom transformations, data enrichment, reusable business logic, and file processing. By keeping Logic Apps as the orchestration layer and using Azure Functions for custom processing, integration solutions can become cleaner, more reusable, easier to test, and simpler to maintain.
SaaS has transformed how startups and enterprises adopt software with its pay-as-you-go model and scalability. However, as systems become distributed, integration becomes critical. Choosing the right SaaS product is not just about features—it’s about how well it fits into your ecosystem and communicates with other systems. Strong API and event-driven capabilities are essential to ensure seamless data flow and long-term scalability.
Azure AI Foundry brings together Azure OpenAI, AI Services, and Content Understanding into a single platform, offering access to 11,000+ models. It allows you to create AI projects with multiple agents, each tailored for specific use cases. A key capability is agent actions, where agents can trigger workflows such as Azure Logic Apps to interact with backend systems like ERP and CRM. This enables reuse of existing integrations while letting AI act as a decision layer. Although still evolving, it shows strong potential for connecting AI with real business processes.
Azure Logic Apps is evolving with agentic capabilities, introducing conversational and autonomous workflows. Conversational workflows rely on human input to guide execution, while autonomous workflows operate based on triggers and AI-assisted decisions within defined boundaries. By combining model inputs with external data, these workflows become more context-aware. While promising, current implementations show some inconsistencies, as the feature is still in preview. It represents an important step toward more adaptive, AI-driven integrations.
A practical explanation of how SQL Server stores users, roles, permissions, schemas, and objects, and how to inspect database access using system views.
Azure Integration Services provides flexible options for building cloud-based integrations, from simple startup workloads to enterprise-grade platforms. Services like Logic Apps, Azure Functions, and Service Bus offer different plans, including Consumption, Standard, Basic, and Premium. The right choice depends on actual business and technical needs such as volume, security, networking, scalability, and reliability. Cost optimization is not about choosing the cheapest plan, but choosing the right plan for the right requirement.
Azure Logic Apps is excellent for orchestrating integration workflows, but some scenarios are easier to manage with code. This blog explains how Azure Functions can complement Logic Apps by handling complex validation, custom transformations, data enrichment, reusable business logic, and file processing. By keeping Logic Apps as the orchestration layer and using Azure Functions for custom processing, integration solutions can become cleaner, more reusable, easier to test, and simpler to maintain.
SaaS has transformed how startups and enterprises adopt software with its pay-as-you-go model and scalability. However, as systems become distributed, integration becomes critical. Choosing the right SaaS product is not just about features—it’s about how well it fits into your ecosystem and communicates with other systems. Strong API and event-driven capabilities are essential to ensure seamless data flow and long-term scalability.
Azure AI Foundry brings together Azure OpenAI, AI Services, and Content Understanding into a single platform, offering access to 11,000+ models. It allows you to create AI projects with multiple agents, each tailored for specific use cases. A key capability is agent actions, where agents can trigger workflows such as Azure Logic Apps to interact with backend systems like ERP and CRM. This enables reuse of existing integrations while letting AI act as a decision layer. Although still evolving, it shows strong potential for connecting AI with real business processes.
Azure Logic Apps is evolving with agentic capabilities, introducing conversational and autonomous workflows. Conversational workflows rely on human input to guide execution, while autonomous workflows operate based on triggers and AI-assisted decisions within defined boundaries. By combining model inputs with external data, these workflows become more context-aware. While promising, current implementations show some inconsistencies, as the feature is still in preview. It represents an important step toward more adaptive, AI-driven integrations.