Code Review

I'm trying to set up a code review process for anything I release into
production on one of my servers. (we have a problem with being responsible
for hosting apps that we didn't develop)
The only things I could think of to put in the policy to check would be:
All Stored Procedures and Views will be:
1)Run through Query Analyzer to check for table scans and other
inefficiencies
2)Run through SQL Profiler
3)Reviewed to ensure developer did not use cursors and temp tables unless
absolutely necessary
Database Architecture will be examined prior to deployment.
Any suggestions?
Security issues
Ownership chains
Use of extended stored procs.
Linked server issues etc.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Amanda" <Amanda@.discussions.microsoft.com> wrote in message
news:DF9E1B44-BE57-403B-B4ED-77F1F19C4B0A@.microsoft.com...
> I'm trying to set up a code review process for anything I release into
> production on one of my servers. (we have a problem with being
responsible
> for hosting apps that we didn't develop)
> The only things I could think of to put in the policy to check would be:
> All Stored Procedures and Views will be:
> 1) Run through Query Analyzer to check for table scans and other
> inefficiencies
> 2) Run through SQL Profiler
> 3) Reviewed to ensure developer did not use cursors and temp tables unless
> absolutely necessary
> Database Architecture will be examined prior to deployment.
> Any suggestions?
>
|||Amanda wrote:
> I'm trying to set up a code review process for anything I release into
> production on one of my servers. (we have a problem with being
> responsible for hosting apps that we didn't develop)
> The only things I could think of to put in the policy to check would
> be: All Stored Procedures and Views will be:
> 1) Run through Query Analyzer to check for table scans and other
> inefficiencies
> 2) Run through SQL Profiler
> 3) Reviewed to ensure developer did not use cursors and temp tables
> unless absolutely necessary
> Database Architecture will be examined prior to deployment.
> Any suggestions?
and...
- Test on a database with the same or similar data to the production
database
- Full regression testing from application while Profiler is running
- Clustered Index Scans in addition to Table Scans
David G.
|||Thanks guys!
I know what I want to look for but I couldn't articulate it.

Clustering with share nothing

Hello,
We're are in the basic design process for a cluster. We have some confusion
as to whether SQL Server clustering supports a share nothing scenario - that
is where the clustered machines have their own storage and do not share
storage.
We're trying to find out if this is supported, and if it is, what are the
downsides to this approach versus using a shared storage device.
Any help or comments greatly appreciated.
Thank you,
Greg Hayes
Funny you should use that term. Microsoft uses the shared nothing model,
only it means that the controlling node does not share with any other
node(s). One node owns a resource at a time.
You can get what you need from Majority Node Set (MNS) read all about it
here:
http://www.microsoft.com/windowsserv...lustergeo.mspx
or view an excellent webcast here:
http://support.microsoft.com/default...b;en-us;838612
lastly Tech Net has some great information here:
http://www.microsoft.com/technet/pro...g/majnode.mspx
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Greg Hayes" <grandgousier@.verizon.net> wrote in message
news:eYUZj8qaEHA.3804@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We're are in the basic design process for a cluster. We have some
confusion
> as to whether SQL Server clustering supports a share nothing scenario -
that
> is where the clustered machines have their own storage and do not share
> storage.
> We're trying to find out if this is supported, and if it is, what are the
> downsides to this approach versus using a shared storage device.
> Any help or comments greatly appreciated.
> Thank you,
> Greg Hayes
>
|||But as far as I know, SQL 2000 does not support MNS.
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
Specialist SQL Server Solutions and Consulting
MVP Program: http://www.microsoft.com/mvp
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:ewrY7QsaEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Funny you should use that term. Microsoft uses the shared nothing model,
> only it means that the controlling node does not share with any other
> node(s). One node owns a resource at a time.
> You can get what you need from Majority Node Set (MNS) read all about it
> here:
>
http://www.microsoft.com/windowsserv...lustergeo.mspx
> or view an excellent webcast here:
> http://support.microsoft.com/default...b;en-us;838612
> lastly Tech Net has some great information here:
>
http://www.microsoft.com/technet/pro...g/majnode.mspx[vbcol=seagreen]
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "Greg Hayes" <grandgousier@.verizon.net> wrote in message
> news:eYUZj8qaEHA.3804@.TK2MSFTNGP10.phx.gbl...
> confusion
> that
the
>
|||That is true. So third party time it is ;)
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uci3tezaEHA.3752@.TK2MSFTNGP12.phx.gbl...
> But as far as I know, SQL 2000 does not support MNS.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Epprecht Consulting (PTY) LTD
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> Specialist SQL Server Solutions and Consulting
> MVP Program: http://www.microsoft.com/mvp
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:ewrY7QsaEHA.1732@.TK2MSFTNGP09.phx.gbl...
>
http://www.microsoft.com/windowsserv...lustergeo.mspx
>
http://www.microsoft.com/technet/pro...g/majnode.mspx[vbcol=seagreen]
scenario -[vbcol=seagreen]
share
> the
>

Clustering SQL Server 2000 Analysis Services

We are in the process of deploying AS on a 2-node Active-Passive SQL Server
2000 MSCS cluster. I understand there is a MS white paper on how to cluster
it which requires lots of manual changes. If we were to follow this paper,
would it be possible to have the AS tools shared across with other SQL
virtual servers on the same cluster? Any experiences with this configuration
are appreciated.
NewsgroupUser wrote:

> We are in the process of deploying AS on a 2-node Active-Passive SQL Server
> 2000 MSCS cluster. I understand there is a MS white paper on how to cluster
> it which requires lots of manual changes. If we were to follow this paper,
> would it be possible to have the AS tools shared across with other SQL
> virtual servers on the same cluster? Any experiences with this configuration
> are appreciated.
I've used reciently that paper (http://support.microsoft.com/?kbid=308023)
with a virtual cluster over Microsoft Virtual Server 2005/Win2K3, and
really works.
I've tested failover and no problems..
coke.cl [-en-] gmail.com
http://www.foto-digital.cl/

Clustered SQL7 upgrade to SQL2000 fails to find default server

We are trying to upgrade to SQL2000 in a failover cluster
environment but the upgrade process is failing to identify
the default server and is instead creating a new named
instance of SQL2000 alongside SQL7 (the 'default' checkbox
on the upgrade wizard is greyed out and unchecked). The
production database is 125Gb so I don't want to use the
copy database wizard if possible. Can anyone suggest how
to get round this? Is it a registry setting?
TIA
JohnI am not sure what process you are taking to do this but here is the proper
sequence:
1. Uncluster SQL Server 7.0 cluster
2. Upgrade SQL Server 7.0 to a SQL Server 2000 default instance (putting
binaries on a local drive)
3. Upgrade the default instance of SQL Server 2000 ti a clustered intance
of SQL Server.
This is documetned in Books on Line:
Upgrading to a SQL SErver 2000 Failover Cluster
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand,
this is exactly the process we are trying to follow, but
the 2nd step fails because the upgrade process can't find
the default SQL7 server to upgrade in place and instead
creates a new instance of SQL2000. We have tried this over
and over again, even to the point of completely removing
and reinstalling SQL7. I've had no trouble before with
upgrading a standalone server so it's probably something
to do with the clustering. Any suggestions would be
greatly appreciated...

>--Original Message--
>I am not sure what process you are taking to do this but
here is the proper
>sequence:
>1. Uncluster SQL Server 7.0 cluster
>2. Upgrade SQL Server 7.0 to a SQL Server 2000 default
instance (putting
>binaries on a local drive)
>3. Upgrade the default instance of SQL Server 2000 ti a
clustered intance
>of SQL Server.
>This is documetned in Books on Line:
>Upgrading to a SQL SErver 2000 Failover Cluster
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>