I am getting an error frequently while converting access database to sql which is given below as
Conversion Error , There is nothing to process in ssma while converting from access to sql
If anyone has faced same problem
please share the answer
Thanks in advance.
i got the answer here it is..
According to the log, in your start menu you should have two shortcuts, one to 32-bit version, another to 64-bit. Or you can go to the folder where ssma is installed (again by looking at the shortcut), and see if there are two similar executables. Try both.
link-http://www.experts-exchange.com/Database/MS-SQL-Server/Q_28433397.html
After hours, I realized that the access file corrupts after a few tries. When i could, I took the original access file and made the complete convertion.
Related
I created.exe file and installed it on my machine.When I insert data I get an error "Failed to update database "Database.mdf" because database file is read-only". I am able to view the data but cannot insert the data. I am using local sql database and visual studio 2019. My connection string is:
Data Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\HovedDatabase.mdf;Integrated Security=True
I have read a lot of topics on the forum about this and so fare I have changed the settings to the db in the SSMS, so that it is not longer a permisson issue.
But it still gives the same error. One thing I havent tried, because of lack of skill, is deploying the data to the %programdata% directory. It looks like this advice is given regarding this issue. So anybody have a idea on how to do this in Visual Studio. I am pretty new to this so dont be afraid to give detailed instructions :) Thank you in advance :)
While trying to generate the diagram for a database (in SQL Server 2017), I am getting an error
Array out of Index
When I restart the application, it works fine for some time, and after few minutes, when I try to add a new table to the Diagram, it shows that same error again.
Is there any solution to avoid this problem?
This sounds like it's a bug with SSMS (v17.4 in my case).
Others have reported similar issues here: https://stackoverflow.com/a/44914581/4768230.
Alternatively, others have suggested making sure you have schema declared for all your tables can possibly help - https://stackoverflow.com/a/44660066/4768230 (I haven't tried this though).
Below is an alternative answer that applies to a very specific situation.
The above answer will most likely solve your problem. However if you run SSMS as a different user than you are logged into Windows as you may get this error.
The workarounds are to either
Use your normal Windows to connect to the SQL Server (which may not be allowed depending on your situation)
User Remote Desktop to connect to a machine with your SQL Account.
Tested with:
Windows 7 64bit
SSMS 17.7
This situation might be related to the computer not being enabled to use Kerberos Double-Hop active directory but this statement is complete conjecture.
I'm trying to use a functions on the SQL SSMS2014 and I get the error on the title.
I can create new tables and databases no problem if i do it with a new query, but afterwards i can't edit or use the design function without getting that error on any of the databases that i have.
Most of the similar errors i found were related to connection to the database, but none of the fixes on those worked for me.
My guess is that the error message you are getting is:
the backend version is not supported to design database diagrams or tables
Solution:
This is commonly reported as an error due to using the wrong version of SMSS. Use the version designed for your database version. You can use the command select ##version to check which version of sql server you are actually using. This version is reported in a way that is easier to interpret than than shown in the Help About in SMSS.
Using a newer version of SMSS than your database is generally error free, i.e. backward compatible.
I have look everywhere for this issue. And after six hours yesterday and an hour today I decided to break down and ask the good fellows of stack overflow.
I set up Oracle 10.2.0 (which was an uphill battle) and finally got sql loader working, which I need because TOAD takes 15+hours to load 400k records. So my question is not how to resolve this error, I know the error. I have read nearly 4 tutorials on fixing the error. I want to know, since my TOAD is connected to the database just fine, is there a way I can get all the info from TOAD to populate/verify that my TNSNAMES.ora and sqlnet.ora files are correctly configured? I copy and pasted the information but it won't work anyway.
Also, aside from those two files, are there any other issues that could be preventing this, as a bit of background, I had to reinstall oracle 10g because the admin tools were not in place for the sql loader. Since the sql loader runs, I figured the install is just fine. If you need more info from me comment and I will edit.
Thanks guys,
Instead of using a tns name you can try connecting using ezconnect:
sqlldr username/password#//localhost:1521/orcl
If this solves the issue the tns name used could not be resolved properly. As you say you had to reinstall oracle to get the admin tools I suspect you might be looking at the tnsnames.ora file from the wrong oracle home.
We are doing a feasibility on what we're going to propose as a solution to a client who wants to migrate to a .NET based solution. Part of the data resides in UniData. What is required can be achieve using the following tool:
http://www.welland.com/export.html
The above product ETLs data from UniData to SQL Server.
As a first step, we want to be sure that there are no hitches in getting the data through SSIS from UniData to SQL Server.
Since we don't have an environment to test this we have to check mostly on the net. But most of the discussions regarding UniDate and SSIS don't look like the problem got solved. The main problem seems to be that people aren't able to get hold of a proper ODBC driver. If the data is converted into XML, then it looks like it's working fine.
Has anyone done this and know that this can go through without any problems?
Cannot say I've done it, but Rocket Software has 2-user license versions of UniData available for download, so at least you would have a system to test on.
We are actually working on this process now -- Unidata to SQL through SSIS. We worked with Rocket Software to get the OLE DB working... ODBC was never fast enough and before there was not OLE DB... Now there is. You have to do some work on the UNIDATA side once the OLE DB is install but that is an answer for another day. So far we have no issues except the work to get it setup.