import Excel into SQL Server using SSIS - excel

I want to import the excel sheet data present in my local machines into SQL Server 2012 (installed in the server).
I have seen some examples using SSIS but the excel & Server installed in the same machine.
how to do import from different machines?
Please help

There is no requirement to have the data you wish to load on the same logical machine as the SQL Server installation. You just need SQL Server Management Studio (SSMS) installed on a machine which has file access to the Excel file you wish to import and which can connect to the target SQL Server instance.
You might want to re-write your question to ask a specific question or describe the actual problem you're having (or at least tell us what you've already tried) if you want more helpful answers.

Related

Microsoft.ACE.OLEDB.16.0 provider is not registered on the local machine

I am trying to import an Excel file (*.xlsx) into a SQL Server table using both SSIS and the "Import Data" feature inside SSMS.  However, in both instances, I am getting "The Microsoft.ACE.OLEDB.16.0 provider is not registered on the local machine (System.Data)."  
However, when I go into my Programs, I see "Microsoft Access Database Engine 2016 (English) 16.0.4519.1000" is installed, as well as "Microsoft Access Database Engine 2010 (English) 14.0.7015.1000" , or at least shows up in the Apps and Features.  What am I missing to allow me to work with *.xlsx files as as the datasource to import into SQL Server either through SSIS or SSMS? 
Please note, I understand Excel as a datasource is not ideal and there are better methods, but unfortunately, I am not in a position to make demands that they use other file formats.  The best I can do right now is ask for them to convert to *.xls format.  
One thing I need to note as well, I do not have the ability to install anything on my own due to company security policies. Everything must be done through their automated system.

cognos analytics and cognos insight

all,
I just try the latest cognos analytics 11 Trial version. It seems to connect to cloud directly, but when I try to connect to MySql database in remote linux (I go to Manage->Data servers->New, then fill in the server, port...) from windows 8.1. It always raise the followed errors:
XQE-JDB-0004 A problem occurred finding the driver class "com.mysql.jdbc.Driver".
It seems JDBC driver has not been installed or configured in the server
My Questions are:
For latest cognos analytics 11 trial version in cloud, where to configure the server or install JDBC driver? Or we need to install cognos express sever firstly?
For cognos analytics 11, besides cloud version, could we download the usual desktop version? when I click the access trial, it seems to directly connect to the cloud version. I could not find where to download the desktop version of cognos analytics
For another cognos software--cognos insight, trial version could only import CSV file, and does NOT support MySql database. Is it right?
Thanks in advance
JDBC drivers need to be added to the <Cognos root>/drivers folder (as of Cognos 11), so there would be no way for you to add the necessary driver to their cloud installation. I am assuming they have only chosen to support a subset of data sources for the cloud trial, but I am not aware of a list of which ones they are allowing/supporting.
I have not heard of an on-premises Cognos Analytics trial, at least one that you are able to get publicly. It is certainly possible that IBM's sales folks would make that happen if it was a potential sales driver for them, but that is conjecture only.
Cognos Insight is capable of several things, one of which is being able to analyze CSV data brought in locally. More specifically, Cognos Insight supports getting data from the following:
CSV files
Microsoft Excel spreadsheets
ODBC data sources
IBM Cognos BI Reports
IBM Cognos TM1 Cube Views
IBM Cognos TM1 Dimension Subsets
Reference: http://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page627.html
I had the same problem but with an Oracle database hence I'm not sure if it helps for MySql, but you could try to perform the following steps:
Install the database Drivers (32 & 64 Bit) on the Cognos Server.
Open the folder cognos_install/v5dataserver/ and rename the file databaseDriverLocations.properties.sample to databaseDriverLocations.properties.
Open this file using a text editor and update the databaseJNIPATH to point to your database drivers.
In my case I configured the following value:
databaseJNIPath=C:\Oracle\product\12.1.0\client_64\bin;C:\Oracle\product\12.1.0\client_32\bin;
See here as well: http://www-01.ibm.com/support/docview.wss?uid=swg21574953

LocalDB Export to Excel

I have collected a bunch of data using my locally developed website. Now I need to analyze the data, but it seems like I cannot locate the .mdf file for the LocalDB database my website uses.
Looking at the data connection, it says myusername\localdb#abunchofnonsense.mydomainname.Models.UserDBContext.dbo. And the the connection string is data source=(localdb)\v11.0; initial catalog=mydomain.models.userdbcontext; integrated security=true.
Also, I'm using ASP.NET MVC, Visual Studio 2013, and Entity Framework if it helps.
It's probably quite confusing what I'm trying to do here. I collected some data and need to run logistic regression with it. Now the question is how can I connect Excel to this LocalDB so I can export the data I have collected?
You can import your LocalDB tables and data directly into Excel by the option Get External Data > From Other Sources under the Data tab in Microsoft Excel (2013 to be precise) - as the following screenshot shows:
A bit late, but perhaps someone can use the answer as I found this thread when running into a similar problem:
The problem is, that the localdb uses a different provider than the "normal" SQL-Connection. You need to use the "SQL Server Native Client" (in your case version 11) to connect. The provider should be installed with the localdb - if not you can find it here
To use in Excel, just choose
"From Other Sources"
- "From Data Connection Wizard"
- "Other Advanced"
- Choose your provider
- Enter the rest of your connection details
(not tested, but I see no reason why it shouldn't work): For existing connections you can edit the connection string and add/change "Provider=SQLNCLI11.1" (of course considering your installed version)
Source: I had the same problem in Installshield where you have to change the provider manually, so I just tried in Excel.

How to migrate SQLYog server connections to another machine

I am changing my work computer, and need to move my sqlYog saved connections to the new machine. I do not remember the passwords, is there a way to move it?
Windows 7 machines.
There are 2 ways:
1) You will find sqlyog.ini in C:\Users\{user}\AppData\Roaming\SQLyog\sqlyog.ini on recent Windows. So just copy it to new machine.
2) You can export/import your connection details. Exporting enables you to transfer connection details to other machines that you can later import into SQLyog. You can export/import connection from the Tools->Export/Import Connection Details
Refer this.
Found in this webpage:
Locate in %appdata% a file called sqlyog.ini.
Move this file to the new machine, and fire up sql yog.
Go to Tools -> Export/Import Connection Details -> Export Connection Details and select all the connections that you wish to export. Choose the directory where the file will be saved, then pick Export.
Use the same procedure to Import the connections (only this time use the Import option).

import data from dynamic excel to sql server 2008 r2 using SSIS without script task

I have to import data from excel(number of columns will change every time)to sql server 2008.
I have done script task for dynamically pulling the data. but the server has ace oledb and jet oledb registry errors. So is there any other way to import data from dynamic excel using SSIS
without script task?
Depending on the version of Excel being used to generate the spreadsheets, you may be able to use the Open XML SDK 2.5 for Office libraries. You will still need a Script Task or Component (or a full-blown custom SSIS component), but you may be able to avoid the ACE and Jet engine errors.
Fixing the registry errors does seem like the easier approach, though.

Resources