SQL Server

Facebook Twitter

Error Handling in SQL Server – a Background. An SQL text by Erland Sommarskog, SQL Server MVP.

Error Handling in SQL Server – a Background

Last revision 2009-11-29. This is one of two articles about error handling in SQL Server 2000. Configuring the Windows Firewall to Allow SQL Server Access. Firewall systems help prevent unauthorized access to computer resources.

Configuring the Windows Firewall to Allow SQL Server Access

If a firewall is turned on but not correctly configured, attempts to connect to SQL Server might be blocked. To access an instance of the SQL Server through a firewall, you must configure the firewall on the computer that is running SQL Server to allow access. The firewall is a component of Microsoft Windows. Microsoft SQL Server Shutting Down Every Night - Microsoft SQL Upgrade - Network Helpdesk.

I ran across an issue on a client's SQL Server 2005 Express instance.

Microsoft SQL Server Shutting Down Every Night - Microsoft SQL Upgrade - Network Helpdesk

The problem was that at 4:01am every morning the SQL server would just shutdown with the event messages of Service Broker manager has shut down.SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. SQL Server: More light shed on “non-yielding scheduler” and Indexes stats. Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.” - SQL Protocols. This error message, which is associated with the Winsock error WSAENOBUFS and actually comes from Windows rather than SQL Server directly, has two well-understood root causes.

Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.” - SQL Protocols

However, it still stumps people today, probably because there is no single source which explains both root causes and offers solutions for both. Here is a description of the two common situations where you may see this error and quick solutions for each: OS runs out of memory for TCP buffers When a powerful client machine, especially one with lots of RAM, is running an x86 version of Windows, people use the /PAE switch in the c:\boot.ini file to allow applications on that machine to be able to address the full range of memory.

Scan network for SQL Server instances. Scan network for SQL Server instances by Ted Krueger (onpnt) on March 9, 2009 in category Database Administration Microsoft SQL Server Admin.

Scan network for SQL Server instances

Article views: 17,413 Instapaper.

Extended Events

Policy Based Management. Fix problems with programs that can't be installed or uninstalled. Installation - Manually removing sql server 2008. Upgrade from SQL 2005 to SQL 2008 might fail with MsiGetProductInfo error - Microsoft SQL Server Tips & Tricks. Consider a scenario where an upgrade from SQL 2005 to SQL 2008 fails with the following messages while installing Setup Support Files.

Upgrade from SQL 2005 to SQL 2008 might fail with MsiGetProductInfo error - Microsoft SQL Server Tips & Tricks

TITLE: SQL Server Setup failure. SQL Server Setup has encountered the following error: MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{0826F9E4-787E-481D-83E0-BC6A57B056D5}'. Error code: 1605.. Unable to install SQL 2008 due to the remnants of a previous installation - SQLqueries. Sometime remnants of a previous installation/ a failed install can prevent us from reinstalling SQL server I have documented the consequence of one such instance which rendered us to be unable to install SQL 2008 from the server · When we launched the setup we got the following error : SQL Server Setup failure. 1 SQL Server Setup has encountered the following error:

Unable to install SQL 2008 due to the remnants of a previous installation - SQLqueries

How to: Uninstall an Existing Instance of SQL Server (Setup) This article describes how to uninstall a stand-alone instance of SQL Server.

How to: Uninstall an Existing Instance of SQL Server (Setup)

By following the steps in this topic, you also prepare the system so that you can reinstall SQL Server. Consider the following important information before you uninstall SQL Server: Before you remove SQL Server components from a computer that has the minimum required amount of physical memory, make sure that the page file size is sufficient. DROP DATABASE (Transact-SQL) Removes one or more user databases or database snapshots from an instance of SQL Server or user databases from the Windows Azure SQL Database server.

DROP DATABASE (Transact-SQL)

Transact-SQL Syntax Conventions -- SQL Server Syntax DROP DATABASE { database_name | database_snapshot_name } [ ,...n ] [;] -- Windows Azure SQL Database Syntax DROP DATABASE database_name [;] -- Core Syntax (common to SQL Server and SQL Database) DROP DATABASE database_name [;]

Clusters

Day 1 of 31 Days of Disaster Recovery: Does DBCC Automatically Use Existing Snapshot? 31 Days of Disaster Recovery Welcome to my series on Disaster Recovery.

Day 1 of 31 Days of Disaster Recovery: Does DBCC Automatically Use Existing Snapshot?

I will spend the entire month of January focusing on all things related to disaster recovery including topics like corruption, data integrity, data loss, DBCC commands, and more.

Storage Engine

Indexes. CodePlex. Trimming More Transaction Log Fat. In my previous post on streamlining the operations of the transaction log, I discussed two of the most common causes of extra log records being generated: dead weight from unused nonclustered indexes and page split operations (that cause index fragmentation). Assuming you’ve read that post, I mentioned that there are more subtle problems that can be detrimental to transaction log performance, and I’m going to cover these here. Many, Many Tiny Transactions Every so often SQL Server will flush a portion of the transaction log to disk. A log flush occurs whenever: Trimming the Transaction Log Fat. In many SQL Server workloads, especially OLTP, the database’s transaction log can be a bottleneck that adds to the time it takes a transaction to complete. Most people assume that the I/O subsystem is the real bottleneck, with it not being able to keep up with the amount of transaction log being generated by the workload.

Transaction Log Write Latency The latency of write operations to the transaction log can be monitored using the sys.dm_io_virtual_file_stats DMV and correlated with the WRITELOG waits that are occurring on the system. Merrill Aldrich : Visualizing Data File Layout I. Part 1 of a blog series visually demonstrating the layout of objects on data pages in SQL Server Some years ago a gentleman called Danny Gould created a free tool called Internals Viewer for SQL Server. I’m a visual sort of guy, and I always thought it would be fun and educational to make a simple visualizer, like the one he created, in order to view how objects are laid out in SQL Server files, and to use it to demonstrate how operations like re-index and shrink affect the layout of files. To that end, and a little bit reinventing the wheel truth be told, I spent this past holiday creating a simple .NET app that renders the file layout of a database into a color-coded bitmap:

Merrill Aldrich : Visualizing Data File Layout II. Part 2 of a blog series visually demonstrating the layout of objects on data pages in SQL Server Part 1 In Part 1 of this series, I introduced a little demo app that renders the layout of pages in SQL Server files by object. Today I’ll put that app through its paces to show, in vivid color (well, teal, anyway) the destructive power of the famous Re-Index Then Shrink anti-pattern for index maintenance. Error on install : The INSTANCESHAREDWOWDIR command line value was not specified.

I am installing on Windows Server 2008 64 bit. We had to use the command line option, and the server installed fine, but during the installation of the tools, the setup stopped with Unknown error. Here is the extract from my log file(s): Error message in the SQL Server Errorlog file after you upgrade SQL Server 2000 to SQL Server 2005 on a server that is running Windows Server 2003: "Unable to update password policy" SQL Server Trace Flags. SAP on SQL Installation on Mount Points - Running SAP Applications on SQL Server - Site Home - MSDN Blogs. "UNDOCUMENTED" SQL Servers Virtual Columns and Row Cracking.

Locks and Waits

My saved files on SlideShare. Sp_dbmmonitorresults (Transact-SQL) Database mirroring. SQL Server and the “Lock pages in memory” Right in Windows Server. How to tell if you have instant initialization enabled? Using AWE Memory in SQL Server 2000. SQL Server 2005/2008/2012 Setup Checklist. Great SQL Server Debates: Lock Pages in Memory. SetFileIoOverlappedRange Can Lead to Unexpected Behavior for SQL Server 2008 R2 or SQL Server 2012 (Denali) - CSS SQL Server Engineers. Scripting out SQL Server Logins. How to transfer logins and passwords between instances of SQL Server. Changing the default SQL Server backup folder.

Sp_BLITZ – SQL Server Takeover Script. Immerse Yourself In SQL Server.