I usually use Microsoft Visual Studio 2010 for system development and I always use the built-in SQL Server Express in Visual Studio to create and manage a database.
Currently, I'm learning Microsoft SQL Server Management Studio 2008 to create and manage a database.
I got some questions here:
What is the differences of the database in built-in sql server in Visual Studio & SQL Server Management Studio? Such as features and limitations.
Will it be better to create and manage database in SQL Server Management Studio instead of the built-in visual studio database?
I encounter a problem which is unable to upload my built-in Visual Studio SQL database to the web server in the past. So is creating database in SQL Server Management Studio much ideal for uploading database file to web server?
Thanks in advance.
Te latest versions of SSMS say "powered by Visual Studio" so your question could be moot. I think using SSMS gets you slightly closer to the database server itself -- which if you are doing admin too may be a good thing.
Related
I have Visual Studio 2010 installed on my Windows 10 PC. My website is on a shared hosting environment and utilizes a SQL Server 2012 database.
The hosting provider doesn't have web interface to manage database so I connect from the Visual Studio 2010 itself for management purposes.
Right now I am able to connect to the database and run my website locally but when I attempt to open table definition, I get this error:
This server version is not supported. Only servers up to Microsoft SQL Server 2008 are supported
Before upgrading to Windows 10, I was able to edit/add tables from Visual Studio 2010 Server explorer but now limited to read purposes only. This Windows 10 and Visual Studio is completely fresh install with nothing kept or saved from earlier windows version. I don't remember if I installed any SQL Server 2012 tools in earlier windows for managing the database from Server Explorer in Visual Studio.
I have searched a lot and even tried installing SQL Server 2012 Express which failed. Now, I am downloading SQL Server 2012 Management Studio from the same link to see if that will work. It will download in an hour or so but I don't remember downloading it earlier so wanted to ask you what can be done.
All I want is the ability to add/modify tables of SQL Server 2012 database from Server Explorer in Visual Studio 2010. Please tell me how can that be done and which tools are required for this purpose.
With the announcement of VS2013 i need to be able to have the following:
-Main Development IDE: Visual Studio 2013
-Integration Services with SQL Server 2008 and SQL Server 2008/R2.
-Integration Services with SQL Server 2012.
Unfortunately i cant upgrade all my SQL Servers to the latest release so i have to maintain a diversified dev env in my laptop.
What i need to do in order to have all the above in one machine?
Probably this is the answer :(
Interoperability and Coexistence (Integration Services)
Also a post made yesterday specifically for SQL Server 2012/2014
SQL Server Data Tools – Business Intelligence downloads
Separate install for each SSIS version i need to develop for.
So it may be like:
Full Visual Studio 2013 for all development except SSIS
VS2012 Shell for SSIS SQL Server 2012
VS2008 Shell for SSIS SQL Server 2008 and 2008/R2
Are there any tools available to design and edit tables in a SQL Server CE 4.0 database?
I am using Visual Studio 2012, I can find the tables and its columns and properties etc. But seems I can't edit table's column properties.
Any standalone third party tools and or plugins any plugin in Visual Studio 2012/2012 for this?
Did you look at the SQL Server Compact Toolbox extension?
Add it to Visual Studio with the Tools\Extensions and Updates menu, then search the Online node.
SQL Server Compact 3.5 and 4.0 Toolbox add-in for Visual Studio. This
add-in adds several features to help your SQL Server Compact
development efforts: Scripting of tables and data, import from SQL
Server and CSV files
While writing this question I had a simple idea which fixed the issue. Maybe other people have the same problem or you would like to comment this so I'm posting it anyways.
tldr/simplified question:
How do i use MS SQL Server 2005 Reporting Services in Visual Studio 2010?
Solution:
Just copy the Visual Studio 2008 Reporting DLLs in your project and include them as references. I guess you have to own a licence for vss2008 when doing this but technically this solves the issue.
Original question:
How can i use MS SQL Server 2005 Reporting Services in Visual Studio
2010? The reason i ask this is the following: We migrated to
VSS 2010 as our IDE but are still using MS SQL Server 2005.
Now, i want to change a piece of code in a Project which makes use of
Reporting Services on said SQL Server.
After converting the Solution to a VSS2010 Solution I get BuildErrors
because it can't find the namespaces "ReportViewer" and "Reporting".
That's because the references to
Microsoft.ReportViewer.Common (9.0.0.0)
Micrsofot.ReportViewer.WinForms (9.0.0.0)
Are no longer resolvable. So i have to replace them with the
references to the same Assemblies in Version 10.0.0.0.
After doing that the Solution builds successfully, but when opening
the ReportViewer i get an SoapVersionMismatchException telling me that
for Remote-Processing i have to use Microsoft SQL Server 2008
Reporting Services or higher.
You need to add the old references to your project. You can find them on your 2005 reporting server.
These can be found on your reporting server in the GAC.
When starting up an isolated mode visual studio shell application, the only databases available in the Tools->Connect to Database are Access, SQL Compact, and SQL Server Database File.
Is there a way to configure the isolated shell to include other database types? In particular SQL Server and MySQL. Are there any licensing agreement issues related to including SQL Server support?
This probably was intentional. These connectivity options are in line with what are provided by the freely available Visual Studio Express Editions. In the real Visual Studio, you must have the Professional Edition or better to access standalone database servers. (In fact this limitation is one of the main reasons a lot of developers buy Visual Studio.)