Showing posts with label includes. Show all posts
Showing posts with label includes. Show all posts

Sunday, March 25, 2012

BEST RECOMMENDATION FOR A TESTING SCENARIO

guys:
I would like to have your best advise.
We am planning to install Passive/Active SQL server Clustering in the
production environment that includes two identical Dell PowerEdge 6650 dual
processor servers with a External Disk Storage PoweVault 220S. We have
bought two copies of Windows 2003 enterprise (for each one of the servers)
and one only copy of SQL Server 200 enterprise Edition licensed per
processor (I was told that only one copy of this software ins needed in an
Active/Passive mode)
On the other hand, since the configuration above would be in production at
all times, we would like to have similar scenario for development and
testing purposes.I was advised to replicate the same hardware and software
scenario described above, however, as you can see, it would be a costly
endeavor. Each Dell 6650 costs approximately $20,000 (two processors, 8 GB
RAM, 2 MB cache) the External Raid $8,000, the Windows 2003 Enterprise
server software $3,000 (for the two servers), and the SQL Server 200
enterprise software about $24,000 (license for two processor, for just one
server)
Could you please if you see any issue in the production scenario? Are we Ok
using only one copy of SQL server there?
Secondly, do we have any other choice for a development and testing
scenario? Most people recommend that a development and testing scenario
would be, if not identical, at least very similar to the production
scenario. I was planning to get those Dell 6650 server but with a single
processor, only 1 GB of RAM, and 1 MB cache (or even 512 KB). In terms of
software I was also told that one economical approach would be to acquire
the MSDN Universal subscription that allows use software for testing
(Windows and SQL server)
Thirdly, do you have any other (most economical recommendation in terms of
hardware and software for our development and testing scenario? How critical
is that this has to be very similar (or identical) to the production
scenario?
Thanks for all your answers
White
First off, what you are implementing is a single instance cluster, not an
active/passive cluster. It may just look like a term, but there is a very
dramatic difference between the two.
As for licensing SQL Server in a cluster, you have exactly what you need.
The easiest way to tally up licensing for a cluster is to ask how many SQL
Servers you can connect to from an application. In your case, it would be
1.
For the dev/testing environments, you do not need to purchase the Enterprise
Edition of SQL Server. You can use the Developer Edition which gives you
the full functionality of Enterprise Edition without all of the cost and
hardware requirements. This even allows you to simulate a cluster, you just
don't get full clustering functionality. But, you do NOT need to stuff
clusters into your dev/test environments. There is no case that I'm aware
of where a clustered SQL Server behaves differently with respect to an
application than a standalone SQL Server.
My recommendation would be to purchase a Dell 6650 with the external RAID
array. Depending on your testing and development scenario, you can very
easily place BOTH dev and test on the same machine in different SQL Server
instances without collisions. The only real reason to have completely
different systems for the two would be if you are doing a lot of very heavy
performance related work. If not, you can get away with a single machine
with external array + Windows 2003 Server + SQL Server 2000 Developer
Edition.
I can send you my address so you can send a check for the ~$54,000 that I
just saved you.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Monday, February 13, 2012

Beginners Question

This is probably straight forward, but let's see:

Say I have a Family which includes an address field table and a related
FamilyMembers table which includes an age field.

I need to output a report on each Family where there is at least one
family member with an age over 16.

Any help gratefully received!Can you specify the details of the stuctures of both the tables?

Regards
Debian

*** Sent via Developersdex http://www.developersdex.com ***|||You need to join those two tables. Then you can filter them on condition(s)
you need. This would be one way of doing it, please specifiy structure and
expected result if this isnt good enough:

select ColumnList -- list of columns you need returned
from
Family f
inner join FamilyMembers fm on f.PK_Family = fm.PK_Family
where
fm.Age > 16

-- PK_Family is Primary Key on Family table

MC

"RichMUK" <support@.insurance.uk.com> wrote in message
news:1119522354.673863.165840@.g49g2000cwa.googlegr oups.com...
> This is probably straight forward, but let's see:
> Say I have a Family which includes an address field table and a related
> FamilyMembers table which includes an age field.
> I need to output a report on each Family where there is at least one
> family member with an age over 16.
> Any help gratefully received!|||Thanks debian & MC.

MCs query works fine but I need to report just one record per family.
In this example the tables are:

Family.FamilyID [id]
Family.FamilyName
Family.Address

and

FamilyMembers.FamilyMemberID [id]
FamilyMembers.FamilyID
FamilyMembers.FirstName
FamilyMembers.Age

SELECT f.FamilyID, f.FamilyName, f.Address
FROM dbo.Family f INNER JOIN
dbo.FamilyMembers fm ON f.FamilyID = fm.FamilyID
WHERE (fm.Age > 16)

MC, the query you suggest repeats the same Family. record by the number
of FamilyMembers in the query.
I hope this makes sense.

Rich|||RichMUK (support@.insurance.uk.com) writes:
> MCs query works fine but I need to report just one record per family.
> In this example the tables are:
> Family.FamilyID [id]
> Family.FamilyName
> Family.Address
> and
> FamilyMembers.FamilyMemberID [id]
> FamilyMembers.FamilyID
> FamilyMembers.FirstName
> FamilyMembers.Age
> SELECT f.FamilyID, f.FamilyName, f.Address
> FROM dbo.Family f INNER JOIN
> dbo.FamilyMembers fm ON f.FamilyID = fm.FamilyID
> WHERE (fm.Age > 16)
> MC, the query you suggest repeats the same Family. record by the number
> of FamilyMembers in the query.

SELECT f.FamilyID, f.FamilyName, f.Address
FROM dbo.Family f
WHERE EXISTS (SELECT *
FROM dbo.FamilyMembers fm
WHERE f.FamilyID = fm.FamilyID
AND fm.Age > 16)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp