Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts

Tuesday, March 27, 2012

A DOS question! (about aspnet_regsql.exe with paramaters)

I need to setup some asp security databases and I have seen several sets of instructions. Some say "Navigate to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727" and some say at the "asp command box". I do know that the directory & file exists on my machine. I have run aspnet_regsql.exe to configure my local server. I now need to run it to configure my web host SQL Server 2005 and that requires some paramaters like "aspnet_regsql.exe -S [DB Server Name] -U [DB login] -P [Password] -A all -d [Database name]". I am old and started before windows. I know DOS. But obviously not well enough.

How do you "Navigate to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727"?

If I say "CD\WINDOWS", it works.

When I am at the "C:\WINDOWS>" prompt and say "CD Microsoft.NET" it says "invalid directory"

When I am at the "C:\>" prompt and say "CD\WINDOWS\Microsoft.NET" it says "invalid directory"

When I am at the "C:\>" prompt and say "CD\WINDOWS\Micros~1" it says "invalid directory"

Thanks for your help. John Brown

Not much traffic on a DOS question! I figured out a work around.

I copied aspnet_regsql.exe to a directory with a short name (C:\trash) and then ran it from the command prompt. It worked!

John Brown

sql

Sunday, March 25, 2012

a connection error

Hi,
I have an error on my Application Server, it uses
analysis services and a SQL Server databases.
When I try to obtain information from the OLAP databases
it send me the next error:
Error Type:
ADODB.Connection(0x800A0E7A)
Provider cannot be found, It may not be properly
installed
Do you help me?
ThanksCheck to make sure you have MDAC installed properly on your app server

Monday, March 19, 2012

90 day trial

I want to convert my 90 day trial of SQL 2005 to the 2005 standard version,
is there an easy way to do this without having to resetup my databases which
a 3rd party setup for us
thanksHi,
From what I know, the trial versions of SQL Server cannot be changed to
Licensed intallations.
0. Turn off your applications that access the trial server.
1. Backup all your databases.
2. Detatch all the user databases (See your Books Online documentation to
see what the system databases are).
3. Uninstall the trial server.
4. Install licensed SQL and follow the instructions for disaster recovery
for the master database. This will recover your logins (with passwords and
SIDs) and linked servers, etc.
5. Attach the user databases you detached in step 2.
That is the basic outline. Use your Books Online documentation to fill in
the details.
--
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:A69038E1-62CB-420F-B7DA-293ABCB6B2A5@.microsoft.com...
>I want to convert my 90 day trial of SQL 2005 to the 2005 standard version,
> is there an easy way to do this without having to resetup my databases
> which
> a 3rd party setup for us
> thanks
>|||Hi Leonard,
Check out the following link.
http://technet.microsoft.com/en-us/library/ms143393.aspx
--
Ekrem Ã?nsoy
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:A69038E1-62CB-420F-B7DA-293ABCB6B2A5@.microsoft.com...
>I want to convert my 90 day trial of SQL 2005 to the 2005 standard version,
> is there an easy way to do this without having to resetup my databases
> which
> a 3rd party setup for us
> thanks
>|||HEY
So reading the document in the link it looks like it will upgrade to SQL
2005 std ok, have I read it right?
"Ekrem Ã?nsoy" wrote:
> Hi Leonard,
> Check out the following link.
> http://technet.microsoft.com/en-us/library/ms143393.aspx
> --
> Ekrem Ã?nsoy
>
>
> "Leonard" <Leonard@.discussions.microsoft.com> wrote in message
> news:A69038E1-62CB-420F-B7DA-293ABCB6B2A5@.microsoft.com...
> >I want to convert my 90 day trial of SQL 2005 to the 2005 standard version,
> > is there an easy way to do this without having to resetup my databases
> > which
> > a 3rd party setup for us
> >
> > thanks
> >
>|||Yep, you can go for it.
--
Ekrem Ã?nsoy
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:D0E6A03A-E719-4424-986A-8AE0043ECDCA@.microsoft.com...
> HEY
> So reading the document in the link it looks like it will upgrade to SQL
> 2005 std ok, have I read it right?
>
>
> "Ekrem Ã?nsoy" wrote:
>> Hi Leonard,
>> Check out the following link.
>> http://technet.microsoft.com/en-us/library/ms143393.aspx
>> --
>> Ekrem Ã?nsoy
>>
>>
>> "Leonard" <Leonard@.discussions.microsoft.com> wrote in message
>> news:A69038E1-62CB-420F-B7DA-293ABCB6B2A5@.microsoft.com...
>> >I want to convert my 90 day trial of SQL 2005 to the 2005 standard
>> >version,
>> > is there an easy way to do this without having to resetup my databases
>> > which
>> > a 3rd party setup for us
>> >
>> > thanks
>> >

90 Databases on cluster (Active/Passive)

hello, I am going to install SQL Server 2000 on Windows2003 server with
(Active/Passive) configuration
I have db space as 600 gig , ranges 1 gb to 90 gb. i have one concern about
how log failover to passive server will take in case of it need? whether it
depend on the db size or file group configuration of sql server? what about
the transactions in case of failover time? is there any way we have to
configure cluster for 100% transactions accuracy. i am using IIS6.0 as web
server for my online store.
Thanks for impromptu in advance.
John
Active-Passive is an obsolete term. You are building a single-instance,
two-node cluster. Under SQL Server 2000, all cluster nodes are treated
equally after initial installation. A single SQL instance can live on any
cluster node, but only on one node at a time.
Think of a cluster failover as a SQL Service stop-restart event. Everything
that happens during a server restart, happens during a failover. All
non-committed transactions are rolled back, committed transactions are
rolled forward. Transactional consistency is still guaranteed. Actual
recovery time is affected by the number of databases to recover and the
number/size of active transactions.
As for transactions log behavior during a failover, all SQL data and log
files must be stored on a cluster resource so they can be assigned to any
host node. The cluster service and the SQL cluster configuration guarantee
all resources go to a particular host node together so the SQL server can
run.
Geoff N. Hiten
Microsoft SQL Server MVP
"John" <John@.discussions.microsoft.com> wrote in message
news:598594BE-EAA6-4727-A56E-CF9DA9D8FB09@.microsoft.com...
> hello, I am going to install SQL Server 2000 on Windows2003 server with
> (Active/Passive) configuration
> I have db space as 600 gig , ranges 1 gb to 90 gb. i have one concern
> about
> how log failover to passive server will take in case of it need? whether
> it
> depend on the db size or file group configuration of sql server? what
> about
> the transactions in case of failover time? is there any way we have to
> configure cluster for 100% transactions accuracy. i am using IIS6.0 as web
> server for my online store.
> Thanks for impromptu in advance.
> John
>

Sunday, March 11, 2012

8.0 compatibility question

All,
I am upgrading an instance of SQL 2000 to SQL 2005.
Two of my applications have databases in this instance. According to their
vendors, these two applications are not compatible with SQL 2005.
However, these databases, although running in SQL Server 2005, are using 8.0
compatibility mode. I learned that databases stay in their original
compatibility mode when upgraded to 2005.
So my question is - if these databases remain in 8.0 compatibility mode
after an upgrade, doesn't that mean they will still work as if they were
running on SQL 2000 once I upgrade to 2005? And doesn't that mean they WON'T
break, which would save me the torture of porting them to a separate named
2000 instance and maintaining that instance?
Please, if anyone has any insight on this, let me know."Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:51F67FB1-BF4D-46F0-B6FB-31DEF7EEDF86@.microsoft.com...
> All,
> I am upgrading an instance of SQL 2000 to SQL 2005.
> Two of my applications have databases in this instance. According to
> their
> vendors, these two applications are not compatible with SQL 2005.
> However, these databases, although running in SQL Server 2005, are using
> 8.0
> compatibility mode. I learned that databases stay in their original
> compatibility mode when upgraded to 2005.
> So my question is - if these databases remain in 8.0 compatibility mode
> after an upgrade, doesn't that mean they will still work as if they were
> running on SQL 2000 once I upgrade to 2005? And doesn't that mean they
> WON'T
> break, which would save me the torture of porting them to a separate named
> 2000 instance and maintaining that instance?
>
8.0 Compatibility Mode is designed to minimize upgrade problems with SQL
2000 applications, running them in an environment as similar to SQL 2000 as
possible. However you still need to work with your application vendor to
make sure that they support your configuration.
David|||Unfortunately no. When you upgrade to 2005 the database structure is
changed. The 8.0 compatibility mode just turns off some of the new
features - it doesn't leave the database in SQL 2000 format.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:51F67FB1-BF4D-46F0-B6FB-31DEF7EEDF86@.microsoft.com...
> All,
> I am upgrading an instance of SQL 2000 to SQL 2005.
> Two of my applications have databases in this instance. According to
> their
> vendors, these two applications are not compatible with SQL 2005.
> However, these databases, although running in SQL Server 2005, are using
> 8.0
> compatibility mode. I learned that databases stay in their original
> compatibility mode when upgraded to 2005.
> So my question is - if these databases remain in 8.0 compatibility mode
> after an upgrade, doesn't that mean they will still work as if they were
> running on SQL 2000 once I upgrade to 2005? And doesn't that mean they
> WON'T
> break, which would save me the torture of porting them to a separate named
> 2000 instance and maintaining that instance?
> Please, if anyone has any insight on this, let me know.

8.0 compatibility question

All,
I am upgrading an instance of SQL 2000 to SQL 2005.
Two of my applications have databases in this instance. According to their
vendors, these two applications are not compatible with SQL 2005.
However, these databases, although running in SQL Server 2005, are using 8.0
compatibility mode. I learned that databases stay in their original
compatibility mode when upgraded to 2005.
So my question is - if these databases remain in 8.0 compatibility mode
after an upgrade, doesn't that mean they will still work as if they were
running on SQL 2000 once I upgrade to 2005? And doesn't that mean they WON'T
break, which would save me the torture of porting them to a separate named
2000 instance and maintaining that instance?
Please, if anyone has any insight on this, let me know.
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:51F67FB1-BF4D-46F0-B6FB-31DEF7EEDF86@.microsoft.com...
> All,
> I am upgrading an instance of SQL 2000 to SQL 2005.
> Two of my applications have databases in this instance. According to
> their
> vendors, these two applications are not compatible with SQL 2005.
> However, these databases, although running in SQL Server 2005, are using
> 8.0
> compatibility mode. I learned that databases stay in their original
> compatibility mode when upgraded to 2005.
> So my question is - if these databases remain in 8.0 compatibility mode
> after an upgrade, doesn't that mean they will still work as if they were
> running on SQL 2000 once I upgrade to 2005? And doesn't that mean they
> WON'T
> break, which would save me the torture of porting them to a separate named
> 2000 instance and maintaining that instance?
>
8.0 Compatibility Mode is designed to minimize upgrade problems with SQL
2000 applications, running them in an environment as similar to SQL 2000 as
possible. However you still need to work with your application vendor to
make sure that they support your configuration.
David
|||Unfortunately no. When you upgrade to 2005 the database structure is
changed. The 8.0 compatibility mode just turns off some of the new
features - it doesn't leave the database in SQL 2000 format.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:51F67FB1-BF4D-46F0-B6FB-31DEF7EEDF86@.microsoft.com...
> All,
> I am upgrading an instance of SQL 2000 to SQL 2005.
> Two of my applications have databases in this instance. According to
> their
> vendors, these two applications are not compatible with SQL 2005.
> However, these databases, although running in SQL Server 2005, are using
> 8.0
> compatibility mode. I learned that databases stay in their original
> compatibility mode when upgraded to 2005.
> So my question is - if these databases remain in 8.0 compatibility mode
> after an upgrade, doesn't that mean they will still work as if they were
> running on SQL 2000 once I upgrade to 2005? And doesn't that mean they
> WON'T
> break, which would save me the torture of porting them to a separate named
> 2000 instance and maintaining that instance?
> Please, if anyone has any insight on this, let me know.

8.0 compatibility question

All,
I am upgrading an instance of SQL 2000 to SQL 2005.
Two of my applications have databases in this instance. According to their
vendors, these two applications are not compatible with SQL 2005.
However, these databases, although running in SQL Server 2005, are using 8.0
compatibility mode. I learned that databases stay in their original
compatibility mode when upgraded to 2005.
So my question is - if these databases remain in 8.0 compatibility mode
after an upgrade, doesn't that mean they will still work as if they were
running on SQL 2000 once I upgrade to 2005? And doesn't that mean they WON'
T
break, which would save me the torture of porting them to a separate named
2000 instance and maintaining that instance?
Please, if anyone has any insight on this, let me know."Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:51F67FB1-BF4D-46F0-B6FB-31DEF7EEDF86@.microsoft.com...
> All,
> I am upgrading an instance of SQL 2000 to SQL 2005.
> Two of my applications have databases in this instance. According to
> their
> vendors, these two applications are not compatible with SQL 2005.
> However, these databases, although running in SQL Server 2005, are using
> 8.0
> compatibility mode. I learned that databases stay in their original
> compatibility mode when upgraded to 2005.
> So my question is - if these databases remain in 8.0 compatibility mode
> after an upgrade, doesn't that mean they will still work as if they were
> running on SQL 2000 once I upgrade to 2005? And doesn't that mean they
> WON'T
> break, which would save me the torture of porting them to a separate named
> 2000 instance and maintaining that instance?
>
8.0 Compatibility Mode is designed to minimize upgrade problems with SQL
2000 applications, running them in an environment as similar to SQL 2000 as
possible. However you still need to work with your application vendor to
make sure that they support your configuration.
David|||Unfortunately no. When you upgrade to 2005 the database structure is
changed. The 8.0 compatibility mode just turns off some of the new
features - it doesn't leave the database in SQL 2000 format.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:51F67FB1-BF4D-46F0-B6FB-31DEF7EEDF86@.microsoft.com...
> All,
> I am upgrading an instance of SQL 2000 to SQL 2005.
> Two of my applications have databases in this instance. According to
> their
> vendors, these two applications are not compatible with SQL 2005.
> However, these databases, although running in SQL Server 2005, are using
> 8.0
> compatibility mode. I learned that databases stay in their original
> compatibility mode when upgraded to 2005.
> So my question is - if these databases remain in 8.0 compatibility mode
> after an upgrade, doesn't that mean they will still work as if they were
> running on SQL 2000 once I upgrade to 2005? And doesn't that mean they
> WON'T
> break, which would save me the torture of porting them to a separate named
> 2000 instance and maintaining that instance?
> Please, if anyone has any insight on this, let me know.

8 GB database problems with cluster

Hello,

We have a microsoft cluster set up with several different databases, we have 5 different webservers that connect to the databases nad a very frequently visited site. a couple of days back we starrted experiencing a problem when posting data into one of the databases, the specific database is the biggest one we have, just below 8 gb of data ( all of the data is basically in 2 different tables).
we run w2k advanced serve service pack 4 , ms clustering , sqlserver sp3.
we started getting messages of timeouts from the webservers, so the timeout was because data couldnt be posted in the database.

after trying to figure out what the problem was , running dbcc checkdb etc i found no errors, but decided to restore a backup. , i did so and things worked perfect again. but only for a days time.. this of course made me consider database /table size being a problem, i now deleted the tables that contained the data and scripted new ones, that "solved" the problem of being able to post data , BUT, we need to have the other data in there as well. i am a bit at a loss now , an clues out there?

Friendly Regards

DavidTry a bit of a test. Run profiler on your new system with no data, and run some of the update statements that were timing out. Then, go to a test system (hopefully with all of the 8GB of data), and run the same profiler trace, and same updates on that database. If the durations of each update are wildly off, you may need to add an index in order to boost performance. This will take some experimenting on the test server.

If the durations are not very far off, then you may have a blocking problem. Look for big reports, or select statements that are grabbing large portions of these big tables. Good luck.

Thursday, March 8, 2012

7.0 to 2000 Upgrade

Is this a reasonable way to upgrade a 7.0 server to 2000?
1. Backup the databases.
2. Move the database mdf and ldf files to a neutral
location on the server's drive.
3. Upgrade the server to Win 2k and Sql Server 2000.
4. Add pertinent logins.
5. Reattach the mdf and ldf files and let sql server
upgrade the databases "on the fly".
The reason I'm asking is that I've always been ultra-safe
in times past and used the copy wizard to copy my 7.0
databases to a 2000 server first.
Is an attach/reattach considered a supported way of doing
a 7.0 to 2000 conversion?
I'm a little scared of course because if it doesn't attach
for some reason, then I can try the .BAK files and if that
doesn't work, I'm dead.It is hard to find documentation that provides it one way or another.
However, iny my experience of doing it Attach/reattaching works fine. Just
make sure you have a backup copy of your databases becauase you'll not be
able to reattach them to a SQL 7.0 server after attaching them to SQL 2000.
The only concerns I can think of have to do more with the sort order, which
would show up when people start to connect and use the system. SQL 2000
supports attaching databases with different sort orders, but some stored
procedures that create temp tables may have issues without having the
collation order specified for them. Only thorough testing will reveal a
problem like this.
My *safest method* is to use DTS to transfer the databases to another
server, then copy them back.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"CLM" <anonymous@.discussions.microsoft.com> wrote in message
news:121bf01c3f57c$ec04e740$a501280a@.phx
.gbl...
> Is this a reasonable way to upgrade a 7.0 server to 2000?
> 1. Backup the databases.
> 2. Move the database mdf and ldf files to a neutral
> location on the server's drive.
> 3. Upgrade the server to Win 2k and Sql Server 2000.
> 4. Add pertinent logins.
> 5. Reattach the mdf and ldf files and let sql server
> upgrade the databases "on the fly".
> The reason I'm asking is that I've always been ultra-safe
> in times past and used the copy wizard to copy my 7.0
> databases to a 2000 server first.
> Is an attach/reattach considered a supported way of doing
> a 7.0 to 2000 conversion?
> I'm a little scared of course because if it doesn't attach
> for some reason, then I can try the .BAK files and if that
> doesn't work, I'm dead.
>

7.0 to 2000 Upgrade

Is this a reasonable way to upgrade a 7.0 server to 2000?
1. Backup the databases.
2. Move the database mdf and ldf files to a neutral
location on the server's drive.
3. Upgrade the server to Win 2k and Sql Server 2000.
4. Add pertinent logins.
5. Reattach the mdf and ldf files and let sql server
upgrade the databases "on the fly".
The reason I'm asking is that I've always been ultra-safe
in times past and used the copy wizard to copy my 7.0
databases to a 2000 server first.
Is an attach/reattach considered a supported way of doing
a 7.0 to 2000 conversion?
I'm a little scared of course because if it doesn't attach
for some reason, then I can try the .BAK files and if that
doesn't work, I'm dead.It is hard to find documentation that provides it one way or another.
However, iny my experience of doing it Attach/reattaching works fine. Just
make sure you have a backup copy of your databases becauase you'll not be
able to reattach them to a SQL 7.0 server after attaching them to SQL 2000.
The only concerns I can think of have to do more with the sort order, which
would show up when people start to connect and use the system. SQL 2000
supports attaching databases with different sort orders, but some stored
procedures that create temp tables may have issues without having the
collation order specified for them. Only thorough testing will reveal a
problem like this.
My *safest method* is to use DTS to transfer the databases to another
server, then copy them back.
--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
*******************************************************************
"CLM" <anonymous@.discussions.microsoft.com> wrote in message
news:121bf01c3f57c$ec04e740$a501280a@.phx.gbl...
> Is this a reasonable way to upgrade a 7.0 server to 2000?
> 1. Backup the databases.
> 2. Move the database mdf and ldf files to a neutral
> location on the server's drive.
> 3. Upgrade the server to Win 2k and Sql Server 2000.
> 4. Add pertinent logins.
> 5. Reattach the mdf and ldf files and let sql server
> upgrade the databases "on the fly".
> The reason I'm asking is that I've always been ultra-safe
> in times past and used the copy wizard to copy my 7.0
> databases to a 2000 server first.
> Is an attach/reattach considered a supported way of doing
> a 7.0 to 2000 conversion?
> I'm a little scared of course because if it doesn't attach
> for some reason, then I can try the .BAK files and if that
> doesn't work, I'm dead.
>|||If you are going to upgrade Windows, I'd recommend
reinstalling everything from scratch. Our experience with
Windows upgrading in place is that it works successfully
30% of the time or less. And if it fails, it can fail
really hard (blue screen on a system that will never boot
again, i.e., total data loss).
SQL Server upgrades (without upgrading the OS) usually
work. One thing you *MUST* do, however, is install the
latest MDAC prior to beginning the SQL Server upgrade.
If you are worried about the integrity of the databases or
their backups, be sure to do a DBCC CHECKDB on all your
databases before you start this. Fix any problems before
taking your backups or detaching.
Also, keep records of all the logical *and* physical file
names (including the disk drive letters/file paths) for
*every* database file! You might need to know these to
get a restore or attach to work. This information can be
recorded from your existing installation only as long as
the databases are still attached, so get it first.
Regarding one of your questions: Both the attach and
restore SQL operations will automatically convert a SQL 7
database to SQL 2000.
P.S. It isn't really necessary to detach the databases to
copy them. You can copy the files safely as long as SQL
Server is stopped.
--Scott
>--Original Message--
>Is this a reasonable way to upgrade a 7.0 server to 2000?
>1. Backup the databases.
>2. Move the database mdf and ldf files to a neutral
>location on the server's drive.
>3. Upgrade the server to Win 2k and Sql Server 2000.
>4. Add pertinent logins.
>5. Reattach the mdf and ldf files and let sql server
>upgrade the databases "on the fly".
>The reason I'm asking is that I've always been ultra-safe
>in times past and used the copy wizard to copy my 7.0
>databases to a 2000 server first.
>Is an attach/reattach considered a supported way of doing
>a 7.0 to 2000 conversion?
>I'm a little scared of course because if it doesn't
attach
>for some reason, then I can try the .BAK files and if
that
>doesn't work, I'm dead.
>.
>

Saturday, February 25, 2012

64 bits version of SQL Server 2000

Did anyone use the 64 bit version in production with large databases?
Is it a better price/performance than the 32 bits version?
Any information if highly appreciated.
Thanks a lot!> Is it a better price/performance than the 32 bits version?
Sorry, there are far too many variables here for anyone to give a realistic
yes/no answer.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Let me be more specific:
- it is used for running some stored procedures and calculate bills based on
some algorithm.
- it needs to process over 500,000,000 records from about 5-10 tables.
- the data will be imported/DTSed from files into the tables
- there will not be more than 2-3 users accesing the data
- the output of the process will be 1-2 tables with the result of the
calculation. These two tables will have about 1,000,000 recods together (or
each of them?)
- we need to be able to run the process in less than 1-2 hours
Unfortunately I do not have more than that. The project did not start yet so
we do not know all the details.
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > Is it a better price/performance than the 32 bits version?
> Sorry, there are far too many variables here for anyone to give a
realistic
> yes/no answer.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>|||If your budget is good, you can buy the developer edition of 64 bit, $49 I
believe but you still need a 64 bit server (hence the budget comment). But
basically you would have to test 32 and 64 side by side. Not having seen
the "algorithm" though, this doesn't _seem_ to be somehting a 32 bit
multiprocessor box with good memory can't handle. Good table design, good
indexes, good statistics, and good queries go a LONG WAY.
hth
Eric
"Daniel P." <danutzp1@.hotmail.comU> wrote in message
news:ecWuIi0uDHA.3532@.TK2MSFTNGP11.phx.gbl...
> Let me be more specific:
> - it is used for running some stored procedures and calculate bills based
on
> some algorithm.
> - it needs to process over 500,000,000 records from about 5-10 tables.
> - the data will be imported/DTSed from files into the tables
> - there will not be more than 2-3 users accesing the data
> - the output of the process will be 1-2 tables with the result of the
> calculation. These two tables will have about 1,000,000 recods together
(or
> each of them?)
> - we need to be able to run the process in less than 1-2 hours
> Unfortunately I do not have more than that. The project did not start yet
so
> we do not know all the details.
>
> "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > > Is it a better price/performance than the 32 bits version?
> >
> > Sorry, there are far too many variables here for anyone to give a
> realistic
> > yes/no answer.
> >
> > --
> > Aaron Bertrand
> > SQL Server MVP
> > http://www.aspfaq.com/
> >
> >
>|||a load and then summary of 500M rows is not something I would characterize
as something a commodity 32-bit server would be able to do in 1-2 hours, but
it does boil down to requirements and design.
"Eric Sabine" <mopar41@.hyottmail.com> wrote in message
news:eKN4Gz0uDHA.1876@.TK2MSFTNGP09.phx.gbl...
> If your budget is good, you can buy the developer edition of 64 bit, $49 I
> believe but you still need a 64 bit server (hence the budget comment).
But
> basically you would have to test 32 and 64 side by side. Not having seen
> the "algorithm" though, this doesn't _seem_ to be somehting a 32 bit
> multiprocessor box with good memory can't handle. Good table design, good
> indexes, good statistics, and good queries go a LONG WAY.
> hth
> Eric
>
> "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> news:ecWuIi0uDHA.3532@.TK2MSFTNGP11.phx.gbl...
> > Let me be more specific:
> > - it is used for running some stored procedures and calculate bills
based
> on
> > some algorithm.
> > - it needs to process over 500,000,000 records from about 5-10 tables.
> > - the data will be imported/DTSed from files into the tables
> > - there will not be more than 2-3 users accesing the data
> > - the output of the process will be 1-2 tables with the result of the
> > calculation. These two tables will have about 1,000,000 recods together
> (or
> > each of them?)
> > - we need to be able to run the process in less than 1-2 hours
> >
> > Unfortunately I do not have more than that. The project did not start
yet
> so
> > we do not know all the details.
> >
> >
> > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > > > Is it a better price/performance than the 32 bits version?
> > >
> > > Sorry, there are far too many variables here for anyone to give a
> > realistic
> > > yes/no answer.
> > >
> > > --
> > > Aaron Bertrand
> > > SQL Server MVP
> > > http://www.aspfaq.com/
> > >
> > >
> >
> >
>|||Thanks everybody for help!
Unfortunately the project is in the inception phase. I only have some pieces
of requirements but no design and of course no code.
I'm pretty good at writing good SQL code and database tuning.
I need to send to my managers a proposal for hardware and software so they
can make the budget for the next year.
"joe chang" <anonymous@.discussions.microsoft.com> wrote in message
news:0b5001c3bb4b$eb1ec730$a501280a@.phx.gbl...
> in a equal # of CPU configuration, Itanium2 should give
> better performance in most applications
> I suspect that Xeon has better table scan performance, but
> have not been able to verify this in a clean test
> environment.
> Itanium2 will also have better performance in high-end
> systems (>4 CPUs)
> also, look at your SQL Server memory utilization, if a
> large chunk of the lower 2 (or 3) GB is being used for
> other than buffer cache, you may benefit from the 64-bit
> address space.
> otherwise, if the vast majority of your memory usage is
> buffer cache, then 32-bit with AWE works ok
> >--Original Message--
> >Did anyone use the 64 bit version in production with
> large databases?
> >
> >Is it a better price/performance than the 32 bits version?
> >
> >Any information if highly appreciated.
> >
> >Thanks a lot!
> >
> >
> >.
> >|||this is interesting
" I suspect that Xeon has better table scan performance"
why do you say that?
"joe chang" <anonymous@.discussions.microsoft.com> wrote in message
news:0b5001c3bb4b$eb1ec730$a501280a@.phx.gbl...
> in a equal # of CPU configuration, Itanium2 should give
> better performance in most applications
> I suspect that Xeon has better table scan performance, but
> have not been able to verify this in a clean test
> environment.
> Itanium2 will also have better performance in high-end
> systems (>4 CPUs)
> also, look at your SQL Server memory utilization, if a
> large chunk of the lower 2 (or 3) GB is being used for
> other than buffer cache, you may benefit from the 64-bit
> address space.
> otherwise, if the vast majority of your memory usage is
> buffer cache, then 32-bit with AWE works ok
> >--Original Message--
> >Did anyone use the 64 bit version in production with
> large databases?
> >
> >Is it a better price/performance than the 32 bits version?
> >
> >Any information if highly appreciated.
> >
> >Thanks a lot!
> >
> >
> >.
> >|||Hi
I believe it would violate the eula if you use the developer edition for a
production system. You should check with your supplier what edition is
needed for your system.
John
"Eric Sabine" <mopar41@.hyottmail.com> wrote in message
news:eKN4Gz0uDHA.1876@.TK2MSFTNGP09.phx.gbl...
> If your budget is good, you can buy the developer edition of 64 bit, $49 I
> believe but you still need a 64 bit server (hence the budget comment).
But
> basically you would have to test 32 and 64 side by side. Not having seen
> the "algorithm" though, this doesn't _seem_ to be somehting a 32 bit
> multiprocessor box with good memory can't handle. Good table design, good
> indexes, good statistics, and good queries go a LONG WAY.
> hth
> Eric
>
> "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> news:ecWuIi0uDHA.3532@.TK2MSFTNGP11.phx.gbl...
> > Let me be more specific:
> > - it is used for running some stored procedures and calculate bills
based
> on
> > some algorithm.
> > - it needs to process over 500,000,000 records from about 5-10 tables.
> > - the data will be imported/DTSed from files into the tables
> > - there will not be more than 2-3 users accesing the data
> > - the output of the process will be 1-2 tables with the result of the
> > calculation. These two tables will have about 1,000,000 recods together
> (or
> > each of them?)
> > - we need to be able to run the process in less than 1-2 hours
> >
> > Unfortunately I do not have more than that. The project did not start
yet
> so
> > we do not know all the details.
> >
> >
> > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > > > Is it a better price/performance than the 32 bits version?
> > >
> > > Sorry, there are far too many variables here for anyone to give a
> > realistic
> > > yes/no answer.
> > >
> > > --
> > > Aaron Bertrand
> > > SQL Server MVP
> > > http://www.aspfaq.com/
> > >
> > >
> >
> >
>|||A quick look on TPC shows that 32 bit systems are better than 64 bits. Sould
I rely on their numbers?
http://www.tpc.org/tpch/results/tpch_price_perf_results.asp?resulttype=noncluster&version=2%
"Daniel P." <danutzp1@.hotmail.comU> wrote in message
news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
> Did anyone use the 64 bit version in production with large databases?
> Is it a better price/performance than the 32 bits version?
> Any information if highly appreciated.
> Thanks a lot!
>|||I do not want to violate any laws so I need a fully licensed-for-production
system.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:fV2Ab.20511$F95.207029457@.news-text.cableinet.net...
> Hi
> I believe it would violate the eula if you use the developer edition for a
> production system. You should check with your supplier what edition is
> needed for your system.
> John
> "Eric Sabine" <mopar41@.hyottmail.com> wrote in message
> news:eKN4Gz0uDHA.1876@.TK2MSFTNGP09.phx.gbl...
> > If your budget is good, you can buy the developer edition of 64 bit, $49
I
> > believe but you still need a 64 bit server (hence the budget comment).
> But
> > basically you would have to test 32 and 64 side by side. Not having
seen
> > the "algorithm" though, this doesn't _seem_ to be somehting a 32 bit
> > multiprocessor box with good memory can't handle. Good table design,
good
> > indexes, good statistics, and good queries go a LONG WAY.
> >
> > hth
> > Eric
> >
> >
> > "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> > news:ecWuIi0uDHA.3532@.TK2MSFTNGP11.phx.gbl...
> > > Let me be more specific:
> > > - it is used for running some stored procedures and calculate bills
> based
> > on
> > > some algorithm.
> > > - it needs to process over 500,000,000 records from about 5-10 tables.
> > > - the data will be imported/DTSed from files into the tables
> > > - there will not be more than 2-3 users accesing the data
> > > - the output of the process will be 1-2 tables with the result of the
> > > calculation. These two tables will have about 1,000,000 recods
together
> > (or
> > > each of them?)
> > > - we need to be able to run the process in less than 1-2 hours
> > >
> > > Unfortunately I do not have more than that. The project did not start
> yet
> > so
> > > we do not know all the details.
> > >
> > >
> > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > > > > Is it a better price/performance than the 32 bits version?
> > > >
> > > > Sorry, there are far too many variables here for anyone to give a
> > > realistic
> > > > yes/no answer.
> > > >
> > > > --
> > > > Aaron Bertrand
> > > > SQL Server MVP
> > > > http://www.aspfaq.com/
> > > >
> > > >
> > >
> > >
> >
> >
>|||John, I think it's pretty clear I was telling him to test the 32 against the
64. There is no evaluation version of the 64 bit, you can only get it as
the developer's edition or the full retail.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:fV2Ab.20511$F95.207029457@.news-text.cableinet.net...
> Hi
> I believe it would violate the eula if you use the developer edition for a
> production system. You should check with your supplier what edition is
> needed for your system.
> John
> "Eric Sabine" <mopar41@.hyottmail.com> wrote in message
> news:eKN4Gz0uDHA.1876@.TK2MSFTNGP09.phx.gbl...
> > If your budget is good, you can buy the developer edition of 64 bit, $49
I
> > believe but you still need a 64 bit server (hence the budget comment).
> But
> > basically you would have to test 32 and 64 side by side. Not having
seen
> > the "algorithm" though, this doesn't _seem_ to be somehting a 32 bit
> > multiprocessor box with good memory can't handle. Good table design,
good
> > indexes, good statistics, and good queries go a LONG WAY.
> >
> > hth
> > Eric
> >
> >
> > "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> > news:ecWuIi0uDHA.3532@.TK2MSFTNGP11.phx.gbl...
> > > Let me be more specific:
> > > - it is used for running some stored procedures and calculate bills
> based
> > on
> > > some algorithm.
> > > - it needs to process over 500,000,000 records from about 5-10 tables.
> > > - the data will be imported/DTSed from files into the tables
> > > - there will not be more than 2-3 users accesing the data
> > > - the output of the process will be 1-2 tables with the result of the
> > > calculation. These two tables will have about 1,000,000 recods
together
> > (or
> > > each of them?)
> > > - we need to be able to run the process in less than 1-2 hours
> > >
> > > Unfortunately I do not have more than that. The project did not start
> yet
> > so
> > > we do not know all the details.
> > >
> > >
> > > "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> > > news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > > > > Is it a better price/performance than the 32 bits version?
> > > >
> > > > Sorry, there are far too many variables here for anyone to give a
> > > realistic
> > > > yes/no answer.
> > > >
> > > > --
> > > > Aaron Bertrand
> > > > SQL Server MVP
> > > > http://www.aspfaq.com/
> > > >
> > > >
> > >
> > >
> >
> >
>|||> A quick look on TPC shows that 32 bit systems are better than 64 bits.
Sould
> I rely on their numbers?
>
http://www.tpc.org/tpch/results/tpch_price_perf_results.asp?resulttype=noncluster&version=2%
Remember that the TPC benchmarks are for very specific applications running
on very specific hardware. Your mileage certainly will vary unless you are
building something similar and are spending the same kind of money on
hardware...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||> I believe it would violate the eula if you use the developer edition for a
> production system.
I think he meant to kick the tires and do some benchmarking, not to save
money in production.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||take a look at the execution plan for your query,
you do not need the full data size, but you should have
more the 100k rows
if the plan shows a hash join or hash match,
then i would highly recommend the 64-bit system,
the hash operator requires intermediate results to be
stored, a 32-bit system can only allocate so much address
space for the working set, after which the hash
performance will take a serious hit
64-bit systems should not be constrained on the ability to
use memory for intermediate results
>--Original Message--
>Let me be more specific:
>- it is used for running some stored procedures and
calculate bills based on
>some algorithm.
>- it needs to process over 500,000,000 records from about
5-10 tables.
>- the data will be imported/DTSed from files into the
tables
>- there will not be more than 2-3 users accesing the data
>- the output of the process will be 1-2 tables with the
result of the
>calculation. These two tables will have about 1,000,000
recods together (or
>each of them?)
>- we need to be able to run the process in less than 1-2
hours
>Unfortunately I do not have more than that. The project
did not start yet so
>we do not know all the details.
>
>"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in
message
>news:Oam%23yb0uDHA.2448@.TK2MSFTNGP12.phx.gbl...
>> > Is it a better price/performance than the 32 bits
version?
>> Sorry, there are far too many variables here for anyone
to give a
>realistic
>> yes/no answer.
>> --
>> Aaron Bertrand
>> SQL Server MVP
>> http://www.aspfaq.com/
>>
>
>.
>|||i know that there is atleast one operation that is much
slower on an Itanium2 system than on a Xeon MP, even
though overall the It2 was faster,
unfortunately, that was a production system, and i could
not get exclusive access to specifically pinpoint which
operation was performing very poorly relative to the Xeon
>--Original Message--
>this is interesting
>" I suspect that Xeon has better table scan performance"
>why do you say that?
>
>"joe chang" <anonymous@.discussions.microsoft.com> wrote
in message
>news:0b5001c3bb4b$eb1ec730$a501280a@.phx.gbl...
>> in a equal # of CPU configuration, Itanium2 should give
>> better performance in most applications
>> I suspect that Xeon has better table scan performance,
but
>> have not been able to verify this in a clean test
>> environment.
>> Itanium2 will also have better performance in high-end
>> systems (>4 CPUs)
>> also, look at your SQL Server memory utilization, if a
>> large chunk of the lower 2 (or 3) GB is being used for
>> other than buffer cache, you may benefit from the 64-bit
>> address space.
>> otherwise, if the vast majority of your memory usage is
>> buffer cache, then 32-bit with AWE works ok
>> >--Original Message--
>> >Did anyone use the 64 bit version in production with
>> large databases?
>> >
>> >Is it a better price/performance than the 32 bits
version?
>> >
>> >Any information if highly appreciated.
>> >
>> >Thanks a lot!
>> >
>> >
>> >.
>> >
>
>.
>|||I guess I will chime in. We are running a 4 way 64bit Unysis ES7000 with
16GB of memory on Windows 2003. We are currently using it for an OLAP
implementation, however the RDBMS is on the server is well. The best
benefit is memory, which we will be bumping up into the 30gigish range soon.
You can dynamically adjust memory over 8GB(do not really need AWE) without
rebooting SQL. When we are loading data into the cubes we can give SQL more
and when aggs are being built in the cube give more to OLAP Services.
Beyond that memory ease, we have not really noticed a great difference. In
alot of aspects it is a pain using SQL 64 bit, due to its lack tools and
bugs we have ran into. We have crashed our 64bit many times with the amount
of data we are trying to punch through(billion +). To give you some hard
numbers from our test using it in an OLTP environment, we traced some daily
activity and we ran the delete, insert, updates for the same anount of time
roughly --
32bit 4 way 8GB memory -- 133 Trans/sec
64bit 4 way 8GB memory -- 613 Trans/sec
32bit 8way 8GB memory -- 493 Trans/sec
"Daniel P." <danutzp1@.hotmail.comU> wrote in message
news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
> Did anyone use the 64 bit version in production with large databases?
> Is it a better price/performance than the 32 bits version?
> Any information if highly appreciated.
> Thanks a lot!
>|||i am not sure which numbers you were looking at,
the best 4P tpc-c for w2k3 + s2k:
it2 1.5G 121k
xeon mp 2.8G 90k
opteron 82k
at >4p, it gets better for It2 relative to Xeon
also, the tpc-c app uses almost all memory for buffer
cache, which works ok for AWE memory
but you will notice that 32-bit SQL Server has a tough
time in tpc-h, which probably better reflect your app
>--Original Message--
>A quick look on TPC shows that 32 bit systems are better
than 64 bits. Sould
>I rely on their numbers?
>http://www.tpc.org/tpch/results/tpch_price_perf_results.as
p?resulttype=noncluster&version=2%
>
>"Daniel P." <danutzp1@.hotmail.comU> wrote in message
>news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
>> Did anyone use the 64 bit version in production with
large databases?
>> Is it a better price/performance than the 32 bits
version?
>> Any information if highly appreciated.
>> Thanks a lot!
>>
>
>.
>|||Finally the kind of answer I was expecting: someone who uses 64 bit every
day.
Thank you very much Kevin!!!
I think I will stick with 32 bit and a lot of memory. I've also notices that
the amount of memory makes a big difference.
BTW: some MS guys came to us about two weeks ago and they said that the OS
(Windows 2000 or Windows 2003) eats up by default 1/2 of the physical
memory. So even if you have 16 GB you only have 8 GB available for the apps
like SQL Server. The rest is reserved for the OS.
This is really strange!!!
They also said this will be changed in Longhorn.
"Kevin Brooks" <jeepnreb@.yahoo.com> wrote in message
news:uISfnT2uDHA.1340@.TK2MSFTNGP09.phx.gbl...
> I guess I will chime in. We are running a 4 way 64bit Unysis ES7000 with
> 16GB of memory on Windows 2003. We are currently using it for an OLAP
> implementation, however the RDBMS is on the server is well. The best
> benefit is memory, which we will be bumping up into the 30gigish range
soon.
> You can dynamically adjust memory over 8GB(do not really need AWE) without
> rebooting SQL. When we are loading data into the cubes we can give SQL
more
> and when aggs are being built in the cube give more to OLAP Services.
> Beyond that memory ease, we have not really noticed a great difference.
In
> alot of aspects it is a pain using SQL 64 bit, due to its lack tools and
> bugs we have ran into. We have crashed our 64bit many times with the
amount
> of data we are trying to punch through(billion +). To give you some hard
> numbers from our test using it in an OLTP environment, we traced some
daily
> activity and we ran the delete, insert, updates for the same anount of
time
> roughly --
> 32bit 4 way 8GB memory -- 133 Trans/sec
> 64bit 4 way 8GB memory -- 613 Trans/sec
> 32bit 8way 8GB memory -- 493 Trans/sec
> "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
> > Did anyone use the 64 bit version in production with large databases?
> >
> > Is it a better price/performance than the 32 bits version?
> >
> > Any information if highly appreciated.
> >
> > Thanks a lot!
> >
> >
>|||Windows does not use that much memory in a typical sql installation. If you
have a 16GB system and you allocate 14 to SQL, SQL will get 14 assuming no
other memory intensive application is running on there.
"Daniel P." <danutzp1@.hotmail.comU> wrote in message
news:u$zCxb3uDHA.3116@.tk2msftngp13.phx.gbl...
> Finally the kind of answer I was expecting: someone who uses 64 bit every
> day.
> Thank you very much Kevin!!!
> I think I will stick with 32 bit and a lot of memory. I've also notices
that
> the amount of memory makes a big difference.
> BTW: some MS guys came to us about two weeks ago and they said that the OS
> (Windows 2000 or Windows 2003) eats up by default 1/2 of the physical
> memory. So even if you have 16 GB you only have 8 GB available for the
apps
> like SQL Server. The rest is reserved for the OS.
> This is really strange!!!
> They also said this will be changed in Longhorn.
>
> "Kevin Brooks" <jeepnreb@.yahoo.com> wrote in message
> news:uISfnT2uDHA.1340@.TK2MSFTNGP09.phx.gbl...
> > I guess I will chime in. We are running a 4 way 64bit Unysis ES7000
with
> > 16GB of memory on Windows 2003. We are currently using it for an OLAP
> > implementation, however the RDBMS is on the server is well. The best
> > benefit is memory, which we will be bumping up into the 30gigish range
> soon.
> > You can dynamically adjust memory over 8GB(do not really need AWE)
without
> > rebooting SQL. When we are loading data into the cubes we can give SQL
> more
> > and when aggs are being built in the cube give more to OLAP Services.
> > Beyond that memory ease, we have not really noticed a great difference.
> In
> > alot of aspects it is a pain using SQL 64 bit, due to its lack tools and
> > bugs we have ran into. We have crashed our 64bit many times with the
> amount
> > of data we are trying to punch through(billion +). To give you some
hard
> > numbers from our test using it in an OLTP environment, we traced some
> daily
> > activity and we ran the delete, insert, updates for the same anount of
> time
> > roughly --
> >
> > 32bit 4 way 8GB memory -- 133 Trans/sec
> > 64bit 4 way 8GB memory -- 613 Trans/sec
> > 32bit 8way 8GB memory -- 493 Trans/sec
> >
> > "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> > news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
> > > Did anyone use the 64 bit version in production with large databases?
> > >
> > > Is it a better price/performance than the 32 bits version?
> > >
> > > Any information if highly appreciated.
> > >
> > > Thanks a lot!
> > >
> > >
> >
> >
>|||Kevin - when you say crash you mean crashing analysis services, right, not
the RDBMS?
"Kevin Brooks" <jeepnreb@.yahoo.com> wrote in message
news:uISfnT2uDHA.1340@.TK2MSFTNGP09.phx.gbl...
> I guess I will chime in. We are running a 4 way 64bit Unysis ES7000 with
> 16GB of memory on Windows 2003. We are currently using it for an OLAP
> implementation, however the RDBMS is on the server is well. The best
> benefit is memory, which we will be bumping up into the 30gigish range
soon.
> You can dynamically adjust memory over 8GB(do not really need AWE) without
> rebooting SQL. When we are loading data into the cubes we can give SQL
more
> and when aggs are being built in the cube give more to OLAP Services.
> Beyond that memory ease, we have not really noticed a great difference.
In
> alot of aspects it is a pain using SQL 64 bit, due to its lack tools and
> bugs we have ran into. We have crashed our 64bit many times with the
amount
> of data we are trying to punch through(billion +). To give you some hard
> numbers from our test using it in an OLTP environment, we traced some
daily
> activity and we ran the delete, insert, updates for the same anount of
time
> roughly --
> 32bit 4 way 8GB memory -- 133 Trans/sec
> 64bit 4 way 8GB memory -- 613 Trans/sec
> 32bit 8way 8GB memory -- 493 Trans/sec
> "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
> > Did anyone use the 64 bit version in production with large databases?
> >
> > Is it a better price/performance than the 32 bits version?
> >
> > Any information if highly appreciated.
> >
> > Thanks a lot!
> >
> >
>|||> BTW: some MS guys came to us about two weeks ago and they said that the OS
> (Windows 2000 or Windows 2003) eats up by default 1/2 of the physical
> memory. So even if you have 16 GB you only have 8 GB available for the
apps
> like SQL Server. The rest is reserved for the OS.
Up to 4 GB, this may be true (I think the max the system will reserve is 2
GB by default). If your system has more than 4 GB of RAM, the system will
not automatically keep consuming *half.* We have systems with > 4 GB and we
have no problem allocating most of it to SQL Server.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||I have crahsed both. I crashed analysis services a few times with MOLAP
dims of around 30million records being processed. I actually corrupted the
whole olap side (it would start but never respond) and tried to reinstall
it. Long story short, I still have a ticket open with Microsoft for a
reinstall bug 64 bit has. Here is the fun part, we could not get OLAP or
SQL to reinstall and they had no idea, so we had to rebuild the whole OS.
As far as crashing the RDBMS, I really should say we have not corrupted an
entire install. However we have brought our server to its knees and then
beat it into the dirt. Our server has quit responding in several different
ways and had more reboots than most servers should. I need to stop and say
that I do not consider it a bad product and I do like 64bit SQL. We really
do things that are not recommended and invent other things that Microsoft
and Industry people would shy away from. However, yes we have crashed both
sides.
"Kevin" <ReplyTo@.Newsgroups.only> wrote in message
news:ezph58BvDHA.2880@.tk2msftngp13.phx.gbl...
> Kevin - when you say crash you mean crashing analysis services, right, not
> the RDBMS?
>
> "Kevin Brooks" <jeepnreb@.yahoo.com> wrote in message
> news:uISfnT2uDHA.1340@.TK2MSFTNGP09.phx.gbl...
> > I guess I will chime in. We are running a 4 way 64bit Unysis ES7000
with
> > 16GB of memory on Windows 2003. We are currently using it for an OLAP
> > implementation, however the RDBMS is on the server is well. The best
> > benefit is memory, which we will be bumping up into the 30gigish range
> soon.
> > You can dynamically adjust memory over 8GB(do not really need AWE)
without
> > rebooting SQL. When we are loading data into the cubes we can give SQL
> more
> > and when aggs are being built in the cube give more to OLAP Services.
> > Beyond that memory ease, we have not really noticed a great difference.
> In
> > alot of aspects it is a pain using SQL 64 bit, due to its lack tools and
> > bugs we have ran into. We have crashed our 64bit many times with the
> amount
> > of data we are trying to punch through(billion +). To give you some
hard
> > numbers from our test using it in an OLTP environment, we traced some
> daily
> > activity and we ran the delete, insert, updates for the same anount of
> time
> > roughly --
> >
> > 32bit 4 way 8GB memory -- 133 Trans/sec
> > 64bit 4 way 8GB memory -- 613 Trans/sec
> > 32bit 8way 8GB memory -- 493 Trans/sec
> >
> > "Daniel P." <danutzp1@.hotmail.comU> wrote in message
> > news:ODRY0Y0uDHA.2508@.TK2MSFTNGP12.phx.gbl...
> > > Did anyone use the 64 bit version in production with large databases?
> > >
> > > Is it a better price/performance than the 32 bits version?
> > >
> > > Any information if highly appreciated.
> > >
> > > Thanks a lot!
> > >
> > >
> >
> >
>

Sunday, February 19, 2012

6.5 to 2000 upgrade - Logon failure...

Hi All,
I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a new
server running Win2003Server and SQL 2000.
The Upgrade Wizard is dying on the Import and Export phase and giving the
error described in KB Article 302850. The cause being a mismatch of users
and permissions between the two machines and the users that are starting the
MSSQLSever service. I attempted to follow the steps listed in this article,
but ran in the problem that I cannot seem to add a domain user from the NT4
machine as a Local Admin on the 2003 Server (no Active directory support I
guess?)
Any other options for me to get this upgrade to happen?
Thanks.
- MaxinNJ
Hi
The solution in:
http://support.microsoft.com/default...b;en-us;818550
is to upgrade your OS on the NT server. You may want to find a third machine
to do this on! Alternatively you may want to try and use the Import
Wizard/DTS or BCP to retrieve the data (and possibly script the database to
get the DDL).
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
> Hi All,
> I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
> new
> server running Win2003Server and SQL 2000.
> The Upgrade Wizard is dying on the Import and Export phase and giving the
> error described in KB Article 302850. The cause being a mismatch of users
> and permissions between the two machines and the users that are starting
> the
> MSSQLSever service. I attempted to follow the steps listed in this
> article,
> but ran in the problem that I cannot seem to add a domain user from the
> NT4
> machine as a Local Admin on the 2003 Server (no Active directory support I
> guess?)
> Any other options for me to get this upgrade to happen?
> Thanks.
> - MaxinNJ
|||Thanks John - missed that KB article. Well, this at least explains things
Off to find a spare machine and dig up SQL 6.5 disks!
- Max
"John Bell" wrote:

> Hi
> The solution in:
> http://support.microsoft.com/default...b;en-us;818550
> is to upgrade your OS on the NT server. You may want to find a third machine
> to do this on! Alternatively you may want to try and use the Import
> Wizard/DTS or BCP to retrieve the data (and possibly script the database to
> get the DDL).
> John
> "MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
> news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
>
>
|||Hi
Make sure it is also service packed to the correct level.
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:DF507549-A9B1-40ED-BF65-0EB53DFB0DDC@.microsoft.com...[vbcol=seagreen]
> Thanks John - missed that KB article. Well, this at least explains things
>
> Off to find a spare machine and dig up SQL 6.5 disks!
> - Max
> "John Bell" wrote:

6.5 to 2000 upgrade - Logon failure...

Hi All,
I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a new
server running Win2003Server and SQL 2000.
The Upgrade Wizard is dying on the Import and Export phase and giving the
error described in KB Article 302850. The cause being a mismatch of users
and permissions between the two machines and the users that are starting the
MSSQLSever service. I attempted to follow the steps listed in this article,
but ran in the problem that I cannot seem to add a domain user from the NT4
machine as a Local Admin on the 2003 Server (no Active directory support I
guess?)
Any other options for me to get this upgrade to happen?
Thanks.
- MaxinNJHi
The solution in:
http://support.microsoft.com/defaul...kb;en-us;818550
is to upgrade your OS on the NT server. You may want to find a third machine
to do this on! Alternatively you may want to try and use the Import
Wizard/DTS or BCP to retrieve the data (and possibly script the database to
get the DDL).
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
> Hi All,
> I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
> new
> server running Win2003Server and SQL 2000.
> The Upgrade Wizard is dying on the Import and Export phase and giving the
> error described in KB Article 302850. The cause being a mismatch of users
> and permissions between the two machines and the users that are starting
> the
> MSSQLSever service. I attempted to follow the steps listed in this
> article,
> but ran in the problem that I cannot seem to add a domain user from the
> NT4
> machine as a Local Admin on the 2003 Server (no Active directory support I
> guess?)
> Any other options for me to get this upgrade to happen?
> Thanks.
> - MaxinNJ|||Thanks John - missed that KB article. Well, this at least explains things :
)
Off to find a spare machine and dig up SQL 6.5 disks!
- Max
"John Bell" wrote:

> Hi
> The solution in:
> http://support.microsoft.com/defaul...kb;en-us;818550
> is to upgrade your OS on the NT server. You may want to find a third machi
ne
> to do this on! Alternatively you may want to try and use the Import
> Wizard/DTS or BCP to retrieve the data (and possibly script the database t
o
> get the DDL).
> John
> "MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
> news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
>
>|||Hi
Make sure it is also service packed to the correct level.
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:DF507549-A9B1-40ED-BF65-0EB53DFB0DDC@.microsoft.com...[vbcol=seagreen]
> Thanks John - missed that KB article. Well, this at least explains things
>
> Off to find a spare machine and dig up SQL 6.5 disks!
> - Max
> "John Bell" wrote:
>

6.5 to 2000 upgrade - Logon failure...

Hi All,
I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a new
server running Win2003Server and SQL 2000.
The Upgrade Wizard is dying on the Import and Export phase and giving the
error described in KB Article 302850. The cause being a mismatch of users
and permissions between the two machines and the users that are starting the
MSSQLSever service. I attempted to follow the steps listed in this article,
but ran in the problem that I cannot seem to add a domain user from the NT4
machine as a Local Admin on the 2003 Server (no Active directory support I
guess?)
Any other options for me to get this upgrade to happen?
Thanks.
- MaxinNJHi
The solution in:
http://support.microsoft.com/default.aspx?scid=kb;en-us;818550
is to upgrade your OS on the NT server. You may want to find a third machine
to do this on! Alternatively you may want to try and use the Import
Wizard/DTS or BCP to retrieve the data (and possibly script the database to
get the DDL).
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
> Hi All,
> I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
> new
> server running Win2003Server and SQL 2000.
> The Upgrade Wizard is dying on the Import and Export phase and giving the
> error described in KB Article 302850. The cause being a mismatch of users
> and permissions between the two machines and the users that are starting
> the
> MSSQLSever service. I attempted to follow the steps listed in this
> article,
> but ran in the problem that I cannot seem to add a domain user from the
> NT4
> machine as a Local Admin on the 2003 Server (no Active directory support I
> guess?)
> Any other options for me to get this upgrade to happen?
> Thanks.
> - MaxinNJ|||Thanks John - missed that KB article. Well, this at least explains things :)
Off to find a spare machine and dig up SQL 6.5 disks!
- Max
"John Bell" wrote:
> Hi
> The solution in:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;818550
> is to upgrade your OS on the NT server. You may want to find a third machine
> to do this on! Alternatively you may want to try and use the Import
> Wizard/DTS or BCP to retrieve the data (and possibly script the database to
> get the DDL).
> John
> "MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
> news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
> > Hi All,
> >
> > I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
> > new
> > server running Win2003Server and SQL 2000.
> >
> > The Upgrade Wizard is dying on the Import and Export phase and giving the
> > error described in KB Article 302850. The cause being a mismatch of users
> > and permissions between the two machines and the users that are starting
> > the
> > MSSQLSever service. I attempted to follow the steps listed in this
> > article,
> > but ran in the problem that I cannot seem to add a domain user from the
> > NT4
> > machine as a Local Admin on the 2003 Server (no Active directory support I
> > guess?)
> >
> > Any other options for me to get this upgrade to happen?
> >
> > Thanks.
> >
> > - MaxinNJ
>
>|||Hi
Make sure it is also service packed to the correct level.
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:DF507549-A9B1-40ED-BF65-0EB53DFB0DDC@.microsoft.com...
> Thanks John - missed that KB article. Well, this at least explains things
> :)
> Off to find a spare machine and dig up SQL 6.5 disks!
> - Max
> "John Bell" wrote:
>> Hi
>> The solution in:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;818550
>> is to upgrade your OS on the NT server. You may want to find a third
>> machine
>> to do this on! Alternatively you may want to try and use the Import
>> Wizard/DTS or BCP to retrieve the data (and possibly script the database
>> to
>> get the DDL).
>> John
>> "MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
>> news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
>> > Hi All,
>> >
>> > I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
>> > new
>> > server running Win2003Server and SQL 2000.
>> >
>> > The Upgrade Wizard is dying on the Import and Export phase and giving
>> > the
>> > error described in KB Article 302850. The cause being a mismatch of
>> > users
>> > and permissions between the two machines and the users that are
>> > starting
>> > the
>> > MSSQLSever service. I attempted to follow the steps listed in this
>> > article,
>> > but ran in the problem that I cannot seem to add a domain user from the
>> > NT4
>> > machine as a Local Admin on the 2003 Server (no Active directory
>> > support I
>> > guess?)
>> >
>> > Any other options for me to get this upgrade to happen?
>> >
>> > Thanks.
>> >
>> > - MaxinNJ
>>

Thursday, February 16, 2012

5 hard drives

On a server with 5 hard drives, I presume a 2-drive raid-1 and a 3-drive
raid-5 (each 146gb) would be the appropriate config.
The user databases only take up 10-20GB.
This is for a very busy web site, so maintasks are reading and fulltext
search.
What would you recommend locating on the raid-1 as well as the OS?
Thanks SOC.If it's really a busy system, then you should seperate the TLog and Data
files of the database. You should locate the TLog on a RAID1 and locate the
data files on a RAD10 if possible, if not then RAID5.
Locate your OS and SQL Server binaries on a RAID1 so in this case, you'll
need 2 more disks :)
--
Ekrem Önsoy
"SOC" <zxc1@.hotmail.com> wrote in message
news:uXNvyrADIHA.972@.TK2MSFTNGP05.phx.gbl...
> On a server with 5 hard drives, I presume a 2-drive raid-1 and a 3-drive
> raid-5 (each 146gb) would be the appropriate config.
> The user databases only take up 10-20GB.
> This is for a very busy web site, so maintasks are reading and fulltext
> search.
> What would you recommend locating on the raid-1 as well as the OS?
> Thanks SOC.
>
>|||Consider placing the transaction logs and tempdb there. HEAVY writes, which
suffer on RAID5. Your mostly-read application 'should' be ok on the RAID5.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"SOC" <zxc1@.hotmail.com> wrote in message
news:uXNvyrADIHA.972@.TK2MSFTNGP05.phx.gbl...
> On a server with 5 hard drives, I presume a 2-drive raid-1 and a 3-drive
> raid-5 (each 146gb) would be the appropriate config.
> The user databases only take up 10-20GB.
> This is for a very busy web site, so maintasks are reading and fulltext
> search.
> What would you recommend locating on the raid-1 as well as the OS?
> Thanks SOC.
>
>

Saturday, February 11, 2012

4 Queries about DB clustering

Hi, Below are few queries:
1. Say for 2 nodes cluster, Do we need to have 2 copies of Databases( 1 on
each node)
2. Hows does the data Synchronization between different nodes of databases
takes place?
3. In Active/Passive mode, does the passive node database is exactly in the
same state (in terms of data) as that of Active?
4. Is 'Server Cluster' specifically for DB clustering ?
Thanks in advance,
Pankaj A. Chitriv
Answers Inline
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
news:847A2BE3-74E1-4B9E-9D61-EEE40D117155@.microsoft.com...
> Hi, Below are few queries:
> 1. Say for 2 nodes cluster, Do we need to have 2 copies of Databases( 1 on
> each node)
No. Data is on shared storage and is controlled by one node at a time.
> 2. Hows does the data Synchronization between different nodes of databases
> takes place?
There is no synchronization. There is a single data store. Access to this
store is arbitrated by the cluster software.
> 3. In Active/Passive mode, does the passive node database is exactly in
the
> same state (in terms of data) as that of Active?
>
Clustering is failover not scaleout technology.

> 4. Is 'Server Cluster' specifically for DB clustering ?
I am not sure what you mean by "Server Cluster"?
> Thanks in advance,
> Pankaj A. Chitriv
>
|||Thanks Geoff.
"Server Cluster" is a inbuild clustering service provided by Windows 2003
Server.
Just wondering, whether that Single Data Store is a seperate windows system?
If so what if that system breaks down? Is that the case that we do DB
clustering only to distribute the processing capabilities?
What I understood by Single Data Store means is there will be a system on
which SQL DB will be created and there would be multiple servers accessing
the same database. But this cannot be called as DB clustering as we don't
have to configure any VIP to access the single data store. Can you clarify
this please?
Thanks a lot again for your answers.
Regards
Pankaj A. Chitriv
"Geoff N. Hiten" wrote:

> Answers Inline
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
> news:847A2BE3-74E1-4B9E-9D61-EEE40D117155@.microsoft.com...
> No. Data is on shared storage and is controlled by one node at a time.
> There is no synchronization. There is a single data store. Access to this
> store is arbitrated by the cluster software.
> the
> Clustering is failover not scaleout technology.
> I am not sure what you mean by "Server Cluster"?
>
>
|||Server clustering is available on Windows Server 2003 Enterprise Edition.
"Single Data Store" is not a service, it is a description. All data resides
on a single logical device physically connected to all host nodes. This can
be a SCSI array, a Fiber array, or a SAN. Ownership of this device is
arbitrated by the cluster service. Microsoft SQL DB clustering exists as a
failover technology only and has no distributed computing capabilities. It
is not a scale-out technology. One server owns the entire database and no
other server can access the data without moving the entire SQL instance to
another host. Active-Passive and Active-Active are not accurate
descriptions of the current SQL clustering technology but are somewhat
misleading holdovers from an earlier version.
Again, clustering is for availability and does not allow multiple
simultaneous connections to the data store from different host nodes.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
news:4A51BB01-D028-4B3B-9244-12EFA8469987@.microsoft.com...
> Thanks Geoff.
> "Server Cluster" is a inbuild clustering service provided by Windows 2003
> Server.
> Just wondering, whether that Single Data Store is a seperate windows
system?[vbcol=seagreen]
> If so what if that system breaks down? Is that the case that we do DB
> clustering only to distribute the processing capabilities?
> What I understood by Single Data Store means is there will be a system on
> which SQL DB will be created and there would be multiple servers accessing
> the same database. But this cannot be called as DB clustering as we don't
> have to configure any VIP to access the single data store. Can you clarify
> this please?
> Thanks a lot again for your answers.
> Regards
> Pankaj A. Chitriv
> "Geoff N. Hiten" wrote:
Databases( 1 on[vbcol=seagreen]
databases[vbcol=seagreen]
this[vbcol=seagreen]
in[vbcol=seagreen]
|||Hi Geoff.
Thankyou very much for your help. It is just great. I really really
appreciate it.
Further, to summarise our discussion what I understood to implement the SQL
Db Cluster is:
1. I need to have SCSI array, a Fiber array, or a SAN as a shared device
"on which I'll install SQL Server Database".
2. Say in a 2 node cluster, both the nodes would be typically Windows 2k3
Server systems, with the SQL Server Instance reference (SQL Client) to the
shared device on which SQL Server is installed.
3. Say in Active / Passive mode, only 1 Win2k3 system will be utilized and
in case of faliure, the other win2k3 server node will be active.
4. I need to install SQL Client on both the nodes and Sql Server on shared
device.
5. Just wondering whether stored procedures of SQL DB will be executed on
the shared drive or on the Node. Does the shared drive have processing
capabilities?
With this queries clarified , I'm ready to shoot :-).
I really appreciate your help and request your comment on above queries.
Regards,
Pankaj A. Chitriv
"Geoff N. Hiten" wrote:

> Server clustering is available on Windows Server 2003 Enterprise Edition.
> "Single Data Store" is not a service, it is a description. All data resides
> on a single logical device physically connected to all host nodes. This can
> be a SCSI array, a Fiber array, or a SAN. Ownership of this device is
> arbitrated by the cluster service. Microsoft SQL DB clustering exists as a
> failover technology only and has no distributed computing capabilities. It
> is not a scale-out technology. One server owns the entire database and no
> other server can access the data without moving the entire SQL instance to
> another host. Active-Passive and Active-Active are not accurate
> descriptions of the current SQL clustering technology but are somewhat
> misleading holdovers from an earlier version.
> Again, clustering is for availability and does not allow multiple
> simultaneous connections to the data store from different host nodes.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
> news:4A51BB01-D028-4B3B-9244-12EFA8469987@.microsoft.com...
> system?
> Databases( 1 on
> databases
> this
> in
>
>
|||You are getting closer. More comments inline.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
news:1D8FA145-7AF2-4EBE-9FA1-FD9822233F81@.microsoft.com...
> Hi Geoff.
> Thankyou very much for your help. It is just great. I really really
> appreciate it.
> Further, to summarise our discussion what I understood to implement the
SQL
> Db Cluster is:
> 1. I need to have SCSI array, a Fiber array, or a SAN as a shared device
> "on which I'll install SQL Server Database".
The database(s) will live on the shared storage. SQL binaries will live on
the local disks of each cluster host.
> 2. Say in a 2 node cluster, both the nodes would be typically Windows 2k3
> Server systems, with the SQL Server Instance reference (SQL Client) to the
> shared device on which SQL Server is installed.
A basic two-node SQL cluster will have four systems visible. There are the
two physical host nodes. There is the cluster vrtual server itself. There
is the SQL Server virtual server. Each virtual system must have a minimum
of one unique IP address, one unique network name, and a physical disk
device located on the shared array. You access the SQL server by connecting
to the virtual server by name or IP address.
>

> 3. Say in Active / Passive mode, only 1 Win2k3 system will be utilized and
> in case of faliure, the other win2k3 server node will be active.
>
Correct. The current terms are single-instance and multi-instance. Each
new instance of SQL will have its own disk(s), IP address(es), and Network
name. Once an instance is installed, you can set the preferred host order
to determine the "normal" home host for that instance. You can have up to
16 instances on a single cluster.

> 4. I need to install SQL Client on both the nodes and Sql Server on shared
> device.
>
First you install MSCS (Clustering). Windows 2003 has an excellent
clustering wizard that makes it very difficult to create a non-working
cluster. Then you install a clustered instance of SQL server, running the
install CD from the node that currently owns the disk resource you wish to
use as the first SQL disk. You can assign additional disks after
installation. The installer writes the executable files to each host node
you choose as part of the installation. This includes server and client
components.

> 5. Just wondering whether stored procedures of SQL DB will be executed on
> the shared drive or on the Node. Does the shared drive have processing
> capabilities?
The binaries are on each host node. The memory and CPU resources come from
the host node. The data is stored on the shared array. SQL uses a "Shared
Nothing" model so after installation you can run any instance from any host
node, regardless of whether any other node or instance is running.
[vbcol=seagreen]
> With this queries clarified , I'm ready to shoot :-).
> I really appreciate your help and request your comment on above queries.
> Regards,
> Pankaj A. Chitriv
>
>
> "Geoff N. Hiten" wrote:
Edition.[vbcol=seagreen]
resides[vbcol=seagreen]
can[vbcol=seagreen]
as a[vbcol=seagreen]
It[vbcol=seagreen]
no[vbcol=seagreen]
to[vbcol=seagreen]
2003[vbcol=seagreen]
on[vbcol=seagreen]
accessing[vbcol=seagreen]
don't[vbcol=seagreen]
clarify[vbcol=seagreen]
time.[vbcol=seagreen]
to[vbcol=seagreen]
exactly[vbcol=seagreen]
|||I have a question for Geoff.
I have a similar situation where I plan to install/configure multi-instance
cluster.
My question is
a) as we plan to use/assign drive letters what care shoud be taken for
multi-instance cluster (3 active 1, passive/standby)?
Thanks.
Kamal.
"Geoff N. Hiten" wrote:

> You are getting closer. More comments inline.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
> news:1D8FA145-7AF2-4EBE-9FA1-FD9822233F81@.microsoft.com...
> SQL
> The database(s) will live on the shared storage. SQL binaries will live on
> the local disks of each cluster host.
> A basic two-node SQL cluster will have four systems visible. There are the
> two physical host nodes. There is the cluster vrtual server itself. There
> is the SQL Server virtual server. Each virtual system must have a minimum
> of one unique IP address, one unique network name, and a physical disk
> device located on the shared array. You access the SQL server by connecting
> to the virtual server by name or IP address.
> Correct. The current terms are single-instance and multi-instance. Each
> new instance of SQL will have its own disk(s), IP address(es), and Network
> name. Once an instance is installed, you can set the preferred host order
> to determine the "normal" home host for that instance. You can have up to
> 16 instances on a single cluster.
> First you install MSCS (Clustering). Windows 2003 has an excellent
> clustering wizard that makes it very difficult to create a non-working
> cluster. Then you install a clustered instance of SQL server, running the
> install CD from the node that currently owns the disk resource you wish to
> use as the first SQL disk. You can assign additional disks after
> installation. The installer writes the executable files to each host node
> you choose as part of the installation. This includes server and client
> components.
>
> The binaries are on each host node. The memory and CPU resources come from
> the host node. The data is stored on the shared array. SQL uses a "Shared
> Nothing" model so after installation you can run any instance from any host
> node, regardless of whether any other node or instance is running.
> Edition.
> resides
> can
> as a
> It
> no
> to
> 2003
> on
> accessing
> don't
> clarify
> time.
> to
> exactly
>
>
|||All drives will need to be visible to all hosts for failover. Drive letters
are assigned cluster-wide for shared resources. The easiest way is to
pretend you are building a multi-instance stand-alone system where SQL Data
and Logs from multiple instances cannot intersect on the same LUN. Also
remember to add a drive for MSDTC and for the Quorum. Don't forget to leave
room for expansion.
Example
C for local boot, Z for local CD-ROM (Old Novell habit)
Q for Quorum, M for MSDTC
K,L for SQLInstance1 data and logs respectively
R,S for SQLInstance2 data and logs respectively
lather, rinse, repeat.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kamal Hassan" <KamalHassan@.discussions.microsoft.com> wrote in message
news:5D8375C6-8269-46FC-B619-BD75E0F8A6CD@.microsoft.com...
> I have a question for Geoff.
> I have a similar situation where I plan to install/configure
multi-instance[vbcol=seagreen]
> cluster.
> My question is
> a) as we plan to use/assign drive letters what care shoud be taken for
> multi-instance cluster (3 active 1, passive/standby)?
> Thanks.
> Kamal.
>
>
> "Geoff N. Hiten" wrote:
the[vbcol=seagreen]
device[vbcol=seagreen]
on[vbcol=seagreen]
2k3[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
There[vbcol=seagreen]
minimum[vbcol=seagreen]
connecting[vbcol=seagreen]
and[vbcol=seagreen]
Each[vbcol=seagreen]
Network[vbcol=seagreen]
order[vbcol=seagreen]
to[vbcol=seagreen]
shared[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
node[vbcol=seagreen]
on[vbcol=seagreen]
processing[vbcol=seagreen]
from[vbcol=seagreen]
"Shared[vbcol=seagreen]
host[vbcol=seagreen]
queries.[vbcol=seagreen]
This[vbcol=seagreen]
is[vbcol=seagreen]
exists[vbcol=seagreen]
capabilities.[vbcol=seagreen]
and[vbcol=seagreen]
instance[vbcol=seagreen]
somewhat[vbcol=seagreen]
nodes.[vbcol=seagreen]
Windows[vbcol=seagreen]
windows[vbcol=seagreen]
DB[vbcol=seagreen]
system[vbcol=seagreen]
we[vbcol=seagreen]
message[vbcol=seagreen]
a[vbcol=seagreen]
of[vbcol=seagreen]
Access[vbcol=seagreen]
|||First, manythanks for quick reply.
In your suggestion is the SQLinstance1 and SQLInstance refer to as ACTIVE
nodes with StandyBy Server or ?
We are not using MSDTC do we still have to setup/configure? and what do you
mean don't forget to leave for expnasion?
Thanks a lot!
Kamal.
"Geoff N. Hiten" wrote:

> All drives will need to be visible to all hosts for failover. Drive letters
> are assigned cluster-wide for shared resources. The easiest way is to
> pretend you are building a multi-instance stand-alone system where SQL Data
> and Logs from multiple instances cannot intersect on the same LUN. Also
> remember to add a drive for MSDTC and for the Quorum. Don't forget to leave
> room for expansion.
> Example
> C for local boot, Z for local CD-ROM (Old Novell habit)
> Q for Quorum, M for MSDTC
> K,L for SQLInstance1 data and logs respectively
> R,S for SQLInstance2 data and logs respectively
> lather, rinse, repeat.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Kamal Hassan" <KamalHassan@.discussions.microsoft.com> wrote in message
> news:5D8375C6-8269-46FC-B619-BD75E0F8A6CD@.microsoft.com...
> multi-instance
> the
> device
> on
> 2k3
> the
> the
> There
> minimum
> connecting
> and
> Each
> Network
> order
> to
> shared
> the
> to
> node
> on
> processing
> from
> "Shared
> host
> queries.
> This
> is
> exists
> capabilities.
> and
> instance
> somewhat
> nodes.
> Windows
> windows
> DB
> system
> we
> message
> a
> of
> Access
>
>
|||Active\Active and Active\Passive are not accurate terms. Each SQL instance
is its own virtual server.
SQLInstance1 and 2 refer to the SQL virtual servers\instances. The host
nodes are all configured identically.
You will have to add disk storage sometime down the road. Leave empty drive
letters for adding new disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kamal Hassan" <KamalHassan@.discussions.microsoft.com> wrote in message
news:DD172480-C6FA-41A6-86CC-65A2C790D3C6@.microsoft.com...
> First, manythanks for quick reply.
> In your suggestion is the SQLinstance1 and SQLInstance refer to as ACTIVE
> nodes with StandyBy Server or ?
> We are not using MSDTC do we still have to setup/configure? and what do
you[vbcol=seagreen]
> mean don't forget to leave for expnasion?
> Thanks a lot!
> Kamal.
>
> "Geoff N. Hiten" wrote:
letters[vbcol=seagreen]
Data[vbcol=seagreen]
leave[vbcol=seagreen]
really[vbcol=seagreen]
implement[vbcol=seagreen]
live[vbcol=seagreen]
Windows[vbcol=seagreen]
Client) to[vbcol=seagreen]
are[vbcol=seagreen]
disk[vbcol=seagreen]
utilized[vbcol=seagreen]
up[vbcol=seagreen]
on[vbcol=seagreen]
non-working[vbcol=seagreen]
running[vbcol=seagreen]
wish[vbcol=seagreen]
host[vbcol=seagreen]
client[vbcol=seagreen]
executed[vbcol=seagreen]
come[vbcol=seagreen]
any[vbcol=seagreen]
data[vbcol=seagreen]
nodes.[vbcol=seagreen]
device[vbcol=seagreen]
database[vbcol=seagreen]
multiple[vbcol=seagreen]
message[vbcol=seagreen]
we do[vbcol=seagreen]
a[vbcol=seagreen]
servers[vbcol=seagreen]
as[vbcol=seagreen]
you[vbcol=seagreen]
at[vbcol=seagreen]
nodes[vbcol=seagreen]
is[vbcol=seagreen]