New Year, New Gear

Start the new year right with a new operating system or book. Be the user who enriches the SQL Server community the most and receive the top price of a full version of Windows XP (a $299 value!). Any SQLServerCentral.com user who helps to build the SQL Server community by submitting a script, posting in the forum or posting an original FAQ is eligible (US and Canada residents only for the first prize in this contest).

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.

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.

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.

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.

Blogs

Backup Techniques for SQL Server on Azure Virtual Machines

By

In the previous blog post I did a quick overview building a SQL VM...

SQLCover 0.5 - Fixes, smaller features and an exciting surprise

By

It has been a little while but I have updated SQLCover to include a...

Switch activity in Azure Data Factory: Container with many IFs

By

(2019-October-16) Developing conditional logic of your Azure Data Factory control flow has been simplified with...

Read the latest Blogs

Forums

SQL Server security after deleting AD group

By jontris

I currently have a scenario where an AD group that was defined as a...

join with GEOMETRY data type

By snomadj

I want to perform something like....   SELECT * FROM a JOIN b ON...

Need help query for current row and previous row

By Adelia

Hye, I've table and data as following, CREATE TABLE [dbo].[WeightStory]( [Idx] [int] IDENTITY(1,1) NOT...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers