I have created a database in SQL Server 2014 but I don't see it in Visual Studio 2013. I've been trying to figure this out for days to no avail. How can I use the database I created in SSMS in VS 2013? or how can I export it to be used in VS 13?
If I try to open the database from SSMS data folder I get an error. "you don't have permission ..."
But if I copy the .mdf file somewhere else and try to open it I get this error:
db cannot be opened because it is version 782. This server supports version 706 and earlier. a downgrade path is not supported
Any help would really be very much appreciated.
Thanks
Do you have the most recent version of SQL Server Data Tools (https://msdn.microsoft.com/en-us/data/tools.aspx)? I believe it's been updated since initial release to support SQL 2014.
Thank you all. I will leave the db alone where it is. I have SSMS 2014 and vs 2013. I thankfully did the following
" Try changing Tools>Options>Data Connections>Database Tools>Data Connections>SQL Server Instance Name. The default for VS2013 is "(LocalDB)\v11.0". Changing to "(LocalDB)\MSSQLLocalDB", for example, seems to work - no more version 782 error."
As from the above link(answer) posted by user1723033 and VikciaR and all is working for now.
Thanks again for your help.
Related
I am having a problem with a SSIS project that downloads data from a MySQL database and insert it in a SQL Server 2014 Database.
So I have two versions of the same project, one for SQL Server 2016 and another one for SQL Server 2014. They have the same scripts and data flows, but for some reason, only the one made for SQL Server 2016 works. The issues resides in the ODBC Driver connector. I can preview data in both project, but for the SQL Server 2014 version, it simply won't load it. So I get 0 rows every time I run it. Sadly, I need the 2014 version for our SQL Server, since when I deploy the project with 2016 as target version, it fails.
This pretty much sum up the whole problem and I have try quite a few things. Including, changing the ODBC connector's version. It all seems it has something to do with Visual Studio, when the target version is change from 2016 to 2014. Still, I can't find a solution to this issue.
I am using a query to source data, but I also tried with the table name, but still didn't work. I am not using any function. I am running directly from Visual Studio in debug mode.
Has anyone gone through the same error? I can't find anything related.
Please, let me know if you need anything else to understand the issue.
Ok I had similar issue but it was in Source query where one of function was not behaving same between 2016 and 2014 version.
When you say 0 rows, does package failed or successful ?
Are you using a query to source data ? If yes, does it have any functions used ?
Are you running from BIDS or SQL Agent ? If Sql Agent, Check if agent job configured to run in same 32bit or 63 bit version ?
Is anybody else having an issue when they right click on an SP, and not seeing the option to execute the SP? Only option that I have is to script as execute. I am running SQL Server 2016 express.
Too long for comment!
I suggest that you back up the database now. Full and transaction.
Then check the Compatibility level. Change it back to your previous version of SQL server. Take another back up (to a new file!!).
Now did you upgrade the whole of SQL server or just SSMS? You could just install another earlier version of SSMS and leave the existing server in place and running, test to see if the functionality is all still there with the new (older) SSMS and the old (Ok most recently installed SQL Server).
Microsoft are doing monthly releases of SSMS so it is changing fast - which can mean bugs, but the server should be more stable, so the problem could just be a SSMS issue and your database could be fine.
New patch came out. It works wonderfully now. My issue was resolved. Thanks for the help...
Well, I have a database running on shared hosting and have successfully connected to it. However, i cannot see the database but when i run i.e.
SELECT * FROM Item
Item is a table in it, i get correct result.
Further more, when connected via Visual Studio 2010 with the same credentials, i see it.
Ive had this issue before and resolved it by applying the current Service Pack to SSMS
It looks like a bug in Microsoft SQL Server Management Studio. See https://connect.microsoft.com/SQLServer/feedback/details/387616/tables-node-does-not-show-all-schemas-in-ssmse-2008
I was trying to remove my recent connection list by deleting the mru.dat (in Application Data folder under windows xp) file as pointed out in numerous tutorial over the internet(I just googled it) but was unable to find it. How am I supposed to clear it? Please help.
See this blog post:
For SQL Server 2008:
C:\Documents and Settings\<user>\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\mru.dat
If you can not find mru.dat at above location look for mru.dat in following folder.
C:\Documents and Settings\[user]\Application Data\Microsoft\Microsoft SQL Server\100\Tools\ShellSEM\mru.dat
If you are using VISTA OS instead of XP OS. Replace C:\Documents and Settings\[user]\Application Data\Microsoft\ with
C:\Users\AppData\Roaming\Microsoft\ and it should work.
I was able to accomplish this using Tools -> Options -> Display X files in recently used list. Simply set it to 1 then back to 10. I had to fiddle with it and restart SSMS a few times. They might still be on the hard drive somewhere, but they don't show up in the MRU list.
I'm working in an Access 2007 database and need help migrating tables to SQL server. Is this possible to do having only purchased Access 2007 or do I need to download a separate program for SQL? When I try to create a new SQL database or open an existing one through Access, I'm getting a "CREATE DATABASE" or "CREATE TABLE" error and not sure what the issue is. Any advice would be greatly appreciated!
Take a look at the microsoft's SQL Server Migration Assistant 2005 for Access (v4.0) which supports access 97 - 2007
Yes, you need to install it. There is a free edition of SQL Server, called Sql server express. Database size limit is 4gb. If it suits you go for it. Also, i belive Access has migration tool built in.
Update: In Access 2007 - Database Tools -> Move Data -> Sql Server ( follow the wizard ).