SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘microsoft data engine’

FIX: SQL Server Has Fatal Exception When Attempting to Shrink Database

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.

FIX: SQL Server Exception Encountered in CQDynArray::Resize

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.

FIX: Restore of a Database Gives Error 4038 Due to Malformed Media Set

Symptoms
When a database is backed up to multiple disk files, and one of the files in the backup set is deleted and then used again in the same backup set to back up a database, a restore of the database using this backup set may fail with the following message:

Server: Msg 4038, Level 16, State 1, Line 1
Cannot find file ID 1 on device ‘d:\north2.bak’.
Server: Msg 3013, Level 16, State 1, Line 1
Backup or restore operation terminating abnormally.
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.

Description of Service Pack 4 for SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

Symptoms
This release of Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0 Service Pack 4 (SP4) provides updates for the database components of a SQL Server 7.0 or MSDE 1.0 installation. This article introduces the following information about SP4:
Service Pack versions and the removal of Service Pack 4
How to download andto extract Service Pack 4
How to install Service Pack 4
How to redistribute database components and Service Pack 4 client components
Explains the issues of running Service Pack 4 that affect sites
Resolution
IntroductionService pack versionsRemoving SP4Downloading and extracting SP4Disk space requirements for SP4Extracting Database Components SP4Service pack installationBack up SQL Server databasesMake sure the system databases have sufficient free spacePrepare cluster configurationsStop applications before you run the Service Pack 4 Setup programInstall Database Components SP4Restart servicesRecluster a cluster configurationRestart applicationsInstalling on replicated serversInstalling SP4 on a server that provides a remote distribution database for merge publicationsUpgrading a merge Publisher that receives new subscriptions to SP4 from the original release of SQL Server 7.0Installing SP4 on a merge replication SubscriberRunning SP4 replication with earlier versions of SQL ServerUpdating Access 2000 (Jet 4.0) merge replication SubscribersRedistributing Database Components SP4 client componentsDocumentation notesUpgrading client-only computers after you install SP4Upgrading Japanese database servers to Windows 2000 after you install SP4Applying SP4 to a later versionInstalling SP4 on Windows NT 4.0, Terminal Server EditionNew Troubleshooting GuideReplication enhancements Optimizing replication synchronization Performance enhancements for merge processing of the initial snapshot Merge metadata cleanupChanges in Database Components New database option New sqlservr startup option Change in cursor behavior Changes in SQL Server ProfilerSQL Server clustering white paperData Transformation ServicesExporting to Oracle databasesUsing the DTS Test featureChanges to the Execute Package dialog boxData Transformation Services error messagesUse of the Set keyword in Microsoft Visual Basic scriptsChanges in DTS packages SQL Server Agent proxy account improvementsSQL Server 7.0 and Exchange 5.5The French version of SQL Server Books OnlineRepository changesImporting from DB2 and Informix databasesImproved retrieval of versioned objects