External Article

Use SSIS to import one cell of an Excel file into SQL Server

Recently I needed to find a method to import one cell of an Excel sheet into SQL Server 2005 using a scheduled job on a 64 bit clustered environment. For example, I have a monthly sales report listing sales per product category, such as Books, Magazines, DVDs, etc. I only want to import the Total Sales amount into SQL Server and this number is located in an Excel file "sales.xls.sheet1.cell.B5". I used to use OPENROWSET to solve the problem, however OPENROWSET requires Microsoft Jet OLE DB Provider which is not available in 64 bit. In this tip I am going to talk about how to use SSIS to accomplish this task easily.

External Article

Configure Windows Firewall to Work with SQL Server

Windows Firewall is an OS level software firewall. It can be a crucial part of OS level security if you are not using other firewall hardware or software. Since I do not have another firewall I have a need to enable Windows Firewall for my SQL Server database server. In this article I go through the process of configuring Windows Firewall for different scenarios along with the associated considerations.

Blogs

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

Read the latest Blogs

Forums

BCA KCP Komp. Taman Kota Tlp (+62 821°3111°179

By kavali.ongole

Jl. Daan Mogot No.KM. 11, Wisma SSK, Kecamatan Cengkareng, Kota Jakarta Barat, Daerah Khusus...

BCA KCP Rantai Mulia Kencana Tlp (+62 821°3111°179

By kavali.ongole

Jl. Pesanggrahan Jl. Puri Kencana No.28 29, Kembangan Sel., Kec. Kembangan, Kota Jakarta Barat,...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers