SqlServer-QA.net

The following pages were recently modified. Source: Knowledge BaseProduct: Microsoft SQL Server 2005 Standard Edition, SQL Server 2005 Enterprise EditionNotification Contents: New and All Modifications The DHCP support is not available when you install SQL Server 2005 on a Windows Server 2008 failover ...

Within a Database Mirroring session within an automatic failover situation it may fail with the error : ''The server network address ''%.*ls'' can not be reached or does not exist. Check the network address name and reissue the command''. If you suspect DNS as a culprit for failure to connect, then perform a PING against that Server is a good ...

Lately we have been getting complaints that database mirroring setup on few of our client's site were failing with TCP related errors. For more information these sites are involved within the firewall setup and active directory too. Initial workaround is to add a Server name & port record in both networks DNS servers or add both SQL servers ...

The following pages were recently modified. Source: Knowledge BaseProduct: Microsoft SQL Server 2005 Enterprise X64 Edition, SQL Server 2005 Enterprise Edition & SQL Server 2005 Standard EditionNotification Contents: New and All Modifications FIX: An application that is included in SQL Server 2005 may stop responding when you specify a ...

The following pages were recently modified. Source: Knowledge BaseProduct: Microsoft SQL Server 2005 Standard EditionNotification Contents: New and All Modifications How to change the network IP addresses of SQL Server failover cluster instanceshttp://support.microsoft.com/kb/244980/en-US

I hope you will get to see the above error message most often and I say a common question among forums & newsgroups. Few times you might be thinking why it is throwing error even though you are using right credentials to access that SQL Server instance. I have seen such as the basic assumption by those users getting this message believed that ...