Tag Archives: cloud computing

Standard

Posted by

Posted on

March 19, 2025

Posted under

Azure Databricks

Comments

Leave a comment

Azure Databricks – Query to get Size and Parquet File Count for Delta Tables in a Catalog using PySpark

Managing and analyzing Delta tables in a Databricks environment requires insights into storage consumption and file distribution. In this blog, we will explore a PySpark query that lists all Delta tables under a specified catalog, retrieving their details, including table size and the number of parquet files.

🚀 Why This Query is Useful?

  • ✅ Comprehensive Overview: Lists all Delta tables under a given catalog.
  • ✅ Storage Insights: Displays table size in Bytes, MB, GB, and TB.
  • ✅ File Count: Helps identify partitioning and performance optimization opportunities.
  • ✅ Automation Ready: Easily adaptable for different catalogs and use cases.

🔍 The Query: Fetching Delta Table Details

The following PySpark script extracts metadata using the DESCRIBE DETAIL command and consolidates the results into a single DataFrame:

📌 Code Implementation

from pyspark.sql import DataFrame

# Fetch all DESCRIBE DETAIL queries
describe_queries = spark.sql("""
    SELECT 'DESCRIBE DETAIL ' || table_catalog || '.' || table_schema || '.' || table_name AS sql_query
    FROM system.information_schema.tables
    WHERE table_catalog = 'Your_Catalog_name_JBCatalog'  --CHANGE THE REQUIRED CATALOG
    AND data_source_format = 'DELTA'
""").collect()

# Execute each query and collect results
results = []
for row in describe_queries:
    query = row["sql_query"]
    detail_df = spark.sql(query)  # Run DESCRIBE DETAIL for each table
    results.append(detail_df)

# Combine all results into a single DataFrame
if results:
    final_df = results[0]
    for df in results[1:]:
        final_df = final_df.union(df)
    
    # Add sizeinMB, sizeinGB, sizeinTB columns
    final_df = final_df.withColumn("sizeinMB", final_df["sizeInBytes"] / (1024 * 1024))
    final_df = final_df.withColumn("sizeinGB", final_df["sizeInBytes"] / (1024 * 1024 * 1024))
    final_df = final_df.withColumn("sizeinTB", final_df["sizeInBytes"] / (1024 * 1024 * 1024 * 1024))
    
    display(final_df)  # Just display the output without storing it
else:
    print("No Delta tables found in the fraud catalog.")

📊 Breaking Down the Query

1️⃣ Querying Delta Tables

  • Uses system.information_schema.tables to fetch all Delta tables under a specified catalog.
  • Constructs DESCRIBE DETAIL queries dynamically for each table.

2️⃣ Executing DESCRIBE DETAIL

  • Iterates over the collected queries and runs DESCRIBE DETAIL on each Delta table.
  • Stores results in a list of DataFrames.

3️⃣ Combining Results

  • Unifies all DataFrames into a single DataFrame using union().
  • Computes additional columns for table size in MB, GB, and TB.
  • Displays the final result in Databricks.

📢 Key Takeaways

✔️ Quickly analyze Delta table metadata to understand storage and file distribution. ✔️ Optimize table performance by evaluating the number of Parquet files. ✔️ Scale storage efficiently by monitoring table sizes at different units. ✔️ Adaptable across catalogs by modifying the table_catalog filter.

📌 Let us know if you have any questions or need further enhancements! 🚀

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Standard

Posted by

Posted on

September 3, 2024

Posted under

Azure Managed Instance

Comments

Leave a comment

Creating JobSchedule Failed on Azure SQL Managed Instance

Introduction

Azure SQL Managed Instance (MI) is a powerful cloud-based database service that provides near-complete compatibility with SQL Server, along with the benefits of a managed platform. However, while working with SQL Managed Instances, you may occasionally encounter errors due to differences between on-premises SQL Server and Azure SQL environments.

In this blog post, we’ll explore a specific error encountered when attempting to create a JobSchedule in SQL Server Management Studio (SSMS) on an Azure SQL Managed Instance. We’ll break down the error, identify the root cause, and guide you through the steps to resolve it. Additionally, we’ll discuss important lessons learned to prevent similar issues in the future.

Issue

When trying to create a new JobSchedule named ‘DBA – Database Copy Only backup’ in SSMS on an Azure SQL Managed Instance, the following error message was encountered:

TITLE: Microsoft SQL Server Management Studio

Create failed for JobSchedule ‘DBA – Database Copy Only backup’. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=14.0.17289.0+((SSMS_Rel_17_4).181117-0805)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobSchedule&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

SQL Server Agent feature Schedule job ONIDLE is not supported in SQL Database Managed Instance. Review the documentation for supported options. (Microsoft SQL Server, Error: 41914)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.00.2000&EvtSrc=MSSQLServer&EvtID=41914&LinkId=20476

BUTTONS:
OK

Understanding the Error:

The error message indicates that the JobSchedule creation failed because the ONIDLE scheduling feature is not supported in Azure SQL Managed Instances.

Key points from the error message:

  • The failure occurred during the execution of a Transact-SQL statement.
  • The ONIDLE feature, which may be supported in on-premises SQL Server instances, is not available in Azure SQL Managed Instances.
  • The version of SSMS used might not be fully compatible with Azure SQL Managed Instance features.

Possible Causes:

  1. Outdated SSMS Version: Using an older version of SSMS that lacks the necessary updates for working with Azure SQL Managed Instances.
  2. Unsupported Feature Usage: Attempting to use a scheduling feature (ONIDLE) that isn’t supported in the Azure SQL environment.
  3. Compatibility Issues: Mismatch between the SSMS client version and the Azure SQL Managed Instance, leading to unsupported operations.

Resolution

To resolve this issue, the primary solution is to update SSMS to the latest version. This ensures compatibility with Azure SQL Managed Instance and the supported feature set.

Step-by-Step Guide to Resolve the Issue:

Step 1: Verify Current SSMS Version

Before updating, check the current version of SSMS installed.

How to Check:

  1. Open SSMS.
  2. Click on “Help” in the top menu.
  3. Select “About”.
  4. Note the version number displayed.

Step 2: Download the Latest SSMS Version

Download the latest version of SSMS from the official Microsoft link.

Download Link: Download SQL Server Management Studio (SSMS)

Instructions:

  1. Click on the above link or paste it into your web browser.
  2. The download should start automatically. If not, click on the provided download button on the page.
  3. Save the installer (SSMS-Setup-ENU.exe) to a convenient location on your computer.

Step 3: Install the Latest SSMS Version

Proceed with installing the downloaded SSMS setup file.

Installation Steps:

  1. Close any running instances of SSMS.
  2. Locate the downloaded installer and double-click to run it.
  3. Follow the on-screen prompts:
    • Accept the license agreement.
    • Choose the installation directory (default is recommended).
    • Click “Install” to begin the installation process.
  4. Wait for the installation to complete. This may take several minutes.
  5. Once installed, click “Close” to exit the installer.

Note: The latest SSMS version as of now supports all recent features and ensures better compatibility with Azure SQL Managed Instances.

Step 4: Reattempt Creating the JobSchedule

After updating SSMS, retry creating the JobSchedule.

Steps:

  1. Open the newly installed SSMS.
  2. Connect to your Azure SQL Managed Instance.
  3. Navigate to SQL Server Agent > Jobs.
  4. Right-click on Jobs and select “New Job…”.
  5. Configure the job properties as required.
  6. Navigate to the Schedules page and create a new schedule without using unsupported features like ONIDLE.
  7. Click “OK” to save and create the JobSchedule.

Expected Outcome: The JobSchedule should now be created successfully without encountering the previous error.

Step 5: Validate the JobSchedule

Ensure that the JobSchedule is functioning as intended.

Validation Steps:

  1. Verify that the job appears under the Jobs section in SSMS.
  2. Check the job’s history after execution to confirm it runs without errors.
  3. Monitor the job over a period to ensure consistent performance.

Additional Considerations:

  • If the error persists, review the job’s configuration to ensure no unsupported features are being used.
  • Consult the official Microsoft documentation for any environment-specific limitations or additional updates required.

Points Learned

  1. Importance of Keeping Software Updated:
    • Regularly updating tools like SSMS ensures compatibility with the latest features and prevents unexpected errors.
    • Updates often include bug fixes, performance improvements, and support for new functionalities.
  2. Understanding Environment Compatibility:
    • Azure SQL Managed Instance differs from on-premises SQL Server in terms of supported features. Always verify feature support based on the specific environment to prevent configuration issues.
  3. Effective Error Analysis:
    • Carefully reading and understanding error messages can quickly point to the root cause and appropriate solutions.
    • Utilizing provided help links and official documentation aids in resolving issues efficiently.
  4. Proactive Maintenance Practices:
    • Regularly auditing and updating database management tools is a best practice to maintain smooth operations.
    • Implementing monitoring and validation steps post-configuration changes ensures system reliability.
  5. Utilizing Official Resources:
    • Relying on official download links and documentation ensures the authenticity and security of the tools being used.
    • Community forums and support channels can provide additional assistance when facing uncommon issues.

Conclusion

Encountering errors in Azure SQL Managed Instances can be challenging, but with a systematic approach to diagnosing and resolving issues, such obstacles can be efficiently overcome. In this case, updating SSMS to the latest version resolved the compatibility issue causing the JobSchedule creation error. This experience underscores the critical importance of maintaining up-to-date software and understanding the specific features supported by different SQL Server environments, especially when working with cloud-based services like Azure SQL Managed Instance.

By adhering to best practices in software maintenance and error resolution, database administrators and developers can ensure robust and uninterrupted database operations, thereby supporting the critical applications and services that rely on them.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Standard

Posted by

Posted on

August 16, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

SQL Server 2022 and Big Data Clusters: A Comprehensive Guide

SQL Server 2022 brings transformative enhancements to Big Data Clusters (BDC), making it a powerful platform for managing and analyzing large-scale data across diverse sources. This exhaustive blog explores the latest updates and features in SQL Server 2022 Big Data Clusters, including data virtualization, big data analytics, and the unified data platform. We’ll also delve into a step-by-step implementation guide and provide a detailed business use case, demonstrating the practical applications and benefits of these advancements.

Business Use Case: Financial Services and Risk Analysis 💼

Scenario: A global financial services firm operates in multiple markets, offering a wide range of services including investment banking, asset management, and retail banking. The firm handles vast amounts of data from various sources, including transaction data, market data, customer profiles, and external economic indicators. The firm aims to leverage big data analytics to enhance risk assessment, detect fraudulent activities, and optimize investment strategies.

Challenges:

  1. Data Silos: The firm deals with data stored across multiple, isolated systems, including relational databases, NoSQL databases, and data lakes. This fragmentation hinders comprehensive analysis and decision-making.
  2. Scalability and Performance: As the firm’s data volumes grow, it faces challenges in scaling its infrastructure and maintaining performance during complex analytics operations.
  3. Real-Time Analytics Needs: The firm requires real-time insights to respond swiftly to market changes, detect anomalies, and make informed investment decisions.
  4. Data Security and Compliance: Handling sensitive financial data necessitates robust security measures and compliance with regulatory standards, such as GDPR and SOX.

SQL Server 2022 Big Data Clusters provide an integrated solution that addresses these challenges, enabling the firm to consolidate data, perform advanced analytics, and derive actionable insights.

Key Enhancements in SQL Server 2022 Big Data Clusters 🌐

1. Data Virtualization 🧩

Overview: Data virtualization is a core feature of SQL Server 2022 Big Data Clusters, allowing organizations to integrate data from disparate sources without the need for data replication or movement. This capability is particularly beneficial for financial services firms, where data often resides in various formats and systems.

Technical Details:

  • PolyBase Integration: PolyBase serves as the cornerstone of data virtualization in SQL Server 2022. It allows querying data from external sources such as Oracle, MongoDB, Hadoop, and other SQL Servers as if they were part of the local SQL Server database.
  • Data Federation: The data federation feature enables seamless querying across multiple data sources, providing a unified view of data. This is achieved through the use of external tables and data source connectors.
  • Performance Optimization: Enhancements in query performance and data retrieval speeds, thanks to optimizations in data source connectors and query execution plans, make data virtualization more efficient.

Business Impact:

  • Comprehensive Risk Analysis: The financial services firm can aggregate data from various systems, including market feeds, customer transactions, and external economic indicators, to create a comprehensive view of financial risks. This integrated approach enables more accurate and timely risk assessments.
  • Reduced Data Redundancy: By leveraging data virtualization, the firm can avoid the costs and complexities associated with data duplication and storage, as there is no need to physically consolidate data from different sources.

2. Enhanced Big Data Analytics 📊

Overview: SQL Server 2022 Big Data Clusters enhance the capabilities for big data analytics, allowing organizations to process and analyze large datasets with advanced tools and technologies.

Technical Details:

  • Apache Spark Integration: Apache Spark is integrated into the Big Data Clusters environment, providing a powerful engine for large-scale data processing and analytics. Spark supports various workloads, including batch processing, streaming analytics, and machine learning.
  • Data Science and Machine Learning Tools: The platform includes built-in support for popular data science languages such as R and Python, and tools like Jupyter Notebooks. This integration facilitates the development and deployment of machine learning models and advanced analytical workflows.
  • Scalable Data Processing: Big Data Clusters are designed to scale out horizontally, accommodating growing data volumes and complex computational tasks. This scalability is crucial for handling high-throughput data streams and intensive analytics workloads.

Business Impact:

  • Advanced Fraud Detection: The firm can leverage machine learning models to identify patterns and anomalies in transaction data, helping to detect and prevent fraudulent activities in real-time.
  • Predictive Analytics for Investment Strategies: By using predictive models, the firm can forecast market trends and optimize investment portfolios, enhancing decision-making and maximizing returns.
  • Customer Segmentation and Personalization: Advanced analytics enable the firm to segment customers based on behavior and preferences, allowing for targeted marketing and personalized financial services.

3. Unified Data Platform 🔗

Overview: SQL Server 2022 Big Data Clusters offer a unified data platform that integrates data storage, data management, and analytics. This platform provides a cohesive environment for building and deploying data-driven applications.

Technical Details:

  • Kubernetes-based Architecture: The platform is built on Kubernetes, an open-source container orchestration system. This architecture offers flexibility, scalability, and ease of management, making it ideal for deploying and managing big data applications.
  • Multi-Workload Support: The platform supports multiple workloads, including transactional, analytical, and data science workloads, within a single environment. This integration facilitates the seamless transition of data between different stages of the analytics pipeline.
  • Security and Compliance: SQL Server 2022 Big Data Clusters include robust security features, such as encryption at rest and in transit, role-based access control (RBAC), and auditing capabilities. These features help organizations meet stringent regulatory requirements and protect sensitive data.

Business Impact:

  • Streamlined Operations: The unified data platform simplifies data management, reducing the operational burden on IT teams and enabling them to focus on delivering value-added services. This is particularly important for large financial institutions with complex data ecosystems.
  • Enhanced Security and Compliance: The platform’s built-in security features ensure the protection of sensitive financial data, helping the firm to comply with regulations such as GDPR, SOX, and PCI DSS. This compliance is critical for maintaining customer trust and avoiding legal penalties.

Implementation Guide: Setting Up SQL Server 2022 Big Data Clusters 🛠️

Implementing SQL Server 2022 Big Data Clusters involves several key steps, from preparing the infrastructure to deploying and configuring the cluster components. This guide provides a detailed roadmap to help you get started.

Step 1: Prepare the Environment 🌱

  1. Infrastructure Setup:
    • Ensure you have the necessary hardware and network infrastructure to support Big Data Clusters. This includes high-performance storage solutions, sufficient memory, and robust network connectivity.
    • Consider using a cloud-based Kubernetes service, such as Azure Kubernetes Service (AKS), for scalability and ease of management. This option provides a managed environment that simplifies cluster deployment and maintenance.
  2. Install Kubernetes:
    • Set up a Kubernetes cluster as the foundation for Big Data Clusters. This involves configuring the control plane and worker nodes, as well as setting up necessary Kubernetes components like etcd, kubelet, and kube-proxy.
    • Use tools like kubectl and Helm to manage Kubernetes resources and deployments.

Step 2: Deploy Big Data Clusters 🚀

  1. Big Data Cluster Deployment:
    • Use the SQL Server Big Data Clusters deployment wizard or command-line tools to deploy the cluster. The deployment process includes setting up the SQL Server master instance, data pools, storage pools, and compute pools.
    • Configure cluster components such as the control plane, data plane, and application services. The control plane manages cluster operations, while the data plane handles data storage and processing.
  2. Configure Data Virtualization:
    • Set up PolyBase to enable data virtualization. This involves configuring PolyBase services, creating external data sources, and defining external tables.
    • Connect to external data sources, such as SQL Server, Oracle, Hadoop, and MongoDB, using PolyBase connectors. This setup allows you to query and integrate data from various sources seamlessly.

Step 3: Set Up Analytics and Data Science Workflows 🔬

  1. Deploy Apache Spark:
    • Install and configure Apache Spark within the Big Data Cluster. This includes setting up Spark clusters, configuring Spark workloads, and integrating with other data services.
    • Set up Spark jobs for data processing, machine learning, and analytics. Use tools like Apache Zeppelin or Jupyter Notebooks for interactive data exploration and analysis.
  2. Data Science Tools:
    • Integrate R and Python environments for data science and machine learning. This involves installing necessary packages and libraries, setting up development environments, and configuring access to data sources.
    • Deploy Jupyter Notebooks or other interactive data science tools to facilitate the development and testing of data science models. These tools provide a collaborative environment for data scientists and analysts.

Step 4: Manage and Secure the Cluster 🔒

  1. Security Configuration:
    • Implement role-based access control (RBAC) to manage user permissions and access to data and services within the cluster. Define roles and assign permissions based on the principle of least privilege.
    • Enable data encryption at rest and in transit to protect sensitive data. Configure SSL/TLS for secure communication between cluster components and data sources.
  2. Monitoring and Maintenance:
    • Set up monitoring tools to track the health, performance, and utilization of the Big Data Cluster. Use tools like Prometheus and Grafana for real-time monitoring and alerting.
    • Regularly update and maintain the cluster to ensure optimal performance and security. This includes applying software patches, updating Kubernetes and SQL Server components, and performing regular backups.

Conclusion: Unlocking the Power of Big Data with SQL Server 2022 Big Data Clusters 🌟

SQL Server 2022 Big Data Clusters offer a comprehensive solution for managing and analyzing large-scale data. The platform’s advanced features, including data virtualization, enhanced big data analytics, and a unified data platform, empower organizations to overcome the challenges of data integration, scalability, and real-time analytics.

For the financial services firm in our use case, these capabilities translate into more effective risk management, fraud detection, and investment optimization. By leveraging advanced analytics and machine learning, the firm can gain deeper insights into market trends, customer behavior, and potential risks, enabling data-driven decision-making and a competitive edge.

SQL Server 2022 Big Data Clusters are not just for financial services; they can be applied across various industries, including healthcare, retail, manufacturing, and more. Whether you’re a data scientist, IT professional, or business leader, this platform offers the tools and technologies needed to unlock the full potential of your data. 🌐

Stay tuned for more insights into SQL Server 2022 features and how they can transform your data strategy. 🚀

For more tutorials and tips on SQL Server, including performance tuning and database management, be sure to check out our JBSWiki YouTube channel.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.