Recently, while I was scheduling a live meeting for one of my online training sessions, I kept receiving the following error message repeatedly. I had never encountered this type of error before, and despite searching online for a long time, I could not solve this problem.

After several failed attempts, I finally managed to fix this error with the help of Solid Quality Mentors IT Support Mentor – Victor. He suggested that instead of just typing my name in the “To” field, I should clear the cache by pressing CTRL + DELETE or perform force lookup by selecting the contact person from the global directory.

First click on the “To” field in your new email window in MS Outlook and lookup the person’s email from the global directory, as showed in image below.

Now, try to send the email; you will be able to send the invitation successfully!

Reference: Pinal Dave (http://blog.SQLAuthority.com)

I have set up replication at many different organization. One error I quite commonly face is after I have removed replication I can not remove database. When I try to remove the database it gives me following error.

Cannot drop the database because it is being used for replication. (Microsoft SQL Server, Error: 3724)

Fix/Workaround/Solution:

The solution is very simple. Create the empty database with the same name on another server/instance first. Take full back of the same and forced restore over this database.

Do let me know if you have any better idea or suggestion.

Reference : Pinal Dave (http://blog.sqlauthority.com)

This error is quite common and I have received it few times while I was working on a recent consultation project.

Cannot open database requested by the login. The login failed.
Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’.

This error occurs when you have configured your application with IIS, and IIS goes to SQL Server and tries to login with credentials that do not have proper permissions. This error can also occur when replication or mirroring is set up.

If you search online, there are many different solutions provided to solve this error, and many of these solutions work fine. However, I will be going over a solution that works always and is very simple.

Fix/Workaround/Solution:

Go to SQL Server >> Security >> Logins and right click on NT AUTHORITY\NETWORK SERVICE and select Properties

In newly opened screen of Login Properties, go to the “User Mapping” tab. Then, on the “User Mapping” tab, select the desired database – especially the database for which this error message is displayed. On the lower screen, check the role db_owner. Click OK.

In almost all such cases, this should fix your problem.

Reference : Pinal Dave (http://blog.sqlauthority.com)

I am currently traveling on a month-long training assignment for Business Intelligence. For demonstration purposes, I use Virtual PC files and hands-on lab examples for attendees of the training. The size of my VPC file is about 15 GB. Initially, I copy this file to a USB Drive and then move it to other computers, as needed.

Recently, while trying to copy my VPC file to my USB drive I received the following error:

Error Copying File or Folder. Cannot Copy. There is not enough free disk space.

I had never experienced this problem before. I tried copying it a few more times using different copy methods and the command line. No matter what I tried, I received the same error message.  I finally decided to check the file system of the USB drive and discovered that it is FAT32. Filesystem FAT32 only supports a maximum file-size of 4 GB file, where as filesystem NTFS does not have this limitation. I had not come across FAT32 for more that two years and had completely forgotten about this limitation. I re-formatted the USB drive with NTFS. After this, it worked fine and I was able to copy my large VPC file successfully.

I used GUI to format my drive, but if you prefer, you can also do it using Command Prompt.

While this article may not be directly related to SQL Servers, SQL Server Database files can be extremely large at times. If a SQL Expert faces this kind of situation in future, it may be helpful.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Unlike my usual articles today’s article is not at all related to SQL Server but something drove me to include it on my blog. This issue snatched away my precious few hours. It took me over 2 hours to resolve it yesterday, which barred me from doing research on SQL Server. I am sure many people must have faced this issue and the sad part is no solution has been proposed so far.

Let us understand the problem first. I got a brand new printer HP Officejet J4580 All-in-One printer. Support Engineer came along to install it. Fax, Printing, Photocopy – all the functions just worked fine. However, when we tried to scan anything the scanned copy had gray or pink shade on it. No matter what I did, the scanned copy still contained gray/pink shade. The support engineer worked for almost an hour on it but had no clue how to resolve it. We called up HP Support online but to my disappointment they replied with uncooperative attitude- we have never faced this issue so you should never face it. I contact several global HP Support and they suggested re-shipping the complete printer to them so that they can look at it.

The most annoying part was that I kept on telling them that Photocopy worked fine, and only scanning was the issue; it seemed to be a software issue. It was very strange that no one from HP support knew how to fix it. Anyway, I decided to use every search engine available on planet to look for the solution for the same. To my surprise, I was not the only one who was facing this issue; this is quite common but there is no real answer to this problem. Most of the time annoyed users keep on changing computer, ink cartridges or ultimately printer, but no one really talks about its solution.

I was determined to solve this software problem. After attempting nearly every possible setting available on software, I finally found the solution. Please pay attention to the checkbox in the image below. Once it is checked, the saved image will appear as follows:

After the setting was changed, the image came out neatly, without any pink or gray shade.

Hopefully, this article will save some time of those who are trying to make this work and who are not able to find time to read SQL Server due to this issue.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

I had previously written two articles about an intriguing observation of triggers online.

SQL SERVER – Interesting Observation of Logon Trigger On All Servers

SQL SERVER – Interesting Observation of Logon Trigger On All Servers – Solution

If you are wondering what made me write yet another article on logon trigger then let me tell you the story behind it. One of my readers encountered a situation where he dropped the database created in the above two articles and he was unable to logon to the system after that.

Let us recreate the scenario first and attempt to solve the problem.

/* Create Audit Database */
CREATE DATABASE AuditDb
GO
USE AuditDb
GO
/* Create Audit Table */
CREATE TABLE ServerLogonHistory
(SystemUser VARCHAR(512),
DBUser VARCHAR(512),
SPID INT,
LogonTime DATETIME)
GO
/* Create Logon Trigger */
CREATE TRIGGER Tr_ServerLogon
ON ALL SERVER FOR LOGON
AS
BEGIN
INSERT INTO AuditDb.dbo.ServerLogonHistory
SELECT SYSTEM_USER,USER,@@SPID,GETDATE()
END
GO
/* Dropping Database AuditDB */
/* Please note login to Server again will
Produce Errors */
USE master
GO
DROP DATABASE AuditDB
GO

After the database is dropped and we try to login again the following error will be displayed.

Logon failed for login ‘SQL\Pinal’ due to trigger execution.
Changed database context to ‘master’.
Changed language setting to us_english. (Microsoft SQL Server, Error: 17892)

This error could have been evaded if the Trigger was dropped prior to dropping database.

USE master
GO
DROP TRIGGER Tr_ServerLogon ON ALL SERVER
GO

Now, it will not be possible to logon to the database using SQL Server Management Studio. The only way to fix this problem is using DAC. Read more details about DAC  Using a Dedicated Administrator Connection to Kill Currently Running Query. Now let us take a look at the example in our case where I am using windows authentication to logon to the system.

Connect SQL Server using sqlcmd and -A option, which will establish DAC. Running the following command on command prompt will allow you to login once again in the database. I am specifying argument -d master which will directly enable me to logon to master database when DAC is connected.

C:\Users\Pinal>sqlcmd -S LocalHost -d master -A
1> DROP TRIGGER Tr_ServerLogon ON ALL SERVER
2> GO

I hope my explanation on logon triggers, DAC, and sqlcmd is clear to everyone. Let me have your thoughts about my present article.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Just a day ago, I was installing SQL Server Express on backup computer. I only use this computer when I have something to experiment. While installing SQL Server Express I found following error in my error log which prevented successful installation to computer. It was difficult to initially understand the problem by itself, after some try and error I found the solution.

Error: 15372, Severity: 16, State: 1.
Failed to generate a ser instance od SQL Server due to a failure in starting the process for the user instance.  The connection will be closed.

Solution for this error is fairly simple. 

Fix/Workaround/Solution:

For XP:
Delete the directory “c:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS ”

For Vista:
Delete the directory “c:\Users\<username>\AppData\Local\Microsoft\Microsoft Sql Server Data\SQLEXPRESS”

Reboot the system.

Reference : Pinal Dave (http://blog.sqlauthority.com)

I often receive emails from reader requesting solution to following error:

“SQLDUMPER library failed initialization. Your installation is either corrupt or has been tampered with. Please uninstall then re-run setup to correct to correct this problem.” in a modal dialog with the title “SQL Writer”

While searching online there are so many different solution and many time the solution is to reinstall SQL Server. There is no need to reinstall SQL Server or do any complex process. It is very simple to fix this issue.

Fix/Workaround/Solution:

Go to Add/Remove Program in windows Control Panel

Remove “microsoft SQL server vss writer” program

Reboot the computer.

The error should have gone by now. If you prefer you can reinstall SQL Server VSS Writer again.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Posted in Pinal Dave, SQL, SQL Authority, SQL Error Messages, SQL Query, SQL Server, SQL Tips and Tricks, T SQL, Technology ]]> http://blog.sqlauthority.com/2009/05/28/sql-server-fix-error-sqldumper-library-failed-initialization-your-installation-is-either-corrupt-or-has-been-tampered-with-please-uninstall-then-re-run-setup-to-correct-to-correct-this-problem/feed/ 5 pinaldave http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/ http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/#comments Thu, 21 May 2009 01:30:01 +0000 pinaldave http://blog.sqlauthority.com/?p=4840 ]]>

Regular readers of my blog are aware of the fact that I have written about this subject umpteen times earlier, and every time I have spoken about a new issue related to it. Few days ago, I had redone my local home network. I have LAN setup with wireless router connected with my four computers, two mobile devices, one printer and one VOIP solution. I had also formatted my primary computer and clean installed SQL Server 2008 into it. Yesterday, incidentally, I was sitting in my yard trying to connect SQL Server located in home office and suddenly I stumbled upon the following error. Finding the solution was the most infuriating part as it consumed my precious 10 minutes.

Let us look at few of the common errors received:

An error has occurred while establishing a connection to the server.

(provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 5)

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1326)

I eventually found the resolution to this error on this blog itself; so I was saved from hunting for the solution. I am sure there are a number of developers who had previously fixed this error while installing SQL Server 2008 or SQL Server 2005 but in due course forgot the right solution to this error. This is just a quick refresher. Make sure to bookmark this as you never know when you would need this solution.

Let us check into the steps to resolve this error.

1) SQL Server should be up and running.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Services, and check if SQL Server service status is “Running”.

In addition, ensure that your remote server is in the same network. Run “sqlcmd -L” in your command prompt to ascertain if your server is included in your network list. You can even find tutorial for the same here SQL SERVER – Find All Servers From Local Network – Using sqlcmd – Detect Installed SQL Server on Network.

I have confronted numerous situations when these nerve-wracking errors crop up, and most of the time when I try to troubleshoot I notice that SQL Server services are neither running nor installed. If SQL Server is not installed as default instance SQL Server Browser should be running together with it; we will explore this further in Topic 5.

2) Enable TCP/IP in SQL Server Configuration

When two or more SQL Servers are connected across network they do all communication using TCP/IP. The default port of SQL Server installation is 1433. This port can be changed through SQL Server Configuration Manager. TCP/IP should be enabled for SQL Server to be connected.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP

Right Click on TCP/IP >> Click on Enable

You must restart SQL Server Services for all the changes to take effect. Right click and go to menu properties to select location where default port of SQL Server can be changed.

3) Open Port in Windows Firewall

Windows Firewall is very efficacious in protecting the Operating system from all sorts of malicious attacks. By default, many of the ports and services are refrained from running by firewall. Time and again, SQL Server ports are not open in firewall as well. All the ports on which SQL Server is running should be added to exception and firewall should filter all the traffic from those ports. As described, by default SQL Server runs on port 1433, but if default port is changed then the new port should be added to exception. If SQL Server has named instance (another instance besides default instance) is installed, SQL Server browser should also be added to the exception, as described in Step 7.

Go to Control Panel >> Windows Firewall >> Change Settings >> Exceptions  >> Add Port

Make the following entries in popup “Add a Port” and click OK.
Name : SQL
Port Number: 1433
Protocol: Select TCP

4) Enable Remote Connection

Enabling remote connection is another important, yet oft-neglected step that is frequently missed by database administrators while setting up SQL Server. If this feature is turned off SQL Server will function smoothly on local machine, but it will let another server connect to it remotely. By default this feature is ON in SQL Server 2008.

Right click on the server node and select Properties.

Go to Left Tab of Connections and check “Allow remote connections to this server”

5) Enable SQL Server Browser Service

If SQL Server is not installed as default instance but instead installed as named instance and also if there is no specific TCP/IP port configured, it will give rise to the error that is being discussed in this article. If SQL Server Browser service is enabled, it will allow the server to be connected through dynamic TCP/IP port. Enabling this service is a one-time process, as on enabling it once it will apply to all the instances installed on the same server.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Browser

Right Click on SQL Server Browser >> Click on Enable

6) Create exception of sqlbrowser.exe in Firewall

As elucidated in Step 6, sqlbrowser service needs to be enabled for named instance. Windows Firewall may prevent sqlbrowser.exe to execute. So, it is imperative to add exception for the same in windows firewall.

Search for sqlbrowser.exe on your local drive where SQL Server is installed. Copy the path of the sqlbrowser.exe like C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe and create the exception of the file in Firewall, as delineated in Step 3.

7) Recreate Alias

It is getting quite common to create alias of SQL Server and use it in application. This will ensure that in future if any physical SQL Server has to be moved, it will not be required to change any code or connection string. You can simply create alias with the same name pointing to different SQL Server and it will start working instantaneously. I have observed that a couple of times due to internal error while recreating alias this error was fixed.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Native Client 10.0 Configuration >> Aliases

Delete the alias that is giving problem and recreate it with identical parameters.

I have tried my best to include all the methods of fixing this error and if I have missed any, please leave a comment and I will be very glad to include them here. I have put in my effort to encompass this issue in one article that needs to be refereed when any connection error comes up.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Posted in Pinal Dave, SQL, SQL Authority, SQL Error Messages, SQL Query, SQL Scripts, SQL Server, SQL Server Management Studio, SQL Tips and Tricks, T SQL, Technology ]]> http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/feed/ 21 pinaldave http://blog.sqlauthority.com/2009/05/18/sql-server-fix-management-studio-error-saving-changes-in-not-permitted-the-changes-you-have-made-require-the-following-tables-to-be-dropped-and-re-created-you-have-either-made-changes-to-a-tab/ http://blog.sqlauthority.com/2009/05/18/sql-server-fix-management-studio-error-saving-changes-in-not-permitted-the-changes-you-have-made-require-the-following-tables-to-be-dropped-and-re-created-you-have-either-made-changes-to-a-tab/#comments Mon, 18 May 2009 01:30:45 +0000 pinaldave http://blog.sqlauthority.com/?p=4822 ]]>

Today, we will delve into a very simple issue that one of the Jr. Developers at my organization confronted. I have a preference for T-SQL. According to me, all the developers should always use T-SQL instead of Design feature of SQL Server Management Studio (SSMS). In fact, sound knowledge of T-SQL has the potential to make a huge difference in the development of the developer. One issue with using design mode of SSMS is that it sometimes adds too much overhead to the actual code and locks up the complete database. In the earlier version of SSMS, it was quite common to see that even on doing a small change the whole SSMS got hanged and went unresponsive till the operation was over.

The reason for SSMS to go unresponsive is that when some operations (i.e. adding column, changing datatype of any column, etc) happen, it has to do much more work than the actual operation. Let us now examine an operation where we will add a new column to an already existing table.

• Transaction starts.
• When a new column is added SSMS renames the existing table to temp table.
• After that, it creates a new table with new specification.
• Now, SSMS has two tables: copy of  previous table with data and empty table with new structure.
• SSMS now starts moving older data from older table to newer table.
• If there is any error, it rolls back transaction.
• If there is no error, it commits all the previous operations.
• Transaction ends.

This entire operation is very resource intensive and puts lock on SQL Server tables in operation, eventually hanging SSMS.

SQL Server 2008 SSMS has new a feature that averts this issue. SSMS prevents user from running any operation that goes through the above-mentioned process. Let us see an example for the same.

First, create table using the following script in any database.

CREATE TABLE dbo.Table_1
(
ID INT NOT NULL,
First VARCHAR(50) NOT NULL,
Second VARCHAR(50) NOT NULL,
Third VARCHAR(50) NOT NULL
) ON [PRIMARY]
GO

Once the table is created open the table in SSMS by clicking on the table name and selecting “Design.” Try to include another column to the existing table and click on save (CTRL+S). It will prevent it from saving and will emit the following error in popup.

Saving Changes in not permitted. The changes you have made require the following tables to be dropped and re-created. You have either made changes to a table that can’t be re-created or enabled the option Prevent saving changes that require the table to be re-created

I like how SSMS takes stance of displaying warning message and stops user from going further to do operation, thereby preventing hanging of SSMS. However, this feature can cause inconvenience in a situation when one is required to save table using SSMS. If such situation arises, then this feature can be turned off by going to Menu >> Tools >> Options >> Designers >> Uncheck “Prevent Saving changes that require table re-creation”.

This restriction only applies to operation attempted using only SSMS. If modification of tables are attempted using T-SQL in Query Editor, it will work just fine!

Reference : Pinal Dave (http://blog.SQLAuthority.com)

At present, I am running Windows Vista Ultimate as OS in my computer. I have installed SQL Server 2008 developer’s version in my computer.

A couple of months back, I learnt that SQL Server Book On-Line (BOL) update has been released. I usually depend on my Windows Update of SQL Server to install all updates in my OS, so I do not have to  bother myself with installing updates manually.

However, this time I was quite taken aback to find that my computer was not updated with the latest updates released by Microsoft. Further, I noticed that my SQL Server Book On-Line is not up to date. This experience was nerve-wracking, as I expected my computer to have all the latest updates. I probed into the matter and found that there was an issue with some previous incomplete updates available with Windows Update. I was getting vexed with the following error every time I tried to run Windows Update.

Windows Update; Error Code 8000FFFF

I attempted to reboot, uninstall antivirus but had no luck fixing this error. I finally sent out an email to my friend who is expert in troubleshooting OS issues.  He sent me some steps to resolve the issue.

Fix/Solution/Workaround:

After I performed the following steps, windows updated started to work normally and I was able to successfully download all SQL Server related updates.

1. Click on Windows button and search ‘regedit’.
2. Right click on the regedit and “Run as Administrator” (See Image 1).
3. Go to HKEY_LOCAL_MACHINE >> COMPONENTS and look for keys described in steps 4, 5 and 6. In the absence of  any  key  go to  the next step (See Image 2).
4. Find key PendingXmlIdentifier and delete it.
5. Find key NextQueueEntryIndex and delete it.
6. Find key AdvancedInstallersNeedResolving and delete it.
7. Restart the computer.
8. Once restarted now attempt Windows Updates;  it  should work fine now.

Do let me know if this solution helps you.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Just a day ago, one of my friend sent me email requesting help with following error:

is not a valid Win32 application. (Exception from HRESULT: 0×800700C1)

In fact this is not SQL Server error but it is of .NET application. The solution of this error is just changing configuration of IIS7.

Fix/Solution/Workaround:

Go to IIS.
Click on Application Pool.
Look for your web application in application pool.
Go to Advanced Settings by right clicking on previously selected application pool.
Enable 32-Bit Applications by checking it.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Today, we will riffle through a very simple, yet common issue – How to unlock a locked “sa” login?

It is quite a common practice that SQL Server is hosted on a separate server than application server. In most cases, SQL Server ports or IP are exposed to the web, which makes them risk prone. For hackers, System Admin login “sa” is the preferred account which they use for hacking. In fact, a majority of hackers try to hack into SQL Server by attempting to login using “sa” account. Once hackers gain access to server using “sa” login, they get a complete control over the SQL Server.

Hackers apply Brute Force method to hack “sa” login. Brute Force method is an attempt to guess a password using every possible combination. Be it in your machine where SQL Server is hosted or in your domain, if you have a policy setting that disables any account after a certain number of unsuccessful attempts, it will also disable all your SQL Server logins including “sa” login. In this scenario, SQL Server will display the following error:

msg: 18486
Login failed for user ’sa’ because the account is currently locked out. The system administrator can unlock it.

Fix/Solution/Workaround:

1) Disable the policy on your system or on your domain level. However, this may not be the most appropriate option as it will adversely affect your security protection level.

2) If this is a one-time issue, enable “sa” login WITH changing password of “sa” login.

ALTER LOGIN sa WITH PASSWORD = 'yourpass' UNLOCK ;
GO

3) If this is a one-time issue, enable “sa” login WITHOUT changing password of “sa” login.

ALTER LOGIN sa WITH CHECK_POLICY = OFF;
ALTER LOGIN sa WITH CHECK_POLICY = ON;
GO

4) If you are not using “sa” login, switch your authentication from mixed mode authentication to windows authentication to remove your “sa” login account.

5) BEST Practice: Create another user with systemadmin role having the same rights as “sa” login and let “sa” login get disabled. Use the newly created account as this will not be exposed on the Internet and for hackers it will be a tough nut to crack! They will find it difficult to guess the right password and moreover, they will not be able to do Brute Force attack over it.

I am eager to know if there are other options to solve this problem.

If you simply want to change the “sa” password, you can follow my previous article SQL SERVER – Change Password of SA Login Using Management Studio.

Please note that it is not mandatory to reboot SQL Server or restart SQL Server services after changing the password for “sa” login. If you are interested, go through all the comments and bring forth your opinion about this discussion.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

Posted in Pinal Dave, SQL, SQL Authority, SQL Error Messages, SQL Query, SQL Scripts, SQL Security, SQL Server, SQL Tips and Tricks, SQLServer, T SQL, Technology Tagged: hacking ]]> http://blog.sqlauthority.com/2009/04/23/sql-server-fix-error-18486-login-failed-for-user-sa-because-the-account-is-currently-locked-out-the-system-administrator-can-unlock-it-unlock-sa-login/feed/ 5 pinaldave http://blog.sqlauthority.com/2009/04/19/sql-server-fix-sql-server-2008-developer-edition-install-fail-due-to-net-framework-35-missing/ http://blog.sqlauthority.com/2009/04/19/sql-server-fix-sql-server-2008-developer-edition-install-fail-due-to-net-framework-35-missing/#comments Sun, 19 Apr 2009 01:30:41 +0000 pinaldave http://blog.sqlauthority.com/?p=4435 ]]>

It goes without saying that computer running slow is a common problem we all face, a pestering one indeed! Last week, I had to format my computer as it was running at an annoyingly tortoise pace. After formatting it, I installed Visual Studio 2008. When tested Visual Studio 2008 worked all fine. However, when I attempted to install SQL Server 2008, I was confronted with an error.

SQL Server 2008 Developer Edition Install fail due to .NET Framework 3.5 missing

For a couple of seconds, I was in a state of surprise, as I had Visual Studio 2008 and it worked absolutely fine; without .NET Framework 3.5 VS 2008 should have not worked. I had a hard time wrapping my head around this idea. I searched online for the solution and successfully found the following link, which clearly gave explanation to my probing mind. As CSS SQL Server Engineers have already explained it perfectly I will be not talking about the same again, but I recommend this as a good read.

SQL Server 2008, Visual Studio 2008 SP1, and .Net Framework 3.5 SP1 explained

If you have installed VS 2008, install VS 2008 SP1 as well.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

A couple of days back I  had my computer formatted. I reinstalled it with Vista SP1 32bit. Subsequent to installing other indispensable software  I tried to install SQL Server 2005 .  However, it instantly displayed the following error message.

The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine Error:2147749896 (0×80041008).

It was a bit frustrating for me as it was pretty late and I ardently wanted to install SQL Server 2008 right after I was done  with installing SQL Server 2005. I pinged my friend James Locazicoski with the above error message. James came to my rescue with a batch file. I immediately ran the batch file on my server;  it took a while and when it was done it closed itself on vista. I kept my fingers crossed and ran my SQL Server installer right after that.   There was no WMI error to wreck my nerve. I was able to successfully install SQL Server right after that.

Well, this bat file is certainly a life savior. While searching online I found this script at several places, which reflects its popularity and usability. I need help from my readers regarding the following information.

1) Where is the original source of this script?

2) What is this script actually doing?

Once I receive response to both the above questions, I will post the answers  on my blog with due credit to my readers.

Download Batch File Here

Reference : Pinal Dave (http://blog.SQLAuthority.com)

This article revolves around a trivial yet common issue. There might be a set of people for whom the current topic might appear to be insignificant. But I have been asked this question innumerable times, particularly from   people who are frequenting using forums or have blog related to storage and highly availability, which instigated me to write this article.

Here goes this frequently asked question.

Question: Is it possible to restore database if one of the files of .mdf (primary data file) or .ndf (secondary data file) is missing?

Answer: In one word the answer is NO. All the .mdf and .ndf files are mandatory to attach or restore database successfully.  Even though  you have all the transactions stored in .ldf you will not be able to restore the database completely.

I hope this answer removes the cloud of doubt hovering over my targeted readers.

Reference : Pinal Dave (http://blog.sqlauthority.com)

Posted in Database, Pinal Dave, SQL, SQL Authority, SQL Backup and Restore, SQL Data Storage, SQL Error Messages, SQL Query, SQL Server, SQL Tips and Tricks, T SQL, Technology ]]> http://blog.sqlauthority.com/2009/04/10/sql-server-restore-or-attach-database-without-ndf-or-mdf-is-not-possible/feed/ 3 pinaldave http://blog.sqlauthority.com/2009/04/09/sql-server-fix-error-msg-9803-level-16-invalid-data-for-type-numeric-data-type-mapping-for-oracle-publishers/ http://blog.sqlauthority.com/2009/04/09/sql-server-fix-error-msg-9803-level-16-invalid-data-for-type-numeric-data-type-mapping-for-oracle-publishers/#comments Thu, 09 Apr 2009 01:30:39 +0000 pinaldave http://blog.sqlauthority.com/?p=4267 ]]>

My present article talks about an error that you will encounter when connecting to Oracle database using OPENQUERY.

The error that eventuates is as follows:

Msg 9803, Level 16, State 1, Line 1
Invalid data for type “numeric”.

Fix/Solution/Workaround:

As far as I can discern, the above error occurs due to numeric precision or numeric definition mismatch. The number field of SQL Server does not appropriately match with the number field of Oracle. In fact, apart from number field there are several other data types that do not match.

I am including the following sample query having NumberCol that is Integer field of SQL Server and it needs to be converted To_Char to match up. NumberCol can be matched to Numeric in Oracle as well.

SELECT CONVERT(INT, NumberCol) AS NumberCol
FROM OPENQUERY (YourConnectionMethod, 'SELECT TO_CHAR(NumberCol) AS NumberCol FROM RemoteTbl');

Do read the article of MSDN to have a sound knowledge about Data Type Mapping for Oracle Publishers.

Please drop a line to me and let me have your doubts and questions. Your suggestions are always welcome!

Reference : Pinal Dave (http://blog.sqlauthority.com)

My present article covers two fundamental questions.

1) What is the maximum number of columns included in Primary Key Index/Constraint?
2) What is fix/solution for the following error:
Msg 1904, Level 16, State 1, Line 1
The index ” on table ‘dbo.Table_2′ has 17 column names in index key list. The maximum limit for index or statistics key column list is 16.

The same error surfaces when example is created using SSMS.

Fix/Solution/Workaround:
Maximum columns per Primary Key Index is 16. In fact, 16 is the limit for columns per Foreign Key and Index Key.
You cannot have more than 16 columns per Index Key, Primary Key or Foreign Key. So, reduce the columns in those column to less than or equal to 16 columns.

Reference : Pinal Dave (http://blog.sqlauthority.com)

While I was working with SQL Server 2008 IntelliSense, I realized that it was not functioning as I expected. Even after I had enabled IntelliSense it was still not opening any suggestions at all. After a while, I figured out some vital information regarding how to make sure IntelliSense smoothly works all the time without you giving any trouble.

Given below are four different ways through which you can enable IntelliSense.

1) Make sure you are connected to SQL Server 2008 Edition.
IntelliSense does not work with the previous versions of SQL Server.

2) IntelliSense should be enabled.
There are two ways to verify whether IntelliSense is enabled or not.
a) From Toolbar

b) Go to Tools >> Options >> Text Editor >> Transact-SQL >> IntelliSense

3) IntelliSense should be refreshed with the latest changes in database.
a) Press CTRL+SHIFT+R
b) Go to Edit >> IntelliSense >> Refresh Local Cache

4) Go to Tools >> Options >> Text Editor >> Transact-SQL >> General >> IntelliSense
Select Auto List Members and Check Parameter Information.

Reference : Pinal Dave (http://blog.sqlauthority.com)

Recently, one of my regular blog readers emailed me with a question concerning the following error:

Msg 2714, Level 16, State 6, Line 4
There is already an object named ‘#temp’ in the database.

This reader has been encountering the above-mentioned error, and he is curious to know the reason behind this. Here’s Rakesh’s email.

Hi Pinal,
I’m a  regular visitor to your blog and I thoroughly enjoy your articles and especially the way you solve your readers’ queries. I work as a junior SQL developer in Austin. Today, when I started to create a TSQL application, I detected an interesting scenario.

It is a common practice for many of us to use the following statements to create a new object.But when I used local temporary table, i.e.

IF EXISTS (
SELECT *
FROM sys.tables
WHERE name='#temp')
DROP TABLE #temp
CREATE TABLE #temp(id INT )

An error was displayed as:  Msg 2714, Level 16, State 6, Line 4
There is already an object named ‘#temp’ in the database.

On running the statement
SELECT *
FROM sys.tables

I see the object under name column in sys.tables as ,
#temp_______________________________________________________________________________________________________________0000000002E1

As far as I can discern, my SQL Server is writing the above entry instead of #temp. Therefore,  I’m getting the error as table already exists – There is already an object named ‘#temp’ in the database. Can you please explain me why this happens to local temporary table?

Thanks and Sincerely Yours,
Rakesh

Rakesh, your question is noteworthy. Let’s look at the solution first and then we will look into the behavior.

Fix/Workaround/Solution:

In case of Temporary tables, run following T-SQL. Please note do not run this for any physical tables. Additionally, please note to replace #temp with yourtemptable name.

IF EXISTS (
SELECT *
FROM sys.tables
WHERE name LIKE '#temp%')
DROP TABLE #temp
CREATE TABLE #temp(id INT )

However, make sure not to run this for physical tables. Additionally, please note to replace #temp with yourtemptable name.
Local temp tables can be created using hash (#) sign prior to table name. They are visible only in current connection.. When connection is dropped its scope ends as well. It is possible to create and use local temp table with the same name simultaneously in two different connections. In order to allow this behavior SQL Server suffixes name of the local temp table with incremental hex digit, which is reset when SQL Services are restarted. It is because of this reason that when looking into sys table it has to compared using LIKE and ‘%’.

Let me create few temporary tables, and then we will observe how hex numbers are suffixed to local temporary tables.

BEGIN
IF EXISTS (
SELECT *
FROM sys.tables
WHERE name LIKE '#temp%')
DROP TABLE #temp
CREATE TABLE #temp(id INT )
SELECT name
FROM sys.tables
WHERE name LIKE '%#temp%'
END
GO 10

Rakesh and my other readers, I encourage all of you to send me interesting and challenging questions that intrigue you as well as observations that you would like to share. As always, I will try my best to answer all your questions. Also, do send me your valuable opinions regarding this article.

Reference : Pinal Dave (http://blog.SQLAuthority.com)