Quick question: is the 4GB limitation on EACH database or for the installed instance of SQL Server? As you know you can create more than one DB in an instance of SQL Server...
The 4GB limit is on each database.
Yes. It's per database, not total. If you want to be really clever you have store a lot more than 4GB by spreading it over multiple databases (or even multiple instances).
Note that size limit for each database has been raised to 10GB in SQL Server Express 2008 R2
According to SQL Server 2005 Express Edition Features:
Scalability and Performance
Supports one CPU, but can be installed on any server
1 gigabyte (GB) addressable RAM
4 GB maximum database size
Related
Currently, I have a window application with using SQL 2008 R2.
This application is used by 200 users at the same time.
The database's size is almost 20gb.
The db server uses 16gb RAM, 200gb HDD.
And server is slow now, the CPU is over 80%, RAM was configured 14gb limit.
Does anyone have a tool or best practice to find out why the server is slow down?
Thanks.
I have a backup query like this:
BACKUP DATABASE #temp_baza TO DISK = #temp_bak
BACKUP LOG #temp_baza TO DISK = #temp_log
It is run by sqlcmd like this:
sqlcmd -l 120 -S %SQL_SERVER% -i %KOPIA_KATALOG%backupPELNY.sql
-o %KOPIA_KATALOG%output_PELNY.txt -v NAZWA_BAZY="%NAZWA_BAZY%"
-v KOPIA="%PELNY_KOPIA%\"
In output_PELNY.txt I have this kind of results:
BACKUP DATABASE successfully processed 645127 pages in 2819.651 seconds (**1.787 MB/sec**).
or
BACKUP DATABASE successfully processed 26338 pages in 227.348 seconds (**0.905 MB/sec**).
Main DB is on one Disc, backup is on second disk.
When I use Explorer to copy files between these two disks, I get a transfer speed of approximately 100 MB/s.
QUESTION:
Why is the backup speed so slow - I mean less than 3MB/s?
REMARKS:
Windows 2012 Essential + SQL Server 2008 R2 EXPRESS
Intel XEON E3-1270 v3 + 16GB RAM
To solve your problem, please refer to the following links:
Options to Improve SQL Server Backup Performance
Is your SQL Server backup running slow? Here’s how you can speed it up
Super-Fast Backup and Restore Throughput for SQL Server
MS SQL Server backup optimization
How to Make SQL Server Backups Go Faster
Below are some sample queries for download
To solve the problem, I suggest that the following part of the query:
backup database DBNAME to disk='C:\1\DBNAME.bak' with buffercount=16 ,maxtransfersize=4194304
SQL Server 2008 R2 Express has the following limitations:
Constrained to a single CPU (this limitation was raised in 2012 to "The lesser of one socket or four cores", so multi-threading is possible)
1GB RAM
10GB database size (per database)
So your backup is likely to be CPU bound and/or memory bound.
(Of course, it raises the obvious question: Why are you using an express version on your server? and why not a later SQL Server version?)
Ref.: SQL Server 2008 R2 Express Database Size Limit Increased to 10GB:
What about CPU and memory limits? Are any other limits changed in SQL
Server 2008 R2 Express?
No, the database size limit is the only limit we updated in SQL Server 2008 R2 Express. SQL Server 2008 R2 Express is still limited
to 1 CPU and 1 GB of RAM.
Starting with the 2016 version the In-Memory-technique is also integrated in the MS SQL Server Express edition. In fact as the Express version is limited to 1 GB RAM I'm wondering whether the RAM for the In-Memory OLTP technique is used as part of the 1 GB RAM or whether it will not affect the 1 GB RAM.
The buffer pool and memory for In-Memory OLTP objects are separate limits, documented here:
Editions and supported features of SQL Server
I am planning to get SQL Server web edition licence from my server provider
https://msdn.microsoft.com/en-us/library/cc645993(v=sql.130).aspx
SQL web edition has 64 gb ram and 16 core limitation
I will run 3 websites on this server and server has 24 cores and 128 gb ram currently
So it is logical for me if I run 2 instances SQL Server and I can utilize all system resources?
However I have never used two instances of SQL Server before.
So how can I install multiple instances of SQL Server 2016 web edition and use them?
This is my static connection string currently
public static string srConnectionString = "server=localhost;database=myDB;uid=sa;pwd=myPW;";
I'd suggest to go with Standard edition. It might be more expensive (about $45K), but you can use all of your 24 cores and 128 gb ram by just one instance.
You do not have to have multi instances, just have everything in different databases. If you are concerned about security, then you can make databases invisible for another user.
In case you want an ability to restart services separately, then it is better to have 2-3 virtual boxes, but in this case you'd have to pay individually for each box.
I've noticed that SQL Server 2005 x64 does not seem to lock pages into memory the same way SQL Server 2000 did. In 2000 I could easily see from task manager that SQL had locked 8GB of ram with AWE. I'm fairly certain I've got 2005 setup in an equivalent way.
Is this a normal x64 difference or am I forgetting a crucial setup option?
SQL Server 2005 x64 certainly doesn't need, or use, AWE; AWE is only to allow it to use > 4GB on 32 bit systems.
You can use the old lock-pages-in-memory trick, but as this KB shows (http://support.microsoft.com/kb/918483): "Note For 64-bit editions of SQL Server 2005, only SQL Server 2005 Enterprise Edition can use the Lock pages in memory user right."
I've seen permissions problems crop up a lot too - if the account you're using for the SQL Server service doesn't have the right permissions, it can't lock pages in memory even if you're running Enterprise Edition. This blog entry by the PSS SQL Server Engineers is really helpful:
PSS Engineers: Do I have to assign the Lock Pages in Memory privilege for Local System?