A funny thing happened the other day. I was running 64-bit Dev edition on my 4Gb Vista 64-bit notebook. SQL Server was set to 1Gb RAM and I was running 10 scripts each continually inserting a new randomly generated person into a table. The goal was to generate 500 million rows. Meanwhile, I was checking email, doing some browsing, doing some ...

The following pages were recently modified. Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise X64 Edition Notification Contents: New and All Modifications How to reduce paging of buffer pool memory in the 64-bit version of SQL Server 2005 http://support.microsoft.com/kb/918483/en-US...(read more)

Got an email to inbox asking a resolution for : I can't find a remedy for this problem on Google either. Any help would be appreciated. When performing the data mining cube process - Error: Memory error: Allocation failure : Not enough storage is available to process this command. For the error text it looks like the system is unable to fine disk ...

Yet another AWE memory settings blog post here that I'm posting for the issues we have had recently. Before going into details review about 3GBPAE blurb here and also refer to this KBA274750 to enable more than 2GB memory within your SQL Server Enterprise edition instance. Coming to the problem on a server having 6GB RAM and having required ...

Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise Edition & SQL Server 2005 Standard Edition Notification Contents: New and Major Modifications FIX: Error message when you run a SQL Server 2005 Integration Services package that contains a Script Component transformation:”Insufficient memory to continue the execution of the ...

The system DMV sys.dm_os_schedulers is an useful DMV to find such as running tasks & active workers threads etc. This is required to monitor the system state is heavily loaded or not, in particular this view will help you identify if there is any CPU bottleneck in the SQL Server machine. SELECT ...

Is 64 bit means more memory? Yes, to be precise. Microsoft has been investing heavily on X64 bit and within couple of years there will be no more development on 32-bit applications, as per the recent road map. So within 32-bit application it is one of the reason that memory has been a constraint on scaling-up server capacity. Once you consider ...

As usual for every performance issue there are many considerations that need to be evaluated when determining how to investigate the root cause for slower performance of many SQL Server databases. I would suggest that an important consideration is whether to use a 64-bit platform or a 32-bit platform to get the best performance results, though ...

Integration with .NET framework CLR within SQL Server gives extra flexibility for the developers to use other programming languages such as C# or VB.net by creating functions, stored procedures, triggers, data types, and aggregates are among the kinds of business logic that programmers can write with these languages. But think about performance ...

You might have come across a situation to have a better understanding on what /3GB or /PAE switch means that are referred in documentations and forums you go on. I will try my best to give you the notes what I have understood so far in this regard. From the available documentation on Technet & MSDN it is pretty informative that : The /3GB ...