I am having lots of problems install Umbraco on SQL Server 2008 are there know compatibility issues?
Also are there any good reasons not to use SQL Server CE 4?
What version of Umbraco? V5.x will only run on SQL 2008 out of the box. Umbraco 4.7 will definitely run just fine on SQL2008.
There is no reason you can't use SQLCE for development, but I wouldn't recommend it.
For production - the performance is just not good enough (though I suppose with a low traffic site it might work). With the much more powerful SQL Express also available for free, there is very little reason not to use it from the get-go, and it would alleviate the SQLCE->SQL Express upgrade headaches you may encounter down the road.
Related
I'm planning a new sistem which is going to use quite large datatables. I'm not sure about which database I ought to use: FireBird (v. 2.5) or SQL Server Express (v. 2008). Despite the limitations of the Express version of SQL, it seems to be more integrated with .NET. Otherwise, FB must to connect with .NET through an "not included" ODBC driver, and I dont' know if it would reduce performance. Anyway, FB seems to be more robust, reliable and not limited as a free version of SQLS. What should I know about this comparation?
As others said: for Firebird, you don't need to use an ODBC driver; there's a native .Net driver which is actively developed/maintained. See the main Firebird site
Additionally, there's a DDX module that lets you integrate Firebird into the Visual Studio (all editions except Express) GUI (database connections etc)
Firebird pros:
- no conscious built in limits/throttling. SQL Express apparently is limited to 1 GB and 1 physical processor Wikipedia but I'm sure there's tons of MS documentation
- scale out from local (embedded or listening on 127.0.0.1:3050) to separate Linux or Windows database server if your dbs get really big
- active support community, paid support available
- allows easy switchover to a Linux/Unix application/environment
Firebird cons:
- SQL Server is more mainstream with .Net (more examples, tighter integration)
- if you're not used to it you have to learn it. Applies to SQL Server as well, of course.
My opinion: if you're willing to learn, go with Firebird and make sure you properly tune the database, possibly with help from the Firebird mailing list (quite helpful).
If you want the easy (from an app dev point of view), mainstream .Net, possibly more expensive way, go with SQL Server Express and scale out to regular SQL Server.
Note: I do not have experience with large scale SQL Server or FB databases, just a happy Firebird user.
I have a project to work on. The project requires SQL server. I am using LINQ. So since I dont have SQL server installed on my computer, is it possible I can just use the LINQ designer to create my classes? And then when I do publish my website to a online hosting company, I can use the LINQ to create the tables and stuff?
Is this overly complicated? I want to stay away from using SQLite, or SQL Server Express or SQL server compact because its hard to transfer stuff. Atleast for me. My one problem is also that I want to use ASP.NET Membership stuff. If I run the .exe tool to automatically create my tables, how would I accomplish this without using a db? I tried using SQL server compact (mdf file i think?) but apparently the tool does not support it.
So what are my options here. I'd like to being programming right away however paying for hosting online is just a waste of money for me right now until i have some of the project done.
I'd suggest installing SQL Server Express Edition on your computer and using that as your database during development. I know that there can be some confusion and difficulty when upgrading your development database from SQL Server Express Edition to the professional edition on the hosting company's database servers, but I'm confident that the time you will need to spend on that will be dwarfed by the time you'd need to spend to build and use a mock database layer, not to mention the extra testing you'd need to do once you moved to a real database.
Also, the challenge in moving from SQL Server Express Edition to the professional edition at the hosting company shouldn't be too bad if you choose a web host that has tools for importing your SQL Server Express Edition database into their database server. (Some have it so you can just upload your SQL Server Express .mdf file and it will automatically import it into their database server.)
Two things you can do
Install Sql Server Express on your development machine (or a server on your LAN). This way you will have a local database to develop and test on.
Not necessary, but you "could" try to use Entity Framework in place of LINQ, and use Code First mapping.
Also with Sql Server Express, you can do a lot of your database work right from Visual Studio (providing you're running VS Pro).
I want to stay away from using SQLite, or SQL Server Express or SQL server compact because its hard to transfer stuff. Atleast for me.
Upgrading shouldn't be too difficult.
My one problem is also that I want to use ASP.NET Membership stuff. If I run the .exe tool to automatically create my tables, how would I accomplish this without using a db? I tried using SQL server compact (mdf file i think?) but apparently the tool does not support it.
aspnet_regsql.exe works on Sql Server Express
Use SQL Server Express. It is free. Easy to install in your development environment. In SQL Server Management Studio (SSMS), you can right-click on a table and generate scripts to create the table if you did this from the graphical designer. All you have to do is run the script on the new server. There are free tools that can create/transfer data as well.
What are you going to do down the road when you need to test changes? I hope you don't plan on using the production database.
Just generate your entities by hand, later you would be able to easily attach SQL Server to all this stuff.
Create classes and mark them with required attributes (I don't remember their exact name,check MSDN)
P.S I just can't believe SQL Server Express is not enough for you )
Not that it's a prerequisite for commenting here, but I'd like to pick the brain of someone that's taken their Reporting Services platform from 2000 to 2008 (skipping right over 2005).
The architecture between 2000 and 2005 (so thus between 2000 and 2008 also) changed significantly it seems, so I'd like to know what needs to be done (before,during,after) the process of taking my rs2000 install (installed on a web server running IIS 5, connecting to a remote sql server 2000 box that hosts the ReportServer/ReportServerTempDB databases) and converting it to SQL208 - where, from the looks of it, is hosted in some sort of it's own native hosting engine, no IIS needed (is that right?).
I've used this tool before, but only for moving stuff between 2 rs2000 databases. I'm curious if it works between 2000 and 2008. I've also been reading on TechNet and MSDN about some kind of "upgrade advisor" and "upgrade wizard" - but I remember what the VB6 to VB.NET Wizard was like, so I'm a little skeptical of a wizard that proclaims to help migrate stuff between 2 architecturally different versions of a product.
Disclaimer: I am not a Reporting Services (or SQL Server) admin. Just the guy on the team most familiar with installing/supporting the tool, so I'm stuck being responsible for this migration too - though I'm a veteran developer, not totally clueless.
Be aware, there is no anonymous mode in SRS 2008, you should use Active Directory / Kerberos / Windows authentication or use your own authentication module.
In SRS2008 you've got feature like Tablix/Matrix which are really usefull, maybe you can make some optimizations into your old reports.
[edit]
I should note that I need to do this on a live production server. The MS SQL Server is already attached to our website and supports a 3rd party ERP package. I want to set up a separate database that I can code against for some auxiliary pages and internal-use apps) which will be completely independent (mostly for security, but also because I prefer mySQL) from the ERP solution.
[end edit]
The MS SQL 2005 express db is already installed and in use, so I don't want to hose it.
Will this create problems, or have you done it successfully?
Aside from performance issues, assuming they're both continuously used, there shouldn't be a problem.
For a development machine this is safe to do. The two database servers listen on different ports, so there is no problem of running both at the same time.
I wouldn't recommend it though for a production system.
Like Assaf said, the only thing you should worry about are possible performance issues with both database services getting run at the same time. Other than that you should have no worries concerning the integrity of the two. They are completely separate and should not have any sort of conflicts.
We were running Tarantino in a Nant build script but we're getting some new hardware and using the opportunity to upgrade to SQL Server 2008. Unfortunately Tarantino won't work with SQL 2K8 so I'm looking for an alternative.
Any ideas?
Migrator.net is the tool I use with SQL 2008. It also has nant script capability. I suggest using the trunk version, rather than the 0.7 release as it's had some good, as yet unreleased changes.
This roundup has other options. And there are few other similar questions here.
There are quite a few really good tools - some require adoption of a database change management process (like DBGhost), while others are less restrictive, but require more work (and efforts) on your side, e.g. Red-Gate's SQL Packager, which allows you to package your database creation and change scripts into .NET projects and/or stand-alone EXE files.
I believe Tarantino has been fixed now to work with SQL2008 as of March 2009
http://code.google.com/p/tarantino/source/list
Try the latest version of Tarantino from SVN, it works with SQL Server 2008.
Unfortunately, they have an outdated release published in Downloads section.
You may want to have a look at RoundhousE as well.