Consolidate SQL servers to single server

So processor is ruled out. That's good.
I suggest you look at the chapter we put in the SQL 2K HA
book which explains how memory works in depth. To access
8 GB of memory under 32-bit, you need to put /PAE in
boot.ini. There is no other way. With /3GB, you can get
up to 3 GB of usable memory (different space tho), and 1
GB is always reserved for the OS. Up to 16 GB, both can
technically play together, and some applications need it.
beyond 16 GB on 32-bit machines, you cannot combine /3GB
and /PAE.
So if you have 8 GB and use /PAE and /3GB, you have 7 GB
of usable memory, of which only 3 GB would be dynamic (so
one instance could potentially be set to dynamic). When
using PAE, it is best to set the AWE settings in SQL as
well as set max mem for the instance. You seem to know
what that is.
So you can run all three instances with separate memory
using /PAE only, and if you can, I'd recommend that
approach.
Thank you for your reply, though I am still a bit confused.
I understand that using /3GB and /PAE will give me 7GB of usable RAM.
However, you say "When using PAE, it is best to set the AWE settings
in SQL as well as set max mem for the instance. You seem to know what
that is.", and while this is what I have read elsewhere, I was under
the impression that AWE settings were not available on SQL 2000
Standard?
In the next paragraph you say "So you can run all three instances with
separate memory using /PAE only, and if you can, I'd recommend that
approach." I don't think I understand this sentence. Are you saying
I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
Basically, I think I'm just looking to see if I can make SQL Standard
address memory above 4GB. I know you can with Enterprise using AWE, I
just thought AWE was not usable on Standard.
Thanks,
Kevin
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...
> So processor is ruled out. That's good.
> I suggest you look at the chapter we put in the SQL 2K HA
> book which explains how memory works in depth. To access
> 8 GB of memory under 32-bit, you need to put /PAE in
> boot.ini. There is no other way. With /3GB, you can get
> up to 3 GB of usable memory (different space tho), and 1
> GB is always reserved for the OS. Up to 16 GB, both can
> technically play together, and some applications need it.
> beyond 16 GB on 32-bit machines, you cannot combine /3GB
> and /PAE.
> So if you have 8 GB and use /PAE and /3GB, you have 7 GB
> of usable memory, of which only 3 GB would be dynamic (so
> one instance could potentially be set to dynamic). When
> using PAE, it is best to set the AWE settings in SQL as
> well as set max mem for the instance. You seem to know
> what that is.
> So you can run all three instances with separate memory
> using /PAE only, and if you can, I'd recommend that
> approach.
|||PMJI, but I'm 99.9% sure that SQL Standard will only ever use 2GB RAM
maximum. Doesn't matter what OS you use or what switches you have set.
Mike Kruchten
"Kevin" <kjarrard@.gmail.com> wrote in message
news:4f5b3722.0407281043.471e0365@.posting.google.c om...
> Thank you for your reply, though I am still a bit confused.
> I understand that using /3GB and /PAE will give me 7GB of usable RAM.
> However, you say "When using PAE, it is best to set the AWE settings
> in SQL as well as set max mem for the instance. You seem to know what
> that is.", and while this is what I have read elsewhere, I was under
> the impression that AWE settings were not available on SQL 2000
> Standard?
> In the next paragraph you say "So you can run all three instances with
> separate memory using /PAE only, and if you can, I'd recommend that
> approach." I don't think I understand this sentence. Are you saying
> I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
> Basically, I think I'm just looking to see if I can make SQL Standard
> address memory above 4GB. I know you can with Enterprise using AWE, I
> just thought AWE was not usable on Standard.
> Thanks,
> Kevin
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...[vbcol=seagreen]

Consolidate SQL servers to single server

So processor is ruled out. That's good.
I suggest you look at the chapter we put in the SQL 2K HA
book which explains how memory works in depth. To access
8 GB of memory under 32-bit, you need to put /PAE in
boot.ini. There is no other way. With /3GB, you can get
up to 3 GB of usable memory (different space tho), and 1
GB is always reserved for the OS. Up to 16 GB, both can
technically play together, and some applications need it.
beyond 16 GB on 32-bit machines, you cannot combine /3GB
and /PAE.
So if you have 8 GB and use /PAE and /3GB, you have 7 GB
of usable memory, of which only 3 GB would be dynamic (so
one instance could potentially be set to dynamic). When
using PAE, it is best to set the AWE settings in SQL as
well as set max mem for the instance. You seem to know
what that is.
So you can run all three instances with separate memory
using /PAE only, and if you can, I'd recommend that
approach.Thank you for your reply, though I am still a bit confused.
I understand that using /3GB and /PAE will give me 7GB of usable RAM.
However, you say "When using PAE, it is best to set the AWE settings
in SQL as well as set max mem for the instance. You seem to know what
that is.", and while this is what I have read elsewhere, I was under
the impression that AWE settings were not available on SQL 2000
Standard?
In the next paragraph you say "So you can run all three instances with
separate memory using /PAE only, and if you can, I'd recommend that
approach." I don't think I understand this sentence. Are you saying
I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
Basically, I think I'm just looking to see if I can make SQL Standard
address memory above 4GB. I know you can with Enterprise using AWE, I
just thought AWE was not usable on Standard.
Thanks,
Kevin
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message news:<532201c47407$87fa0
8c0$a501280a@.phx.gbl>...
> So processor is ruled out. That's good.
> I suggest you look at the chapter we put in the SQL 2K HA
> book which explains how memory works in depth. To access
> 8 GB of memory under 32-bit, you need to put /PAE in
> boot.ini. There is no other way. With /3GB, you can get
> up to 3 GB of usable memory (different space tho), and 1
> GB is always reserved for the OS. Up to 16 GB, both can
> technically play together, and some applications need it.
> beyond 16 GB on 32-bit machines, you cannot combine /3GB
> and /PAE.
> So if you have 8 GB and use /PAE and /3GB, you have 7 GB
> of usable memory, of which only 3 GB would be dynamic (so
> one instance could potentially be set to dynamic). When
> using PAE, it is best to set the AWE settings in SQL as
> well as set max mem for the instance. You seem to know
> what that is.
> So you can run all three instances with separate memory
> using /PAE only, and if you can, I'd recommend that
> approach.|||PMJI, but I'm 99.9% sure that SQL Standard will only ever use 2GB RAM
maximum. Doesn't matter what OS you use or what switches you have set.
Mike Kruchten
"Kevin" <kjarrard@.gmail.com> wrote in message
news:4f5b3722.0407281043.471e0365@.posting.google.com...
> Thank you for your reply, though I am still a bit confused.
> I understand that using /3GB and /PAE will give me 7GB of usable RAM.
> However, you say "When using PAE, it is best to set the AWE settings
> in SQL as well as set max mem for the instance. You seem to know what
> that is.", and while this is what I have read elsewhere, I was under
> the impression that AWE settings were not available on SQL 2000
> Standard?
> In the next paragraph you say "So you can run all three instances with
> separate memory using /PAE only, and if you can, I'd recommend that
> approach." I don't think I understand this sentence. Are you saying
> I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
> Basically, I think I'm just looking to see if I can make SQL Standard
> address memory above 4GB. I know you can with Enterprise using AWE, I
> just thought AWE was not usable on Standard.
> Thanks,
> Kevin
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...[vbcol=seagreen]

Connectivity Book

Hi,

Can someone please guide for a book that speaks in depth about connectivity issues and bugs related to SQL server connection objects.

I am also looking for a good getting started(and in depth) guide/resourse for following components....

MDAC Architecture & Installation

SQL Server Profiler.................................................................................................. 5

SQL Server Security................................................................................................. 7

Indexes..................................................................................................................... 8

Network Libraries and Connectivity........................................................................... 9

Linked Servers........................................................................................................ 11

Microsoft JET Basics........................................................................................................ 1

Access and Jet.................................................................................................................. 2

JET Provider 3.51 vs. 4.0.................................................................................................. 2

Unrecognized Database Format with Data Control............................................................. 3

Access ODBC driver and ASP – Just say No!.................................................................. 3

JET Installation.................................................................................................................. 3

............................................................................................................................. 1

Cursors; Location and Type.............................................................................................. 2

Objectives................................................................................................................. 2

What is a cursor?...................................................................................................... 2

Simple ADO Code.................................................................................................... 3

Default Values........................................................................................................... 3

FireHose Cursor....................................................................................................... 4

CursorType Property Values..................................................................................... 4

Static Cursor............................................................................................................. 5

Keyset Cursor........................................................................................................... 5

Dynamic Cursor........................................................................................................ 6

Limitations of CursorType......................................................................................... 6

CursorLocation......................................................................................................... 7

Server Side Recordsets............................................................................................. 7

Client Side Recordsets.............................................................................................. 8

Questions to ask........................................................................................................ 9

Guidelines............................................................................................................... 10

Knowledge Base Articles........................................................................................ 10

Resources............................................................................................................... 10

COM Basics....................................................................................................................... 1

COM – A Binary Component Architecture........................................................................ 4

COM Defined....................................................................................................... 4

Summary of the limitations of traditional object oriented techniques......................... 4

How COM Works............................................................................................................ 5

Using COM Objects............................................................................................. 5

Objects and classes................................................................................................... 7

Objects and interfaces............................................................................................... 7

Interface – a Contract................................................................................................ 7

Interfaces.......................................................................................................................... 8

An Array of Function Pointers................................................................................... 8

Identifying an Interface............................................................................................... 8

Interface Types......................................................................................................... 8

IUnknown................................................................................................................. 9

The COM Activation Process.......................................................................................... 10

Activation Steps for in-process COM component................................................ 10

Activation Steps for local COM component......................................................... 11

Creating a COM Client................................................................................................... 12

Declaring your COM object Variables............................................................................. 13

Creating COM Objects................................................................................................... 13

Destroying COM Objects............................................................................................... 15

Ensuring the “correct” COM Object is Created................................................................ 15

Lab - Creating a COM Client in Visual Basic............................................................... 15

Creating an In-Process COM Component....................................................................... 17

Creating Properties.......................................................................................................... 18

Creating Methods............................................................................................................ 19

The Instancing Property for ActiveX DLL’s..................................................................... 20

MTSTransactionMode Property...................................................................................... 22

Creating a Local Server COM Component...................................................................... 24

Component Versioning in Visual Basic............................................................................. 25

Components in COM+.................................................................................................... 29

COM+ Surrogate.................................................................................................... 29

COM+ Object context............................................................................................ 29

Just In Time (JIT) activation............................................................................................. 29

JIT Activation and state................................................................................................... 31

Demonstration: JIT Deactivation.................................................................................. 31

Demonstration: JIT Activation...................................................................................... 32

Active X Dlls created in Visual Basic that are enlisted in MTS / COM+ Applications34

ADO Basics – COM Automation object model................................................................ 1

COM Automation object model........................................................................................ 2

ADO Basics...................................................................................................................... 3

ADO Objects................................................................................................................... 4

ADO – Command Object................................................................................................. 9

ADO –Recordset Object................................................................................................ 10

ADO Recordsets – ways of obtaining.............................................................................. 13

ADO Objects – Data Access Summary........................................................................... 15

ADO Collections –.......................................................................................................... 16

ADO – Updating & Locking........................................................................................... 22

ADO – Using Stored Procedures.................................................................................... 23

This is just a list of things i would like to learn!!

Thankyou

Jay

Book online and KB have good info. I am not aware of any book dedicated to sql connectivity issue yet.|||

Thanks Nan,

I am trying to go inside the working of couple of things like database connection process and connection object behaviour in distributed systems in general.

I do appriciate your reply.

Thankyou,

Jay