We are developing an intranet web application for our organization via third party vendor and the vendor who is implementing this for us has provided SQL Server Express edition. As we know, SQL Server Express has a limitation of 10 gb only so we have asked the vendor to provide SQL Server Standard or other paid licensed db with no size limitation.
But the vendor is saying that they have implemented system in such a way that automatically new schema is created by system periodically such that 10 gb limitation will not impact system. As per vendor multiple schema are automatically used by application as required with no manual intervention. So according to vendor 10 gb limitation is not a problem.
But we are not satisfied with vendor reply.
Related
When a project is created in Asp.net MVC you have the possibility to choose between different types of database, which is the recommended and what are their differences and uses.
SQL Server runs as a service, whereas SQL Server Compact is an embedded database in the same physical location as the application. SQL Server Compact is meant for a standalone application and is not intended to be shared among many users or in situations where there is a lot of concurrent access, such as with a web site.
SQL Server runs as a service and listens for requests on a port. You can have multiple concurrent connections with its use and it acts as a gatekeeper checking for permissions from incoming connections. It is meant for work groups and enterprises, and is not intended (overkill) for single-user/single-computer applications.
SQL Server Express is the free edition of the full SQL Server, and has certain limitations such as a maximum database size of 10GB, among others. SQL Server Standard is like the full edition. There are also Enterprise, Datacenter, and Developer editions.
I have SQL Server 2012 Web Edition.
I want to configure High Availability on this Server.
Do I need to have another SQL Server to configure High availability?
How is SQL Server Native Client 11.0 is part of this?
I know this is a wide area question, but I am looking for a start on this.
Yes, for all high availability scenarios you need more than one server. As for high availability in the web edition, all you get is log shipping, so you will need to manually fail over to another server if your primary dies.
The native client is a combined ODBC driver and OLE DB Provider for SQL server. It doesn't in itself provide high availability, but it can be used, for example if you were using database mirroring, to provide the name of the mirror server for automatic failover.
I have been tasked to set up SharePoint 2010 on a Virtual Machine (Hyper V), and I have loads of resources at my disposal. I want to know what will the best practiced (or optimal) hardware and software specifications be to set up SharePoint 2010 on this Virtual Machine, it needs to at least support up to 400 people. I found some guides on the Microsoft website at http://technet.microsoft.com/en-us/library/cc262485.aspx . As far as I know, Microsoft sees Small Deployments as machines that are able to support 2500 people, which is way too much for me.
Can anyone please help?
EDIT
Server 1 – Web Frontend Server
• Windows 2008 R2 64-bit
• CPU: ?
• RAM: ?
• HDD Space: ?
• External IP? Yes/No
• Ports open: 80, 443, ???
Server 2 – Application Server
• Windows 2008 R2 64-bit
• CPU: ?
• RAM: ?
• HDD Space:
• External IP: Yes/No
• Ports Open: 80,443, ???
SQL Server
• Standard/Enterprise edition?
• New Instance?
• Service account for instance?
• Full-text search?
• Maintenance plans?
• Space requirements?
Sharepoint Setup
• Domain name: ???.XXXXXXXXX.XXX
• Email Server to use: ???
• Service Accounts: XXXXX\???
** ANOTHER EDIT **
I already have some of the data, like SQL Data. Ignore SQL
The Planning guide for server farms and environments for Microsoft SharePoint Server 2010 http://www.microsoft.com/download/en/details.aspx?id=21097 will give your more precise answers than I'll ever will but anyway :
For 400 users, depending on the actions that your users will do and the number / load of synchroneous operations, you could even go for a standalone farm (everything on a single server). If you have a separate SQL Server 2008 Server, that will be even better as all database operations will be handled by this additional server.
You'll want a 64 bits Windows 2008 R2 / SQL Server 2008, at least 8gb of ram (the more you can give, the better).
Microsoft recommand at least a four cores CPU but you can go with only 2 (but you don't seem to have issue with ressources) For your WFE / App server I would allocate 80 ~ 120gb of disk, for the SQL Server, it will depend on the content / database recovery model / versioning you'll have (and many other factors like the search database size if you plan on having search functionnalities).
At the end, it's all about the usage of your farm. You can have 400 users on which 80% will read data while only 20% will contribute or you can have 10 users that will inject gbs of data each day... It's hard to advice you without knowing the business requirements that you need to fullfill.
Also Checkout the capacity planning from MS : http://technet.microsoft.com/en-us/library/ff758645.aspx, http://technet.microsoft.com/en-us/library/ff758647.aspx as well as for SQL Server with SharePoint in mind : http://technet.microsoft.com/en-us/library/cc298801%28office.14%29.aspx
I am using Django on Windows 2003 Server SP2 and IIS 6 with pyisapi.
Do you recommend using sqlite3 on this production server?
What are the advantages and disadvantages of using sqlite3 on a production server in general and especially on Windows 2003 Server.
Our application is an order management tool which will have 5 clients accessing it (not necessarily concurrently). It is only used on an intranet. For this purpose we have adjusted the admin interface to our needs.
SQLite is an excellent product. It's very simple to use and deploy, is very fast, highly reliable and doesn't typically require any external administration. It uses very few operating system resources, allowing you do better utilize the operating system and hardware resources that are available. SQLite is used by many projects.
You may also want to look into Berkeley DB's SQL API. It's completely SQLite compatible. In addition, it offers concurrency (multiple readers and writers active in the database), scalability (BDB manages databases in the 100's of GB to TB range today) and HA (High Availability either for load balancing or for hot standby with automatic failover) above and beyond what's currently available with SQLite.
How many concurrent users on a Sql Server 2005 workgroup edition?
1 database?
Entire server?
There are no built-in limitations - from SQL Server 2005 Workgroup Edition:
Workgroup Edition is the data
management solution for small
organizations that need a database
with no limits on size or number of
users. Workgroup Edition can serve as
a front-end Web server or for
departmental or branch office
operations. It includes the core
database features of the SQL Server
product line and is easy to upgrade to
Standard or Enterprise Edition.
There are no limitations on the number of users. The limitations primarily are:
Doesn't run in 64bit mode (Uses Windows On Windows if
installed on a 64bit OS) - therefore it has a 3GB ram limit
Limited to 2 CPUs
That being said, I also found the lack of Integration Services running on the engine (you could do it as a file that runs with the Windows scheduler) somewhat of a pain.