How To SQL

How to troubleshoot SQL Server error 8645

2007-06-26T06:47:00.001-07:00

SUMMARY

This step-by-step article describes how to troubleshoot SQL Server error 8645. You may receive the error 8645 when there is a high server workload or when the servers are experiencing high memory pressure.

Symptoms

You may see the following 8645 error sporadically:

Error 8645: A time out occurred while waiting for memory resources to execute the query. Re-run the query.

Additionally, you may also see one or more of the following symptoms:

	When new users try to connect to SQL Server, they receive a "login failed" error message.
	Users are disconnected and they receive various error messages.
	CPU usage is very high on the server.
	When you run

Causes

The error message 8645 is raised when memory-intensive queries, such as those involving sorting and hashing, are queued and are unable to obtain the requested memory before a time-out period. SQL Server waits for memory for a length of time that is based on the query wait configuration value. By default, the query wait value is set to -1, which means SQL Server waits for 25 times the estimated cost of the query. If you modify the query wait value to a non-negative number, SQL Server waits for the number of seconds that you specify in the value of the query wait option.

HOW TO: Store and Retrieve an Image File with SQL Server CE and eVB

2007-06-19T11:15:00.000-07:00

SUMMARY

This step-by-step article describes how to store an image file to a Microsoft SQL Server 2000 Windows CE Edition (SQL Server CE) database and how to retrieve the stored image from the database and reconstruct the image file. This article uses Microsoft Embedded Visual Basic as the development platform.

The sections that follow describe how to create an Embedded Visual Basic application that uses two command buttons. One command button stores a .jpg file to a SQL Server CE database. The second command button is for reconstructing the .jpg file from the image data stored in the SQL Server CE database.

How to connect to an Oracle database by using ASP and ADO

2007-06-13T05:28:00.001-07:00

INTRODUCTION

This article discusses how to connect to an Oracle database by using a Microsoft Active Server Pages (ASP) page and Microsoft ActiveX Data Objects (ADO).

MORE INFORMATION

To connect to an Oracle database, you can create an ASP page that contains the following code.

Note

Make sure that the connect string has a valid user ID and password and that the SQL statement references a valid table.

<%@ Language=VBScript %>
   <html>
   <head>
   <title>Oracle Test</title>
   </head>
   <body>
   <center>
   <%
     Set objConn = Server.CreateObject("ADODB.Connection")
     objConn.Open "Provider=MSDAORA;Data Source=<Your_TNSNames_Alias>;User Id=<userid>;Password=<password>;"

     Set objRs = objConn.Execute("SELECT * FROM DEMO.EMPLOYEE")

     Response.Write "<table border=1 cellpadding=4>"
     Response.Write "<tr>"

     For I = 0 To objRS.Fields.Count - 1
       Response.Write "<td><b>" & objRS(I).Name & "</b></td>"
     Next

     Response.Write "</tr>"

     Do While Not objRS.EOF
       Response.Write "<tr>"

       For I = 0 To objRS.Fields.Count - 1
         Response.Write "<td>" & objRS(I) & "</td>"
       Next

       Response.Write "</tr>"

       objRS.MoveNext
     Loop

     Response.Write "</table>"

     objRs.Close
     objConn.Close
   %>
   </center>
   </body>
   </html>

APPLIES TO

-	Microsoft Active Server Pages 4.0
-	Microsoft Internet Information Services 6.0
-	Microsoft Data Access Components 2.8

How To: Connect to SQL Server Using Windows Authentication in ASP.NET 2.0

2007-05-14T19:19:00.000-07:00

This How To shows you how to connect to SQL Server 2000 using a Windows service account from an ASP.NET version 2.0 application. You should use Windows authentication instead of SQL authentication whenever possible because you avoid storing credentials in connection strings and you avoid passing passwords over the network to your database server. You should consider encrypting your connection string to protect server connection details, such as the database server and name. By default, ASP.NET does not impersonate the caller to the database. On Windows Server 2003, you can use the network service account, which has network credentials (machine$), or you can configure an application pool identity. If you configure impersonation to use the original caller, you need to evaluate the scalability of per-user connection pools.

View SQL Link

How to Migrate from Access to SQL Server 2000

2007-05-14T19:17:00.000-07:00

Microsoft Access developers generally consider a move to Microsoft SQL Server for performance, security, and stability reasons. This process is known as upsizing, and developers will find a number of key differences while migrating from Access to SQL Server.

SQL Server and Access are similar but have some major differences. They vary in the way that data is stored and indexed, the data types available, and storage capabilities. Microsoft provides the Microsoft Upsizing Wizard to assist in the migration process. It analyzes your Access database and converts your data and database structure into SQL Server format.

The Microsoft Upsizing Wizard effectively and accurately converts most of your Access database and database objects into SQL Server. However, some features in Access are not supported by SQL Server and vice versa, so it is important that you manually analyze and rectify any potential issues that may arise before, during, and after the migration process. It is also crucial that after conversion, the resulting database manually be inspected to ensure all tables, data, and relationships were correctly migrated.

This paper details:

• What the Upsizing Wizard does

• Preparing your Access database for migration

• Running the Upsizing Wizard

• What to do after upsizing your database

This paper does not cover reasons to upgrade to SQL Server from Access. More information about this can be found in the Microsoft white paper, "What's New and Different When Moving Your Back End from Access to SQL Server 2000."

View SQL Link

How to obtain the latest SQL Server 2000 service pack

2007-05-14T19:16:00.000-07:00

How to obtain the latest SQL Server 2000 service pack

SUMMARY
Microsoft distributes bug fixes in service packs. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled for easy downloading. Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, as well as any new fixes. You do not need to install a previous service pack before you install the latest one. For example, you do not need to install SQL Server 2000 Service Pack 1 (SP1) before you install SQL Server 2000 Service Pack 2 (SP2).

View SQL Link

How to identify your SQL Server version and edition

2007-05-14T19:14:00.000-07:00

How to identify your SQL Server version and edition

SUMMARY
This article describes how to identify your current Microsoft SQL Server version number and the corresponding product or service pack (SP) level. It also describes how to identify the specific edition if you are using Microsoft SQL Server 2000 or Microsoft SQL Server 7.0.

View SQL Link