Should this tool be installed and run in a production server?
MM
barney@.newsgroups.nospam
Martin,
If you are concerned about installing this tool on production server, you
can install this tool on a remote machine and you could analyze a production
server from a remote machine (as long as you can connect to target SQL
Server from remote machine)
SQL Best Practices Analyzer relies on the BPA Repository database, which is
a SQL Server database created during SQL BPA installation. You can have this
BPA repository database created on local SQL Server or a remote SQL Server.
SQL Best Practices Analyzer requires the following components to be
installed on the machine
.. Microsoft Internet Explorer 6.0 or later
.. Microsoft .Net Framework 1.1
Reference:
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Sethu
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.
"Martin Millar" <barney@.newsgroups.nospam> wrote in message
news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
> Should this tool be installed and run in a production server?
> --
> MM
> barney@.newsgroups.nospam
|||Thanks for this. perhaps I should have been a bit more precise. I am a
developer and I'm having a beef with my DBA who has installed this on the
live production server. My argument is that this should be installed and run
on a test system as there is no need to test the performance of the hardware
on which the DB runs on.
If it's OK on Test then it gets ported to live. I believe that anything that
does not need to be installed on a production server should not be on there
as there is a danger that something else running on the box may result in a
loss of service or may intoduce a risk of virus or attack. This tool requires
the dot.net framework and I am a strong fan of this being an asp.net
developer. But until this (dot.net) becomes a core part of the OS (i.e. when
it's installed by default on XP, win2003 etc) I categorise this as a
development add-on and has an attached if installed.
If MS release a security patch for dot.net then I need to schedule downtime
on the production server to apply this.
So back to my original question, which is in itself is about best practises,
should it be best practise to install the BPA on a production server?
Thanks in advance
"Sethu Srinivasan [MSFT]" wrote:
> Martin,
> If you are concerned about installing this tool on production server, you
> can install this tool on a remote machine and you could analyze a production
> server from a remote machine (as long as you can connect to target SQL
> Server from remote machine)
> SQL Best Practices Analyzer relies on the BPA Repository database, which is
> a SQL Server database created during SQL BPA installation. You can have this
> BPA repository database created on local SQL Server or a remote SQL Server.
> SQL Best Practices Analyzer requires the following components to be
> installed on the machine
> .. Microsoft Internet Explorer 6.0 or later
> .. Microsoft .Net Framework 1.1
> Reference:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Thanks
> Sethu
> --
> 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.
>
> "Martin Millar" <barney@.newsgroups.nospam> wrote in message
> news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
>
>
Showing posts with label tool. Show all posts
Showing posts with label tool. Show all posts
Friday, March 30, 2012
Microsoft SQL Server 2005 Best Practices Analyzer
Does anyone know if this tool is released or just still in beta?
It will not update, the site is: http://go.microsoft.com/fwlink/?LinkID=82044
Not released yet. However, you can download the latest CTP (public pre-release) version here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=DA0531E4-E94C-4991-82FA-F0E3FBD05E63&displaylang=en
Friday, March 9, 2012
MetaData Repository Standards (crossposted from comp.databases.ms-access)
I put this up on the other NG, then thought better of it...
---
I'm tasked with developing a enterprise-level metadata tool - starting yesterday
and TB delivered by Jan 30th.
There actually is some small chance of my delivering same - since I've already
done something similar in the context of recording report requirements (field
sources, calculations, and so-forth).
But this time, I'd like to do the architecture the "right" way - i.e. with the
same table structure that some commercially-avaiable tools use.
Anybody know of a reference book that details this sort of architecture? It's
not quite as obvious as it may seem at first because of various recursive
relationships - like fields/calculation components and allowed values/sub
values.
--
PeteCresswellHave you had a look at SQL Server Meta Data Services' Here is what it does:
Meta Data Services is intended to store meta data, and it is designed to be
integrated with other tools and applications. It provides a solution for
storing and managing data warehousing definitions, OLAP definitions, design
data used in development tools, and any other type of meta data used in a
programming environment.
I've not personally worked with this, but maybe it can meet some of your
requirements.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"(Pete Cresswell)" <x@.y.z> wrote in message
news:aeevtvkbg1aae0enkk28pfi5jbchsnl6j2@.4ax.com...
> I put this up on the other NG, then thought better of it...
> ---
> I'm tasked with developing a enterprise-level metadata tool - starting
yesterday
> and TB delivered by Jan 30th.
> There actually is some small chance of my delivering same - since I've
already
> done something similar in the context of recording report requirements
(field
> sources, calculations, and so-forth).
> But this time, I'd like to do the architecture the "right" way - i.e. with
the
> same table structure that some commercially-avaiable tools use.
> Anybody know of a reference book that details this sort of architecture?
It's
> not quite as obvious as it may seem at first because of various recursive
> relationships - like fields/calculation components and allowed values/sub
> values.
> --
> PeteCresswell|||> Meta Data Services is intended to store meta data, and it is designed to be
We're using a product called PACE - implmented here with an Oracle
back end.
It's primary uses are
- As a staging area for data flowing into local systems from
outside vendors
- As a staging area for the reverse: data from local systems
to the outside
- As a historical archive: some systems want to know the state
of, say, a muncipal bond as of a certain day in the past.
Over the years it's grown and grown - becoming slower and more
complex.
The tactical problems at hand are three:
1) That people have used it's "UserField" definition capability
extensively and created many duplicate calulation fields which need to
be identified and coalesced.
2) The owners suspect there are a number of loops: i.e. a field comes
from and outside vendor, goes into local system XYZ, and then gets
harvested back into the staging area unchanged.
3) By now it must contain a number of "orphan" fields: fields that
are not used by any local system.
The tool I'm writing will enable various people to document each field
in PACE: all the places it comes from, all the places it goes, how
often it's refreshed, the properties of each of it's incarnations,
rollup calculations, user calculations, upload
calulations/transformations, and so-forth.
I can think of several data architectures/table designs/whatever to
accomplish this, but I'd *really* like to copy something written for
the same niche that has a proven track record - both for
bulletproofness, and because eventually they'll purchase a "real" tool
and there will be a migration...
Of course, nobody's saying what the "real" tool will be - but I'm
hoping that all the major contenders' developers will have arrived at
similar designs looking at the same requirements...
---
I'm tasked with developing a enterprise-level metadata tool - starting yesterday
and TB delivered by Jan 30th.
There actually is some small chance of my delivering same - since I've already
done something similar in the context of recording report requirements (field
sources, calculations, and so-forth).
But this time, I'd like to do the architecture the "right" way - i.e. with the
same table structure that some commercially-avaiable tools use.
Anybody know of a reference book that details this sort of architecture? It's
not quite as obvious as it may seem at first because of various recursive
relationships - like fields/calculation components and allowed values/sub
values.
--
PeteCresswellHave you had a look at SQL Server Meta Data Services' Here is what it does:
Meta Data Services is intended to store meta data, and it is designed to be
integrated with other tools and applications. It provides a solution for
storing and managing data warehousing definitions, OLAP definitions, design
data used in development tools, and any other type of meta data used in a
programming environment.
I've not personally worked with this, but maybe it can meet some of your
requirements.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"(Pete Cresswell)" <x@.y.z> wrote in message
news:aeevtvkbg1aae0enkk28pfi5jbchsnl6j2@.4ax.com...
> I put this up on the other NG, then thought better of it...
> ---
> I'm tasked with developing a enterprise-level metadata tool - starting
yesterday
> and TB delivered by Jan 30th.
> There actually is some small chance of my delivering same - since I've
already
> done something similar in the context of recording report requirements
(field
> sources, calculations, and so-forth).
> But this time, I'd like to do the architecture the "right" way - i.e. with
the
> same table structure that some commercially-avaiable tools use.
> Anybody know of a reference book that details this sort of architecture?
It's
> not quite as obvious as it may seem at first because of various recursive
> relationships - like fields/calculation components and allowed values/sub
> values.
> --
> PeteCresswell|||> Meta Data Services is intended to store meta data, and it is designed to be
We're using a product called PACE - implmented here with an Oracle
back end.
It's primary uses are
- As a staging area for data flowing into local systems from
outside vendors
- As a staging area for the reverse: data from local systems
to the outside
- As a historical archive: some systems want to know the state
of, say, a muncipal bond as of a certain day in the past.
Over the years it's grown and grown - becoming slower and more
complex.
The tactical problems at hand are three:
1) That people have used it's "UserField" definition capability
extensively and created many duplicate calulation fields which need to
be identified and coalesced.
2) The owners suspect there are a number of loops: i.e. a field comes
from and outside vendor, goes into local system XYZ, and then gets
harvested back into the staging area unchanged.
3) By now it must contain a number of "orphan" fields: fields that
are not used by any local system.
The tool I'm writing will enable various people to document each field
in PACE: all the places it comes from, all the places it goes, how
often it's refreshed, the properties of each of it's incarnations,
rollup calculations, user calculations, upload
calulations/transformations, and so-forth.
I can think of several data architectures/table designs/whatever to
accomplish this, but I'd *really* like to copy something written for
the same niche that has a proven track record - both for
bulletproofness, and because eventually they'll purchase a "real" tool
and there will be a migration...
Of course, nobody's saying what the "real" tool will be - but I'm
hoping that all the major contenders' developers will have arrived at
similar designs looking at the same requirements...
Subscribe to:
Posts (Atom)