Articles

Technical Article

Simple OLE DB Provider for XML

The OLE DB Simple provider for XML (XML OSP) can be used to load the hierarchical data that is in an XML document into a read-only ADO recordset. The data can then be read and accessed by using the standard methods of the ADO Recordset object. The XML OSP can be used to provide a different method for working with data that is contained in XML documents.

2001-12-10

1,479 reads

SQLServerCentral Article

Introduction to ADO Part 4 - Combining It All

In three previous articles Andy has done a very basic introduction to the ADO connection, command, and recordset objects. In this wrap up article he talks about how to use the power of ADO client side filtering and disconnected recordsets, then adds some code which shows how to combine all the objects. ADO is not simple, but Andy has done a good job in limiting his dicussion to the things you REALLY need to know about ADO to get started.

5 (1)

You rated this post out of 5. Change rating

2001-12-07

10,239 reads

External Article

Microsoft SQL Server 2000 Security

This document introduces the new security features of Microsoft SQL Server 2000. New features are outlined, and a detailed discussion is provided about how to best implement security in a Microsoft Windows 2000 domain environment. Source code examples are included for developers who want to implement the security model immediately.

2001-12-06

1,547 reads

SQLServerCentral Article

Worst Practices - Depending on the GUI

One of the strengths of SQL Server is its ease of management and administration over other systems. Oracle, DB2, even early versions of SQL Server required command line mastery to make many types of changes. But should you really be using the GUI for most of your tasks?

5 (1)

You rated this post out of 5. Change rating

2001-12-04

6,230 reads

External Article

HOWTO: Run Singleton SELECT Queries in a Visual Basic Client

This article demonstrates how to retrieve a single record from SQL Server by using the IRow interface with a singleton SELECT. The main purpose for this technique is to avoid the overhead of creating a recordset when you are fetching a single record. Because no recordset is actually created, only one read-only ADODB.Record is returned. This is true even if the specified SELECT results in multiple records being returned if a normal ADODB.Recordset is used.

2001-11-26

1,684 reads

Blogs

DATEADD Truncates the Number Parameter: #SQLNewBlogger

By

This was an interesting thing I saw in a Question of the Day submission....

Our SQL Server is Slow! What Do I Do First?

By

Don’t Panic! It’s a vague but common complaint, frequently with no additional details. Before...

Using SQLFluff

By

I thought I didn’t care about linting, and lately, I haven’t written a lot...

Read the latest Blogs

Forums

Dynamic T-SQL Script Parameterization Using Python

By omu

Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...

Eliminate a function by writing out the code is now throwing an error

By stevec883

/* I'm trying to eliminate (write out) this function 'largest_date', but SQL Server 2016...

SQL Server Migration - Redirecting Old Instance Connections to New AG Listener

By Wecks

Hi everyone, I’ve been tasked with migrating a Standalone SQL Server instance to a...

Visit the forum

Question of the Day

A Strange Choice

What is returned when I run this code in SQL Server 2022?

CREATE TABLE CatIndex
( indexval VARCHAR(20)
)
GO
INSERT dbo.CatIndex (indexval) VALUES ('1'), ('2'), ('3')
GO
SELECT CHOOSE(indexval, cast('2025-01-01' AS DATE), CAST('2025-02-01' AS DATE), CAST('2025-03-01' AS DATE))
FROM dbo.CatIndex AS ci

See possible answers