﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged T-SQL, Programming, Visual Basic 6</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, Programming, Visual Basic 6 posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Introduction to ADO - The Command Object</title><description>The third article in a four part series, this week Andy shows how to use the command object to work with stored procedure parameters.



</description><guid>http://www.sqlservercentral.com/articles/Stored+Procedures/introductiontoadothecommandobject/535/</guid><pubDate>2007/02/09</pubDate><link>http://www.sqlservercentral.com/articles/Stored+Procedures/introductiontoadothecommandobject/535/</link></item><item><title>Data Dictionary from within SQL Server 2000</title><description>Mindy explores the metadata stored in SQL 2000 to show you how to produce a simple and useful data dictionary!

</description><guid>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</guid><pubDate>2005/02/04</pubDate><link>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</link></item><item><title>Managing Jobs Part 3</title><description>This week Andy looks at where, when, and how jobs should be run and why you need to think about those items before you build the job. Part of this is deciding what runs on production servers and what doesn&amp;#39;t.
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart3/936/</guid><pubDate>2003/03/11</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart3/936/</link></item><item><title>Default Values and Named Parameters for Stored Procs</title><description>Are you using default values for your parameters? Using named parameters when you call the proc or passing the values by ordinal? Should you be? Andy thinks 6 out of 10 of our readers will agree with his point of view, we&amp;#39;ll be a little more conservative and guess that 5 of out 10 will be closer.
</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/defaultvaluesandnamedparametersforstoredprocs/882/</guid><pubDate>2003/01/08</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/defaultvaluesandnamedparametersforstoredprocs/882/</link></item><item><title>Restoring Using DMO - Getting File List and No Recovery</title><description>Following up on a question posted in our discussion area, Andy demonstrates how to backup/restore a database using DMO, how to get the list of files to be restored, and how to do a restore with no recovery. Lots of sample code!
</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/restoringusingdmogettingfilelistandnorecovery/823/</guid><pubDate>2002/10/15</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/restoringusingdmogettingfilelistandnorecovery/823/</link></item><item><title>Generating HTML Tables</title><description>In this article Andy looks at one way you can separate your presentation code from your data when you generate HTML tables for simple reports. Lots of code examples so you can see how it works.
</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/generatinghtmltables/749/</guid><pubDate>2002/08/05</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/generatinghtmltables/749/</link></item><item><title>Using Interface-Based Programming Techniques in SQL Server</title><description>Programmers can most commonly relate to interface-based programming in their programming language. This is harder to accomplish in SQL Server though. In this article by Chris Cubley, he shows you how to build interfaced-based SQL.


</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/sql_interface_final/732/</guid><pubDate>2002/07/19</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/sql_interface_final/732/</link></item><item><title>Version Control for Stored Procedures</title><description>Version control for stored procedures isn&amp;#39;t always popular and certainly isn&amp;#39;t easy. Or can it be? Andy discusses a technique he used on a recent project that you might find interesting.
</description><guid>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</guid><pubDate>2002/05/10</pubDate><link>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</link></item><item><title>Performance Comparison: Data Access Techniques</title><description>Architectural choices for data access affect performance, scalability, maintainability, and usability. This article focuses on the performance aspects of these choices by comparing relative performance of various data access techniques, including Microsoft® ADO.NET Command, DataReader, DataSet, and XML Reader in common application scenarios with a Microsoft SQL Server™ 2000 database.</description><guid>http://www.sqlservercentral.com/redirect/articles/620/</guid><pubDate>2002/03/01</pubDate><link>http://www.sqlservercentral.com/redirect/articles/620/</link></item><item><title>Data Dictionary from within SQL Server 2000</title><description>Mindy explores the metadata stored in SQL 2000 to show you how to produce a simple and useful data dictionary!

</description><guid>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</guid><pubDate>2005/02/04</pubDate><link>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</link></item><item><title>Reducing Round Trips - Part 2</title><description>Last week Andy started a discussion of the various ways you can reduce the number of round trips to the server. This week he continues by looking at a method he used recently to do client side caching of data to eliminate the round trip altogether. Gotta read it!
</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/</guid><pubDate>2002/02/06</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/</link></item><item><title>XML Data Solutions</title><description>This sample is provided in conjunction with the MSDN Magazine article, &amp;#34;SQL Server 2000 and XML: Developing XML-Enabled Data Solutions for the Web.&amp;#34; This article presents and compares five data access approaches, using a variety of technologies including ASP and ADO, XSLT, and DirectXML. Once built, the solutions are compared on the basis of their speed and efficiency.
</description><guid>http://www.sqlservercentral.com/redirect/articles/575/</guid><pubDate>2002/01/18</pubDate><link>http://www.sqlservercentral.com/redirect/articles/575/</link></item><item><title>Introduction to ADO - The Command Object</title><description>The third article in a four part series, this week Andy shows how to use the command object to work with stored procedure parameters.



</description><guid>http://www.sqlservercentral.com/articles/Stored+Procedures/introductiontoadothecommandobject/535/</guid><pubDate>2007/02/09</pubDate><link>http://www.sqlservercentral.com/articles/Stored+Procedures/introductiontoadothecommandobject/535/</link></item><item><title>HOWTO: Run Singleton SELECT Queries in a Visual Basic Client</title><description>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. </description><guid>http://www.sqlservercentral.com/redirect/articles/540/</guid><pubDate>2001/11/26</pubDate><link>http://www.sqlservercentral.com/redirect/articles/540/</link></item><item><title>Using COM to Output Queries to a Text File</title><description>This article presents a method of outputting the results of a query as a tab delimited text file using COM.

</description><guid>http://www.sqlservercentral.com/articles/Advanced+Querying/usingcomtooutputqueriestoatextfile/360/</guid><pubDate>2001/07/20</pubDate><link>http://www.sqlservercentral.com/articles/Advanced+Querying/usingcomtooutputqueriestoatextfile/360/</link></item><item><title>Executing Multiple Scripts in a Folder using the ScriptRunner Utility</title><description>Ever have a large batch of scripts you need to run? It takes a while if you have to open each one in Query Analyzer and execute it. One of our readers proposed an alternative - take a look the small app Andy Warren wrote to make doing this task a breeze.
</description><guid>http://www.sqlservercentral.com/articles/Administering/scriptrunner/292/</guid><pubDate>2001/06/14</pubDate><link>http://www.sqlservercentral.com/articles/Administering/scriptrunner/292/</link></item></channel></rss>