Long story short. Let us say I have 3 different database servers, one SQL Server 2008 Standard and 2 SQL Server 2008 Web edition.
Will the following hold true?
Can I backup and restore between 2008 standard and 2008 web edition without compatibility issues?
Can I mirror the 2008 standard to a 2008 web edition? The web edition would only subscribe.
I would test if I could, but won't buy licenses for the servers until I know it is possible.
Thanks!
Related
I need a best technique to boost the performance and availability for the web and database server. My problem is I only can afford two 2 dedicated servers total.
I like to take a full advantage of the two servers by installing the NBL to help the IIS to distribute the traffic. I believe I will have a problem with the MS SQL 2008 Standard edition with Failover option.
My question is:
Does the NBL cause conflicts with the SQL 2008 Standard with the Failover and doesn't my settings below causing any conflict with the database settings.
Server settings are:
Server 1 - SQL 2008 R2 Standard Edition with NBL installed, IIS, SQL Standard with Failover
Server 2 - SQL 2008 R2 Standard Edition with NBL installed, IIS, SQL Standard with Failover.
I believe I have to remove the NBL to work the server work property, this is a waste of resource. I understood that the SQL 2008 Standard do not support scale-out feature. Moving from standard to enterprise edition would be too expensive.
MS SQL Standard Failover option will not work on the MS Windows Server Standard version, only the enterprise and datacenter editions can support the failover.
Ref: http://technet.microsoft.com/en-us/library/cc770625%28v=ws.10%29.aspx
I am planing to built database driven website with DotNetNuke and SQL Server Express 2012 on my laptop and than host it on web server that has SQL Server 2008 Standard edition.
Is SQL Server 2008 compatible with database files created by Server 2012?
Because I can install and build website using SQL Server 2008 Express Edition and upload to hosting provider server.
Is SQL Server 2008 compatible with database files created by Server
2012?
NO.
SQL Server database files are never backwards compatible - if you create a database on SQL Server 2012 - there is no way, no hack, no trick, no method to get this to be able to be restored or attached on an earlier version (e.g. 2008 / 2008 R2) of SQL Server.
No and it doesn't make much sense if you think about it. If it was the other way around, "maybe" it could be done (I actually never tried) because 2012 would somehow be aware of 2008 structure, but 2008 engine isn't aware of 2012 DB structure.
I'm writing a .NET app that connects to a remote hosted SQL Server. Researching hosts for when I roll this app out to multiple customers, I find that SQL Server 2008 R2 Web Edition is cheaper (monthly on a hosted dedicated server) than the Workgroup Edition and much cheaper than the Standard edition. Everything says Web Edition is for "website support" and "internet facing" use.
I know I must use Windows Server Standard and not Windows Server Web Edition to support database services, but what about the SQL Server version?
Simply - can a large number of users of a .NET Windows Forms program use a direct connection string to connect to SQL Server 2008 R2 Web Edition on the hosted server without going through a web server / browser?
Yes, it supports remote data connections.
Yes.
From my understanding of Web Edition, it is basically a mid-liner between Express and Standard. It's obviously not free, but it doesn't have the restrictions that Express does yet gives a lot of features (PBM, more than 1 CPU utilization, etc.).
I am setting up my development machine and I am wondering if I should install SQL Server 2008 R2 (for Developers) or SQL Server 2008 (for Developers) on my machine.
All of the databases that I work with are on SQL Server 2008 (not the R2). So I am torn. Should install what I am currently using? or should I be a bit forward looking and use the R2 version?
Will the client tools from the R2 install connect ok to the non R2 servers?
I guess in general what I want to know is what are the differences between R2 and non-R2 from a developer's point of view? (I don't really care about back end stuff too much.)
As far as I'm concerned, in R2 more features previously available only in Enterprise edition are now available in Standard edition. Otherwise, no big difference.
For a non-Business Intelligence developer (just plain old OLTP stuff), there's really hardly any difference and any additional features in R2, unfortunately :-(
The only thing that might become interesting at some point is the Master Data Service stuff - can't totally wrap my head around it just yet, so for now : R2 is not a big release for database devs in my opinion. Works great and all - but all the new shinyness is in the BI space.
Well.. in my case I have instaled on my computer SQL server 2008 but I wasn´t able to run SQL server management Studio so I decided to move on SQL server 2008 r2 and it works for me, I was able to start successfully SQL server configuration Studio and to connect to Vs2107 that was my primary goal.
Is there any chance of installing Reporting Services 2008 against an instance of SQL Server 2000? The docs clearly state that only SQL Server 2005 or 2008 are supported, but I thought I should ask anyway, for ways to bypass this limitation.
I should mention that I am not talking about the data source for my reports (which is a remote data source that can be any type of sql server). I am interested in the databases where the report server stores its things.
No, the reportserver and reportservertempdb REQUIRE 2005 or 2008. You could source data for your reports from a 2000 instance, but your reporting services databases need to be 2005 or 2008.
see: http://msdn.microsoft.com/en-us/library/ms157285.aspx and read the section on Database Server Version Requirements
I have no idea if this would work, however reporting services also depends on the SQL Server Agent service (for subscriptions) as well as the relational databases, so both would need to be compatible. If you have Reporting Services 2008 then you (or your organisation) must own a SQL Server 2008 license of some sort, therefore I cannot see why you would ever want to do this since you can install the SQL 2008 database engine to support your report server (on the same server, otherwise you would need an additional license).
Bear in mind that as of April 2008 SQL Server 2000 is no longer in mainstream support from Microsoft, so you should avoid implementing new infrastructure or functionality using this version wherever possible. The configuration you describe above, even if you got it to work, would be unsupported by Microsoft and probably all ISVs and partners.