Viewing 15 posts - 1 through 15 (of 22 total)
In SQL BOL look for AWE using this syntax:
"Using AWE Memory on Windows 2000"
There are other settings in SQL that need to be set and BOL has good coverage...
February 19, 2002 at 12:19 pm
Andy's absolutely right about having to assign memory once you enable AWE. But, keep this in mind, you're allocating, min/max memory limits.
Also, you can only take advantage of greater than...
February 11, 2002 at 5:23 pm
Bryan, all things being equal, memory is your most important sizing consideration. What kind of hardware are you buying and what's your environment? Is your app mission-critical where you can't...
February 11, 2002 at 10:54 am
A/S up to 8GB of RAM. You can run one instance (or more, but let's assume only one) of SQL2K on A/S and you can take advantage of most of...
February 10, 2002 at 11:28 am
There is a "per processor" licensing option for SQL2K that may be more cost effective. Check with the vendor and negotiate the hell out of the price. Just tell them...
February 8, 2002 at 11:08 am
Check out SQL2K BOL, use the Index tab to search for, Memory. Under Memory, select Architecture.
cabby2583
Always Learn!
February 7, 2002 at 9:31 pm
So, the short answer to the original question is: 8GB of memory with PAE, /3GB and AWE enabled, depending on the server type. Many servers will only use 4GB of...
February 7, 2002 at 7:58 pm
In a multi-instance environment, each instance yields memory resources only to the operating system, and not to other instances of SQL Server. So, consider switching to "fixed memory" size when...
January 28, 2002 at 10:33 pm
Just a quick note here on the Quorum disk. MSFT recommends a separate physical disk in production environments. If you're setting up a lab at home, you can just designate...
January 24, 2002 at 7:30 am
This first article has an excellent description of the Quorum Disk, it's a step-by-step guide to installing MSCS:
http://www.microsoft.com/windows2000/techinfo/planning/server/clustersteps.asp
Then, you'll need to read this second article on clustering SQL...
January 24, 2002 at 7:05 am
If you're using Win98, there's a bug. Check out the following KB article (Q273833), on Microsoft TechNet:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q273833
cabby2583
Always Learn!
January 23, 2002 at 10:32 pm
Was that the entire SELECT statement?
My understanding is that clauses, such as TOP, SET ROWCOUNT, etc...., can have different effects on how the SQL Server engine processes information, therefore affecting...
January 23, 2002 at 12:39 pm
You can also setup SNAPSHOT replication with Queued Updating.
Here's a link to relevant white papers on MSDN site:
cabby2583
Always Learn!
January 22, 2002 at 6:01 am
By the way, one at a time, check the Client Network Utility and Server Network Utility. This'll help you isolate which one may be causing the problems.
cabby2583
Always Learn!
January 21, 2002 at 4:20 pm
Check the Data Source Name (DSN). You may have multi-protocol selected and this can cause you problems. De-select multi-protocol and then try connecting. If this doesn't work, try deleting this...
January 21, 2002 at 4:17 pm
Viewing 15 posts - 1 through 15 (of 22 total)