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.).
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
The features of system is;
Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
Microsoft Analysis Services Client Tools 2007.0100.1600.022 ((SQL_PreRelease).080709-1414 )
Microsoft Data Access Components (MDAC) 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 8.0.6001.19475
Microsoft .NET Framework 2.0.50727.4241
Operating System 6.0.6002
on windows 2008 Server ;
i have connection on sql server. not locally.
there is no problem. by this way; but one or two days later it doesn't allow us to connect.
if i restart server (computer) it connects again.
how can i solve this problem
I have two sql server database at two different locations. Source is developer edition of sql server and destination is web edition of sql server. Can i create ssis package in developer edition, for data transfer from developer to web edition.
Yes*, you can create an SSIS package in the Developer Edition and it will transfer data between the developer edition database and the web edition just fine. It will be a straight data transfer between two SQL Server instances.
That pesky asterisk though, that might be make this a No answer. The Web edition is not licensed for Integration Services. There is the import/export wizard which builds an SSIS package but if you persist it and execute the package, then it will fail as the machine will report it does not have the right components installed. It's certainly nothing you can schedule. You might think that you can make an end-around and run the SSIS package from the development server but that will likely violate your license as the dev license is not supposed to communicate with production systems.
SQL Server 2012
SQL Server 2008R2
SQL Server 2008
Summary
There is no technical restriction preventing an SSIS package from pushing from a developer edition to an web edition but there is likely a legal restriction for doing so.
YMMV, IANAL, consult your licensing agent.
Have an option to choose either a windows SE or Web Edition to install, for my Web based application built on Asp.Net 3.5 Framework.
Question: Have noticed in some blogs they mentioned that, we cannot install SQL Server 2008 on a WebEdition. Is that true?
Mainly - it is not true, you can install STandard, Developer, Express, Enterprise (and may be Datacenter) editions of SQL Server # Web edition of Windows Server 2008
You need something unusual?
I am assuming you mean SQL Server 2008 R2, if so it can be installed on a web edition but you need a special version of SQL Server 2008 R2.
More information here:
http://msdn.microsoft.com/en-us/library/ms143506.aspx#Web64
I am looking for a best web host to host my application developed with the following technologies.
ASP.NET MVC1
SQL Server 2008 with FILESTREAM
support
I first tried to host on DiscountASP.net. After creating account, I realized that they do not support FILESTREAM in SQL Server 2008. I checked with Godaddy as well. They do not seem to support SQL Server 2008.
I appreciate if you can point me to some good web hosts for my requirements.
I know that this is an old question but I had the same question so here is an answer.
GoDaddy Pro can support FILESTREAM via a virtual dedicated server. They run a VM running Windows Server 2008. Then you install a SQL Server that supports FILESTREAM (2008R2, 2012, 2014).
So, I would further guess that any service that can provide you with a dedicated virtual machine can ultimately give you the FILESTREAM service that you need.
I have verified that the following hosted services do not support FILESTREAM:
Amazon AWS doesn't support FILESTREAM
Winhost doesn't support FILESTREAM
http://www.webhostingbus.com/enabling-filestream-option-on-the-sql-server-database/