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).
Related
I'm trying to get into Sage 50 (v20 2014) via ODBC in Excel 2016 64bit. I keep running into connection problems.
I've set up a 64bit DSN using the utility on the Sage disk and I get the following...
If I go through 'Data/From other sources/From Microsoft Query' I get the usual 'Choose data source' box and the Sage DSN is visible. If I click it and click ok MS Query launches and then crashes immediately and I get 'Microsoft Query has stopped working'.
Interestingly, if I go back to the 'Choose Data Source' box, I get the error 'One or more of the folders in the search path could not be accessed'.
The default path set in the DSN is to 'C:\ProgramData\Sage\Accounts\2014\Company.000\ACCDATA' - the actual Sage database that I'm trying to access is in a network folder - 'V:\SHARED\Sage\COMPANY.002\ACCDATA'. I've tried both paths in the DSN and get the same results.
If I go through 'Data/New Query/From Other Sources/From ODBC' and then choose the Sage DSN, I get a full list of the tables but when I click on one of them to generate a preview, I get the following error...
DataSource.Error:ODBC:ERROR[42S02] Table not found
Details:
DataSourceKind=Odbc
DataSourcePath=dsn=SageLine50v20
OdbcErrors=Table
Also, if I use 'From data Connection Wizard', Excel crashes as soon as I choose the Sage DSN.
I'm not using any kind of connection string so I don't think it's authenticating with a user - I'm wondering if that would make a difference and if so, what would the connection string be?
I've been through everything that comes up if I google the problem and I've set up logins correctly etc but it will not connect. I don't know if this might be a 32/64bit comparability issue, but I'm using the 64bit Sage driver from the disk so I assumed that it wouldn't be a problem.
I've also tried connecting with MS PowerBI but I get the same problems.
Sage 50 is temperamental in how it allow connections to their database, what I mean: When it don't change the port, it just reject connections in awkward ways or not connect at all.
I didn't find a solution. However I found this workaround: Open sage, login and close it then connect using the DSN sage created with the sysadmin account(It grants you full access).
When defining the data path, it is critical to include a final backslash e.g
C:\ProgramData\Sage\Accounts\2018\COMPANY.001\ACCDATA\
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.
I am on a Windows 7 machine and have configured a ODBC connection by name of 'MyExcelDb' to an excel file. I am able to programatically connect to 'MyExcelDb' using type-1 jdbc driver and everything is working fine.
I now want to use Oracle SQLDveloper to query the DSN 'MyExcelDb' but I am not able to make this connection as I do not find any option for ODBC Connection. I have tried using the 'advanced' option in Oracle section and tried putting custom jdbc URL as 'jdbc:odbc:excelDB' bugt to no avail.
I have tried adding entries in SQLDeveloper for third party drivers like:
- sourceforge.net/projects/xlsql/
- code.google.com/p/sqlsheet/
- hxtt.com/excel.html
Despite this but no new connection option would appear and I am still struggling to make connection between the two.
I have searched around and found that I could install Oracle and add a TNS for the excel and that way I may be able to connect using the Oracle TNS in SQLDeveloper. Installing Oracle database but would be like killing a mosquito using a canon.
I wonder if there is a simple solution to my problem.
Have you tried following Oracle's guidelines for connecting to Excel files? Did you set up a system DSN as described in step three of the Oracle guide. Importing files into the database is routine and simple but using SQL Developer in the manner you describe, without the client installed. Here is an example of reading an Excel file via PL/SQL.
My question is why use SQL Developer to manipulate a datastore in Excel when Excel is designed to manipulate the data?
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.
Here is the steps to my problem:
I have a MOLAP cube with MOLAP dimensions on the AS2008 server
I connect to it with Excel 2007 and save it in a local cube file (.cub)
I disconnect from network, then I try to open the offline cub file through excel. It is successful.
I copy the .cub file to another machine, start Excel, try to connect to the .cub and I got error.
Please help. Thank you so much.
Additional info, on the machine I failed to open the offline cube, I have also installed Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider.
Great job finding a solution! I don't think you should necessarily need to put the local cube in the same folder, or have the same localization settings. Another possibility: Was the local cube in use at the time you copied it? If so, the file can be affected. Try copying the local cube when it is not in use and see if it can be used elsewhere.
Regards,
Nathan Peterson
www.cubeslice.com
Ok, I found the solution. We must establish at least these 2 conventions between source and target machine when saving the cube:
Same drive letter and folder name, e.g.: C:\Cube\Test.cub.
Same Localization in the Control Panel Regional setting.