Microsoft OLE DB Provider for SQL Server error ’80004005′
[DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found.

CAUSE

Microsoft OLE DB provider for SQL Server error 80004005, primary occurs because ASP page is unable to connect to SQL Server using connections settings, which you used in connection String.

SOLUTION

There are multiple cause, which can result, microsoft ole db provider for odbc drivers error 80004005 or Microsoft OLE DB provider for SQL Server error 80004005.

I would suggest you to quickly go thru thru this checklist, to ensure everything is correct.

CHECKLIST to FIX Microsoft OLE DB provider for SQL Server error 80004005

• Make Sure there is no syntax error in your connection String, you see multiple examples of Connections Sting here
  • SQL Server 2012
  • SQL Server 2008
  • SQL Server 2005
• Ensure that you have used the Correct parameters in Connection String and there is no Typo Error in SERVERNAME, USER NAME, Datasource name
• Try connect to SQL Server Directly from SQL Server Management Studio using the details, which you specified in the connection string.

There might be a possibility that you can connect to Server by IP address but not by names or you can connect to SQL Server just by typing FQDN which is SQL Server name.DomainNAME but not by just Server NAME. you have specified the instance name , if you are connecting to sql server instance.

• There might be a possibility there is firewall between Application web server , your Machine and SQL Server, so it’s better to try the validate connection directly from Application Server / IIS Server. If SQL Server Management studio is not installed, you can use ODBC from Control Panel\All Control Panel Items\Administrative Tools\Data Sources (ODBC)

If that success, you should be good now but if you fail to connect to SQL Server from application Server using ODBC then validate

• your SQL Server is running
• you can connect to SQL Server using same credentials in connection string directly at SQL Server, if not
• Check SQL Server Authentication setting and make sure it’s running in MIXED MODE
• you might want to check Cannot connect to SQL Server, ERROR 2
• Then try to FIX connectivity by verifying SQL Server is using TCP IP protocol
• SQL Server is enable for remote connections
• SQL Server is running port 1433 else specify port in connection string
• Certificates are working and are not expired, incase Certificates are used.

Ideally, the above checklist should be able to fix Microsoft OLE DB provider for SQL Server error 80004005

Keywords : ole db provider odbc drivers error 80004005 microsoft jet database engine update windows sql server providers data name connection hosting 0×80004005 ms connect

The post Microsoft OLE DB provider for SQL Server error 80004005 appeared first on SQL Server Training | Tutorials | How to's.

Error 15023: User already exists in current database.

Cause : The problem occurs because database users which you see inside the database are “orphan“. Orphan users are those users for which there is no login id associated with this database user. This is true even if there is a login id that matches the user, since there is a GUID (security ID SID) that has to match as well. This can be easily understood by following picture,

This picture has been taken from Jonathan

User – means a user which you find inside a database

LOGIN – A login credentials which you see in security section of Server and use to connect with SQL Server.

Solution / FIX :

The solution is pretty simple, we need to make sure that SID of Login (Server Principal) matches with SID of database user.

To do so we have multiple Options

SOLUTION 1 : Maps an existing database user to a SQL Server login One by One

ALTER USER <Database_User_name> WITH LOGIN = <SQL_Server_LoginName>

Execute the above code, to make a mapping between database user and server login. In case you are using SQL Server 2005 SP1 and older versions then use the following SP

EXEC sp_change_users_login 'Update_One', '<DB_USER_NAME>','<SQL_Server_Login_NAME>';

IF you want to find all Orphan Users in current database, Database Users that are no link to SQL Server Login, use the following SQL statement.

SQL statement, which will list all Orphan Users

USE <YourDB_NAME>
GO
EXEC sp_change_users_login 'Report'
GO

In case you have multiple Orphan users, then it’s pretty time consuming to map user to login one by one, to overcome this problem, we can do all at once using following TSQL statement

DECLARE @username varchar(50)
DECLARE fixusers CURSOR FOR
SELECT UserName = name FROM master..sysusers
WHERE issqluser = 1 and (sid is not null and sid <> 0x0)
and suser_sname(sid) is null
ORDER BY name
OPEN fixusers
FETCH NEXT FROM fixusers
INTO @username WHILE @@FETCH_STATUS = 0
BEGIN
EXEC sp_change_users_login 'update_one', @username, @username
FETCH NEXT FROM fixusers
INTO @username
END
CLOSE fixusers
DEALLOCATE fixusers

this TSQL statement, will check all Logins, weather they have a similar name Database User or not, if it found, this will map the login with user.

NOTE - this Script might give you some errors, if a login doesn’t have a corresponding user, which should be fine and you can ignore those errors, as it has already fixed, what was matched.

Solution 2 :

Drop the Database User and create again and give necessary permission.

The post User already exists in current database. SQL Server Error 15023 appeared first on SQL Server Training | Tutorials | How to's.

SOLUTION :

You need to grant permission to the user to access database and/or to execute stored procedure.

How to grant reader/writer access to SQL database:

1. Log on to SQL Server Management Studio by going Start >> All Programs >> Microsoft SQL Server>>> SQL Management Studio. and suppl user credentials & click OK.
2. In Object Explorer, expand Secuirty, expand Logins, for which you are getting the Error and then expand Security.  Make sure the Login exists else add that user by right click and add and then
3. Right-click Login, and then click Properties for the USER NAME / LOGIN NAME for which you are getting the Error “Cannot open database requested by the login. The login failed”, SQL Server Error 4060
4. 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.

This should fix this error but consider this security recommendation

Recommendation: – Assigning a a DBO privileges to NETWORK SERVICE is security violation as mostly all security standard. Change the application / Service startup account to to dedicated Service account and then give these privileges to dedicated service / application account.

The Similar error has different interfaces. for example, In SQL Server 2012, this get the following Error Message, when you try to access a database, where user don’t have permission for specified database.

The database CRM is not accessible. (ObjectExplorer)

OR this error, when you access the same from Query Window

Msg 916, Level 14, State 1, Line 1
The server principal “hyperion” is not able to access the database “CRM” under the current security context.

OR when you try to access from front End / Application

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

The same solution applies to all these errors.

The post Cannot open database requested by the login. The login failed. SQL Server Error 4060 appeared first on SQL Server Training | Tutorials | How to's.

Cannot write property IsFileStream.This property is not available on SQL Server 7.0. (Microsoft.SqlServer.Smo)

CAUSE

SQL Server Management is unable to set up the default property while creating a database using previous version of SQL Server Management Studio.

SOLUTION

To immediately fix this issue, we can create a database using a Create Database statement using Query Analyzer or we can upgrade a management studio client tool.

In my case, I create a Database using a TSQL statement, which worked perfectly fine.

The post Cannot write property IsFileStream.This property is not available on SQL Server appeared first on SQL Server Training | Tutorials | How to's.

We can configure SQL Server Database Engine, Analysis Services and Integration Services  for High availability but how to Configure Reporting Services on Cluster (SSRS Cluster) for High Availability that too without using a any third party Load Balancing component.

The best way to configure SQL Services Reporting Services on cluster (SSRS Cluster) is to scale out Reporting services environment and have load balancer in place so that Load balancer can automatically forward the requests to multiple Reporting services, which are part of scale out deployment, using some algorithm like round robin etc.

I was being asked by one of my college, how can we configure SQL Server Reporting Services on a cluster (SSRS Cluster) so that an automatic failover can occur without using a Load balancer as the project was on low cost and a low number of active SSRS users.

Let’s take a quick example, where I going to go thru with a SQL Server Reporting Services Cluster Installation.

In the above solution all Users will be accessing Reporting Services by a virtual name “REPORTServer” which has it’s own IP Address : 192.168.5.99

This is the similar configuration as we have for Clustered SQL Server Instance.

STEP BY STEP VIDEO Tutorial to Configure Reporting Services for High Availability in Clustered environment.

STEP 1 – Install Reporting Services on both Nodes and Scale OUT solution, Please check my previous article, ” Installing & Configuring SQL Server Reporting Services on Cluster Environment for High Availability“, here you will find that step by step instructions to configure Both Reporting Services (Nodes) pointing to common Report Database Server.

STEP 2 – Create a Virtual Server Name / IP Address (Client Access Point) in Clustered Services or Application group where you have SQL Services / resources

Enter the Virtual Name, which you want to use for your reporting Services and Enter virtual IP address which you want to configure for reporting Services. In Demo I used “REPORTSERVER” as name and 192.168.5.99 as Virtual IP address for cluster Services.

I have created this Virtual name / IP address for Reporting services in same Resource group as SQL Server as I wanted to go for automatic failover of this Virtual IP / NAME of reporting Services with SQL Server.

If you want reporting services Virtual name should go with SQL Server then add a dependency of SQL Services on Reporting Services IP address.

NOTE - The limitation of this configuration is that SQL Services / Reporting services both will be used by users on Same NODE, which might result some resource contention.

To overcome this issue or in highly used reporting environment, create a dedicated resource group for Reporting services and add Virtual name / IP address in that group.

In this the limitation is you will not be able to create resource dependency and users will able to ping the name / address even if the SQL services are not running. But I believe that should be fine.

STEP 3 – Create a DNS Record and PTR record in DNS Server in my case this is “REPORTSERVER” and point that a Virtual Server Name / IP Address, which we created in previous step using (Client Access Point) in Clustered Services or Application group where you have SQL Services / resources.

That’s it, you are done with SQL Server Reporting Services Cluster Configuration (SSRS Cluster) without load balancer. Now you can access reporting Services on any machine using virtual name and that will support the automatic failover too.

If you have question to any step, check the video, which is inbuilt in this post, that has Step by step instruction and work flow of configuring SSRS cluster without load balancer.

The post SSRS Cluster, How to Install and Configure SQL Server Reporting Service Cluster Configuration for High Availability VIDEO appeared first on SQL Server Training | Tutorials | How to's.

Currently many customer / Business managers are unaware of this fact, how cost effective is to use Microsoft cloud / SQL Server Azure. specially for startups, where buying a software licensing is too costly. I prepared a small example to understand this fact. The very first question is

What are the Key factors for taking decision on hosting data on SQL Server Vs SQL Azure?

Compare SQL Server with Windows Azure SQL Database

Taking a decision between SQL Server (In house Hosting) vs hosting on Microsoft Cloud (SQL Azure) is not a big challenge.

As per my personal experience, decision of hosting Data on SQL Server vs SQL Azure is mainly derived by

• COST  / Financial
• Technical Limitations

Let’s understand these two in details by apple to apple comparison.

In this scenario, let’s take example for startup company and planned a database services solution 3-5 years time frame from cost prospective.

Assumptions

• This is new company and gonna host a website for user interaction
• The initial Database size would be 1 GB
• First Year, marketing team is very active in advertisements etc, because product is still in development phase but application is available to users for first year. During this phase data growth is expected an avg of 1 GB per month. Thus by End of 1st year, our database size is expected to be 13 GB (1 Gb initial and 1 GB per month)
• After a year company is expected to come up with big launch and will advertise in market and expected 5 time growth in second year i.e. 2 Gb Data would be added per month. Thus by End of 2nd  year, our database size is expected to be 13 GB (1 Gb initial and 1 GB per month)
• Third and fourth year onwards company is expecting double his business and expected that 3 GB new Data will be added to a database.
• As product is mature and reach it’s capacity, Year 5 company will have a bit slow growth but will look for more products to launch in market thus data growth would be 2.5 GB per month

So finally this is how the Database size growth chart looks like, based on above assumptions

Both two charts are based this Data for calculation purpose for calculating SQL AZURE Prices

Hosting In house Database Server COST

If you plan to host a in house / in premises SQL Server Database server, then you are gonna pay approx $15,000 for this solution in 5 years time span.

I am assuming that you don’t want to take head ache for security / firewall / redundant Power,

Redundant Internet Backbones, DR etc and will prefer to host inside a vendor hosted datacenter and will pay a monthly rent.

So In our above example, a One time cost of $9,172 in buying software and hardware and will be paying $100 recurring cost for server hosting in Data center, which sill sum up to $15,172 and you need to manage your own server where you will be responsible for hiring a consultant, who will

• Install and Configure SQL Server on a New Server
• Will apply security patches, whenever there is a release
• There is no DR covered in this, if Server fails, your business stops
• Will buy some Antivirus to protect Server.
• Need a DBA to for maintenance, who will be taking backup and other stuff.
• There might be a possibility, Microsoft may come with New Version of SQL Server like SQL Server 2015 and might want to upgrade than , additional headache.
• Need a Windows Consultant to manage windows Server / patches / maintenance same as SQL Server.

Conclusion on COST, the cloud hosting will be a preferred option, if you look at above example, where a SQL AZURE Database (Microsoft Cloud Cost for SQL Azure Database) is costing you $7,592 over a period of 5 years the same solution will cost you approx $15,172, if you decide to host your own SQL Server.

SQL AZURE Database is better Option than SQL Server database / hosting, considering Cost as primary factor and avoiding technical limitations.

But Costing if one part of solution, there are some technical limitations on SQL AZURE, which you should keep in mind, before taking a final decision.

Hosting Database SQL Server Database on SQL Azure / Microsoft Cloud or Building your own Database Server

Compare SQL Server with Windows Azure SQL Database

SQL AZURE PROS and CONS

The Above facts are being taken from MSDN, “General Guidelines and Limitations, SQL AZURE”

SQL Azure, is not only the Services which are being offered by Microsoft on cloud, As on date Microsoft offers following services as part of their Cloud Services Portfolio.

Standard Rates for various Cloud Services at glace:

Windows Azure

• Compute
  • Small instance (default): $0.12 per hour
  • Medium instance: $0.24 per hour
  • Large instance: $0.48 per hour
  • Extra large instance: $0.96 per hour
• Storage
  • $0.15 per GB stored per month
  • $0.01 per 10,000 storage transactions
• Content Delivery Network (CDN)
  • $0.15 per GB for data transfers from European and North American locations*
  • $0.20 per GB for data transfers from other locations*
  • $0.01 per 10,000 transactions*

SQL Azure

• Web Edition
  • $9.99 per database up to 1GB per month
  • $49.95 per database up to 5GB per month**
• Business Edition
  • Maximum $225.78 per month a maximum database size, which is 150 GB, various prices can be check at Azure Calculator, SQL AZURE Pricing

  AppFabric

  • Access Control
    • $1.99 per 100,000 transactions
  • Service Bus
    • $3.99 per connection on a “pay-as-you-go” basis
    • Pack of 5 connections $9.95
    • Pack of 25 connections $49.75
    • Pack of 100 connections $199.00
    • Pack of 500 connections $995.00

  Data Transfers / Storage

  • North America and Europe regions
    • $0.10 per GB in
    • $0.15 per GB out
  • Asia Pacific Region
    • $0.30 per GB in
    • $0.45 per GB out

  Neudesic has built an Azure ROI Calculator, which provides an interactive tool to provide indicative pricing, which you check.

The post SQL AZURE pricing (PROS | CONS) – How costly is to have SQL Database on a Cloud? appeared first on SQL Server Training | Tutorials | How to's.

You may also get Error “The execution of scripts is disabled on this system”

As per the error message, the script is not trusted to be run on your system. This is because, my current security policy doesn’t allow to run any PowerShell Script, which is not Digitally signed.

FIX / Resolution

I have seen this issue in past where I get error “execution of scripts is disabled on this system”, to fix this, I modified security settings and asked PowerShell environment to run any PowerShell Script by setting ““ExecutionPolicy” as  Unrestricted, using the following command in PowerShell window “Set-ExecutionPolicy Unrestricted”

Note : Make sure, the command prompt / PowerShell window is opened with elevated privileges, I mean to say, run as Administrator Mode.

After that, when I ran my PowerShell script, that worked without any issues.

The post PowerShell script error – File not digitally signed : FIX appeared first on SQL Server Training | Tutorials | How to's.

This weekend, I was performing a SQL Server upgrade from SQL Server 2000 to SQL Server 2005, still pretty old but the customer application is not being tested on SQL Server 2008 / R2 so that the only version which is achievable.

There are multiple ways to upgrade SQL Server

1. Side by Side upgrade
2. In Place upgrade

SIDE by SIDE upgrade is always an better option for DBAs, this option will leave the current instance as it is and we install a new SQL Server instance as a named instance and perform a backup and restore method to transfer databases from old version to newer version of SQL Server. In this solution, no down time is required as both instances can in parallel.

In Place upgrade, in this option we upgrade binaries from existing installation to a newer version of SQL Server. This method requires downtime and may fail in betwwen.

In my case, I did a In place upgrade because of following two limitations.

• Limitation of Storage / resources -  The server which I am gonna upgrade is lower end and doesn’t’ have enough storage to run two copied of databases.
• Application Limitation – Application SME is not available to modify connection string from default instance to Named instance.

This is a development server upgrade and production environment will be upgrade once every application level functionality is being verified by business on the DEV environment.

Step by Step Guide to Upgrade SQL Server In place Upgrade from SQL Server 2000 to SQL Server 2005 Enterprise Edition.

PRE Upgrade TASK

Prior to actual upgrade, please ensure that your database / database objects / application are compatible for newer version of SQL Server. Every version of SQL Server add some new features and deprecate some old / legacy  features. So prior to upgrade, please check and confirm that  you are not using any feature of SQL Server / TSQL Code which is deprecate in newer version of SQL Server.

Upgrade Advisor checks for any potential compatibility issues, deprecated functionalities, and feature and behavior changes, and provides you with a recommended list of tasks that need to be done before and after the upgrade.

This is tuff task, thus Microsoft has come up with a solution named “Upgrade Advisor” , which check and verifies each and every piece of your database / database objects will work in next version f SQL Server. If there is any deprecate feature, which you are currently using, SQL Server Upgrade Advisor will produce a report for the same.

If any feature / Code is being reported by Upgrade Advisor as warning / Error / deprecate feature, please work with developer to take special consideration.

To run Upgrade Advisor for SQL Server, you must have this application installed on your system. If you don’t have this Upgrade Advisor Installed, No worries, this is a free application from Microsoft. you can find Upgrade Advisor at Microsoft Site or it’s also available in SQL Server installation media / DVD.

Install Upgrade Advisor. Start the Upgrade Advisor from SQL server installation media

Enter Registration information and finally select upgrade advisor to install.

Once the Upgrade Advisor is installed, run that for all user databases and system databases and check the report.

This may take hours to run depending on size of the database. In my case this took approx 2 1/2 hours to complete.

Then verify that you are ready to upgrade and all your database objects will work on newer version of SQL Server.

SQL Server Upgrade Actually

Prior to start SQL Server Installation / upgrade. Please verify that you have met all pre requisite for SQL Server 2005 installation like Windows Installer Services. In case of SQL Server 2008, .Net framework is also required.

Ensure that you have Windows Installer Services Installed on your Windows System. If you don’t have Windows Installed, then you can install Windows Installer 4.5  from Microsoft. In my case I need to install This on Windows 32 bit so I downloaded and installed WindowsServer2003-KB942288-v4-x86.exe

Once this is being Done, Restart system and begin with Windows 2005 Setup installer by double clicking SETUP.EXE in installation media file.

Enter the product key and License aggreement

Select the component which you want to install

Click on Installed Instances and select the instance which you want to upgrade

Once the Instance in identified, which you want to upgrade, the setup will show you current version and once you click on Details, it will show you available options during this setup session.

Select the mode for authentication mechanism. This credentials will be used by SQL Server connection to old instance, which we are upgrading.

OPEN SQL Server Management studio and verify SQL Server version

Prior to send this good news to business, please validate SQL Server installation log files to verify there is no issue with any component of sql server. Please check my previous article to check installation logs (BOOTSTRAP files).

Now apply Updated Service pack to keep software upto date. so now in my case, I need to install and apply SQL service pack 4, which is latest available for this version of SQL Server 2005.

The post How to upgrade SQL Server? Step by Step Guide – Screen Shots appeared first on SQL Server Training | Tutorials | How to's.

This Error was received by one of the developer on his Development Server. The first impression was, Developer has must have written a extremely complex Long queries to meet complex Business requirement.

But Actually he was just running a simple SELECT statement, like this

SELECT Column 1 , Column 2 ,Column  3 from Table 1 where  Column 1 in (Select DISTINCT Column1 from Table 2 where COLUMN2 = @userVAR)

It’s hard to digest that this is a complex Query and we were able to reproduce this issue by running this again and again.

Just for information, The tables used in above illustration has huge data. Table 1 has approx. .9 million records and Table has approx .14 million records

My objective was to get away from this Message and User should able to get the results because I was running out of time.

SOLUTION / FIX :

I suggested developer to Join the tables instead of using the IN clause, which immediately FIXED this issue.

A day after, I was spending time to analyze why this SQL server treated that simple Query as extremely COMPLEX QUERY and retuned an Error Message. I started running this query on server by changing where clause condition and I was surprised with result.

I was able to get this error again when attempting to select records through a sub query query with a large number of entries in the “IN” clause. The moment I sub query started returning less records there was no Error/ Warning message.

Recommendation :  If you have left out with no other option and have to use IN CLAUSE only with large table then

1. Simplify your query
2. may divide query into multiple sub query (DIVIDE and RULE)
3. modify the Query plan bu supplying HINTS.

LESSON LEARNED :

In case you are using a sub query to extract the records from other table. THE IN clause should have less than  10,000 records (< 10,000), if its returning more than that you might get I was getting error “ran out of internal resources and could not produce a query plan“. Later on I found the same thing in Microsoft Documentation about this IN clause limitation.

This once again confirmed that Joining table is better option that using a IN CLAUSE.

The post The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information Error 8623 / 8632 appeared first on SQL Server Training | Tutorials | How to's.

Restore a backup from TDP library is pretty easy but you just need to be familiarized with tool to interact with Data Protection for Microsoft SQL Server.

To Restore a USER Database from a Tivoli, SQL Server Data Protection, you need to

OPEN GUI tool named Data Protection for Microsoft SQL Server; Start Menu\Programs\Tivoli Storage Manager\Data Protection for Microsoft SQL Server

1. Click on the ‘Restore Databases’ tab.
2. Select the ‘Show Active and Inactive’ and ‘Wait for Tape Mounts for File Information’ checkboxes.
3. Selecting the ‘Show Active and Inactive’ option returns information on all backups within the retention period (not selecting this option will display only the most recent backup)
4. The ‘Wait for Tape Mounts for File Information’ is required if replacing an existing database
5. Expand the SQL Servers group.
6. Expand the server name to display a list of all databases.
7. Highlight the database being restored. The list of candidate backups is displayed in the right window.
8. Select the backup from which you need to restore by clicking the checkbox
9. Ensure the database being restored is selected and the correct backup selected.
10. Right Click on the Selected Backup and select Restore INTO
11. Enter the name of the database being restored to and Click OK.
12. Again Right Click on the selected backup and select Relocate to relocating your database files to a new location and Click OK
13. Click the Restore button, which will start the Restore Operation and you can Monitor the progress window to confirm completion of the restore; respond to error messages accordingly.

This will successfully restore your selected database from Achieve with a New Database name.

The post Tivoli Data Protection SQL Server – Restore Database with different name appeared first on SQL Server Training | Tutorials | How to's.