SQL Server Q&A

After the process, as customers make their decisions can be useful for advertising.

Problem recognition

The first step for customers is when they realize that they have a specific need or a problem. But sometimes her problem recognize clients unable, if you tell them. Their main motivation for buying a specific product or service are their need for a solution to their problem.

You are in the: it’s up to you to find out what are the needs and concerns of your customers. It is also up to you to show that they have these problems and that you the solution for them. Keep in mind that people have different needs. But according to Maslow hierarchy of needs, there are certain requirements that we all share. Every need is based matched importance. Use Basic and important need of customers, which is relevant for your products and services to motivate and encourage them to buy your product.

Information search

The next step is when customers look for information that will ensure the credibility and the quality of your product. Customers want to ensure that they will make the right decision by choosing your product.

Symptoms
When you attempt to script an object that has a number of large, string descriptions for the value field of its extended properties, an access violation exception may occur, resulting in failure to generate the script. This problem only occurs if you have requested to script the object’s extended properties when generating the script.
An error message similar to the following occurs:

[SQL-DMO]Code execution exception: EXCEPTION_ACCESS_VIOLATIONYou may encounter this problem when you try to script the object by using SQL Server Enterprise Manager or the Query Analyzer Object Browser, or if you are using the Script method in a SQL Distributed Management Objects (DMO) application.
Resolution
The length of the text for the values of the extended properties are long enough so that an internal buffer being used for building the script text is overrun.

Symptoms
Consider the following scenario. In Microsoft SQL Server 2005, you try to run a SQL Server Integration Services (SSIS) package. The SSIS package transfers data between two instances of SQL Server 2005. In this scenario, you may receive an access violation error message. When this problem occurs, the Microsoft Windows Application log contains an event that documents the system error message. The system error message resembles the following:

DTExec.EXE – Application ErrorThe exception unknown software exception (0×40000015) occurred in the application at location 0×7ee8bd9e.Note This problem occurs when Lookup transformations that are in the SSIS package are executed in parallel.This problem does not occur when Lookup transformations that are in the SSIS package are executed sequentially.
Resolution
This problem occurs when Lookup transformations from multiple data flow tasks share the same cache area.Lookup transformations may share the same cache area when the textin the SQLCommand property of one Lookup transformationthat isin a data flow taskis the same asthe textin the SQLCommand property of a Lookup transformationthat is in another data flow task.

Symptoms
When you attempt to shrink a database, SQL Server might stop with a Fatal Exception, multiple 816 errors, and a stack dump in the errorlog.
Resolution
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561?(http://support.microsoft.com/kb/254561/) INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0For more information, contact your primary support provider.

Symptoms
Resize is an internal class method that is used to resize an array. PvReplace may incorrectly use the Resize method leading to an exception.
The following, or similar, top of the stack is logged in the SQL Server error log when the problem occurs:

0×0051ea81 Module(sqlservr+11ea81) (CQDynArray::Resize+69)
0×0043acc7 Module(sqlservr+3acc7) (CQDynArray::PvReplace+2e)
.
Resolution
Microsoft has confirmed this to be a problem in SQL Server7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799?(http://support.microsoft.com/kb/274799/) INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0For more information, contact your primary support provider.

Symptoms
Inserting certain Unicode strings into a SQL Server 2000 Windows CE (SSCE) table might cause an SQL INSERT command to fail with an application error, or the application might stop responding (hang) while other programs remain responsive. The symptoms of the problem can vary, but may include messages similar to:

Application <Executable file name> has performed an illegal operation and will be shut down. Fatal Exception 0xC0000005
Resolution
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Microsoft SQL Server 2000 Windows CE Edition 2.0

DateTimeVersionSizeFile name—————————————————————–15-Apr-200314:152.0.5214.01,403,972 bytesSsce20.dllARM
Microsoft SQL Server 2000 Windows CE Edition 1.1

DateTimeVersionSizeFile name—————————————————————–26-Feb-200320:441.1.5026.01,258,496 bytesSsce10.dllARMNote Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.