We are developing an application with Visual Studio 2008 and TFS. Our database is a MySQL DB. As we develop we keep the new queries that need to be applied to the database of our new release as the New Version Update Queries. Right now I'm keeping them in a simple text file (which is a painful task!). I know that TFS integrates with MSSQL and makes this job very easy. I've already asked our consultant from Microsoft if there is any way to integrate TFS and MySQL, and his answer was "NO". So I was wondering if anyone knows any smart way of handling this issue?
I think the question may be a little misleading in that I think you're saying TFS when you mean Visual Studio. My guess is that you are looking for a MySQL provider to hook into VS2008 so you can use the database developer features (DataDude) with it? TFS itself is simply a server that provides source control and work item tracking services and isn't designed to work with anything other than MSSQL.
Visual Studio's data tools can be hooked into other databases using the Database Schema Provider interfaces (it's a 2010 feature). An implementation exists for Oracle, but nothing yet exists for MySQL.
My suggestion would be to store your scripts in TFS as regular source controlled items, and keep doing what you are doing until someone writes a DSP for MySQL.
Related
Were still using Reporting Services for SQL2008 (not SP2). I recently started using report builder 2.0, but it looks like report builder isn't able to modify data models - and VS2010 lacks business intelligence features. My question is: Have data models been depreciated? If not, what is the current tool for managing them? I have new reports to write so I'm trying to think ahead. Can datasets be used, and access controled, for ad-hoc reporting?
There isn't a way to modify the report models using vs2010 you would still have to have vs2008 BIDS installed to be able to modify these. It looks like reports models may be depreciated from SQL 2012 (http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0d0650d1-6d40-4d12-a471-54fb29b3356d).
If you starting a new project then personally I would look at using shared data sets based on views or stored procedures as these will be a lot easier to maintain and use. You can then use the permissions on these to control who has access to what.
I've had a big problem in replicating a simple SQL Server 2008 R2 Express database for use on a development server. I thought I had it sorted but it turns out that each table has lost it's 'Identity' value somewhere along the line, and it's not possible to add those back in now. This is pretty much useless. So I'm back at square 1; having to get a copy of a MSSQL database plus data from a web server to another web server.
I've read that SQL Server Publishing Wizard does this, and maintains crucial things like identity settings etc. Trouble is, I'm working with SQL Server 2008 R2 Express and I can't actually seem to find a way to access that program anywhere - even though when I go to 'control panel > remove programs' it's in there. When I try to find it on my system (e.g. via start > find programs / files) it's nowhere.
Does anyone know how to access this program, and will it do what I need?
Thanks!
Sure thing, thanks Michael. So the solution was to connect to the database through VWD 2010 Express, which has the options required to do this. There are actually some really great third party tools which do database migrations from one system to another detailed here: http://erikej.blogspot.co.uk/2009/04/sql-compact-3rd-party-tools.html. The ones on this page are geared specifically at SQLCE migrations, but several of the tools also support other full SQL versions too.
this is a quick question:
I have this Database Project in a Web app solution with the real database. I want to update the database using SQL server managment studio, and then update the corresponding VS project.
This can be done?
I know that you can update the scripts in the project, but I'm not the SQL kind of guy, i rather do this changes using Mangment studio...
Thanks in advance
Update: Okay, the point is that I want to make changes (if I have to) on the database, using Sql Server Managment studio, and then update the scripts in the Visual Studio DataBase Project, instead of make my updates on those scripts, because I don't feel confortable writing SQL commands. Now what I do is to recreate everytime the Database Project (delete and then create again), this is what I want to avoid
Also, I have Visual Studio 2010 Professional.
It is very achievable in VS2010 Premium and I am currently doing what you describe with a Database Project and a Schema Comparison item.
Sigd is not correct in saying you can only compare Database/Project Compare, you can also compare Project / Database and Database / Database
You can achieve this using the Schema Compare feature, but this is only available with the Premium or Ultimate editions of Visual Studio, not the Professional edition.
In many cases this is possible using Red Gate SQL Compare Pro, although I should warn you that this is not a fully supported scenario just yet (I'm the product manager for this tool so I'd welcome your feedback if you go this route!).
Red Gate's SQL Source Control better fulfills your suggested way of working, although this won't help you just yet as we don't tie into VS Database Projects. Again, this is something we are considering for an upcoming release. You're welcome to try it and let us know what you think.
http://www.red-gate.com/products/SQL_Source_Control/index.htm
If only the Schema Compare tool did what it's name suggests.
Unfortunately it is a "Database/Project Compare". So my project which includes only a single schema, when compared with the database, generates loads of Create actions for all the other schema objects present in the database.
Nice idea, needs work.
Traditionally, our plucky team of developers have always migrated our own reports into production. This task is now being taken up by our support staff, who'll need detailed instructions to do so.
We have always deployed straight from VS2005, which can be made available to the new migrators. Is there a better way to migrate these reports without VS2005?
Also, we need to provide some backup and rollback instructions. Have to confess, SSRS reports are probably the only thing I haven't backed up prior to a migration ( I normally take the "hey, they're only reports!" view ). Does anyone know of a good resource which covers backup of reports prior to deployment of replacements?
Have a look at this, it will backup all your reports using a script. I've used for migrating reports between servers. If you open the script file that it generates, you'll get a good idea how to generate your won scripts that you run using the RS.exe utility built into SSRS.
http://www.sqldbatips.com/showarticle.asp?ID=62
I found this extremely old document which appears to say that many of the web client features are not availiable when running on express edition--scheduling, subscription, etc--as well as no access to the report builder. Is that information still current, and are there any other features which are unavailable?
Subscriptions and scheduling are indeed absent in both MSSQLEx2005 and MSSQLEx2008, but I have never found this to be much of a problem. The underlying platform has a scheduler and the web service will do all the rendering, so you can recreate the missing elements without too much trouble.
The report builder is also absent, and this is non-trivial to replicate. You could always install SQLEx locally and let them use BIDS. Or you could stop being cheap. It's pretty good for free.
I recommend you use SSRS2008 rather than 2005 because it no longer requires IIS, and there are several sexy new capabilities in the report engine. In particular it now supports flow-based rich text with inline fields for mail-merge type reports.
Compatibility is excellent but some applications reject a newer database engine version. If this is a problem, continue to use SQLExpr2005 for the database.
So, are you saying that A) SSRS 2005
requires IIS whereas 2008 does not,
and that B) SSRS2008 is backwards
compatible with a SQL2005 database?
(It sounds like you might be saying
that SSRS 2008 could be used with
somebody running 2005 DBs
Yes, I am indeed saying that
SSRS 2005 requires IIS whereas 2008 does not
SSRS 2008 is backwards compatible with a SQL2005 database
SSRS 2008 could be used with somebody running 2005 DBs, or even 2000 DBs.
You can use SSRS with any database server for which ADO.NET drivers are available, including Oracle and MySQL.
I've caught somewhere the idea about rich text in SSRS 2008.
As I see it will allow me to make such static text
"Some test with some text in bold and some italic text"
with a single text box which was impossible in RS 2005. (even don't know good way to make it there)
You wrote it doesn't require SQL Server 2008 to be installed.
What about IDE for reports development ?
Looking forward with big hopes for SSRS 2008,
thanks for attention in advance,
Alex