Get flash to fully experience Pearltrees
An SQL text by Erland Sommarskog , SQL Server MVP. Last revision 2009-11-29. This is one of two articles about error handling in SQL Server 2000.
Firewalls work by inspecting incoming packets, and comparing them against a set of rules. If the rules allow the packet, the firewall passes the packet to the TCP/IP protocol for additional processing. If the rules do not allow the packet, the firewall discards the packet and, if logging is enabled, creates an entry in the firewall logging file.
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 ProtocolsThis 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.
Policy Based Management
Upgrade from SQL 2005 to SQL 2008 might fail with MsiGetProductInfo error - Microsoft SQL Server Tips & TricksConsider a scenario where an upgrade from SQL 2005 to SQL 2008 fails with the following messages while installing Setup Support Files. TITLE: SQL Server Setup failure.
Sometime remnants of a previous installation/ a failed install can prevent us from reinstalling SQL server
This article describes how to manually uninstall a stand-alone instance of SQL Server. 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 use this procedure to uninstall SQL Server:
To use DROP DATABASE, the database context of the connection cannot be the same as the database or database snapshot to be dropped.
31 Days of Disaster Recovery Welcome to my series on Disaster Recovery. 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.
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).
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.
Part 1 of a blog series visually demonstrating the layout of objects on data pages in SQL Server
Part 2 of a blog series visually demonstrating the layout of objects on data pages in SQL Server
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.
On a server that is running Windows Server 2003, you upgrade from Microsoft SQL Server 2000 to Microsoft SQL Server 2005. However, an access violation occurs during the startup of the SQL Server service. Additionally, the following error message is logged in the SQL Server Errorlog file: spid4s * Exception Address = 78144D3A Module(MSVCR80+00014D3A) spid4s * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION spid4s * Access Violation occurred reading address 00000006 Unable to update password policy Messages that resemble the following are logged in the SQLSetup0005_ _SQL.log file: Service MSSQL$ with parameters '-m SqlSetup -r -T4022 -T4010' is being started at MSI (s) (80:A4) [12:46:36:153]: Running as a service.
Locks and Waits