Does anyone have any techniques to be able to display what environment a
server might be part of (e.g. Production, UAT, Development etc).
Instance names already follow a standard naming convention (non descriptive)
so that is not an option.
My ideal solution would be to have a description appear for the server
registration in SSMS or Entman.
e.g.
server1 (SQL Server 8.0.878 - dom1\myuser)
would become...
server1 (SQL Server 8.0.878 PRODUCTION - dom1\myuser)
-
What metadata/ registry entries would I need to change to get this. Would it
cause issues (such as service pack upgrade problems). I would prefer not to
have to resort to putting this in a db/ table since I want the information
visible without having to issue a query.
Many thanks,
Mark.Hi
How does it know whether SQL Server uses PRODUCTION ir DEVELOPMENT?
http://dimantdatabasesolutions.blog...er.ht
ml
"news.microsoft.com" <nospam@.nospam.com> wrote in message
news:OFMENhYNIHA.5140@.TK2MSFTNGP05.phx.gbl...
> Does anyone have any techniques to be able to display what environment a
> server might be part of (e.g. Production, UAT, Development etc).
> Instance names already follow a standard naming convention (non
> descriptive) so that is not an option.
> My ideal solution would be to have a description appear for the server
> registration in SSMS or Entman.
> e.g.
> server1 (SQL Server 8.0.878 - dom1\myuser)
> would become...
> server1 (SQL Server 8.0.878 PRODUCTION - dom1\myuser)
> -
> What metadata/ registry entries would I need to change to get this. Would
> it cause issues (such as service pack upgrade problems). I would prefer
> not to have to resort to putting this in a db/ table since I want the
> information visible without having to issue a query.
> Many thanks,
> Mark.
>|||> My ideal solution would be to have a description appear for the server
> registration in SSMS or Entman.
Both SSMS and Enterprise Manager allow you to to logically group servers.
You might consider creating different groups for PROD, UAT, etc. to
categorize your servers by environment.
Hope this helps.
Dan Guzman
SQL Server MVP
"news.microsoft.com" <nospam@.nospam.com> wrote in message
news:OFMENhYNIHA.5140@.TK2MSFTNGP05.phx.gbl...
> Does anyone have any techniques to be able to display what environment a
> server might be part of (e.g. Production, UAT, Development etc).
> Instance names already follow a standard naming convention (non
> descriptive) so that is not an option.
> My ideal solution would be to have a description appear for the server
> registration in SSMS or Entman.
> e.g.
> server1 (SQL Server 8.0.878 - dom1\myuser)
> would become...
> server1 (SQL Server 8.0.878 PRODUCTION - dom1\myuser)
> -
> What metadata/ registry entries would I need to change to get this. Would
> it cause issues (such as service pack upgrade problems). I would prefer
> not to have to resort to putting this in a db/ table since I want the
> information visible without having to issue a query.
> Many thanks,
> Mark.
>|||those properties just tell me about the installation and are readonly.
I'm looking to add a custom property description that will be displayed at
the server registration.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uUguZuZNIHA.1168@.TK2MSFTNGP02.phx.gbl...
> Hi
> How does it know whether SQL Server uses PRODUCTION ir DEVELOPMENT?
> http://dimantdatabasesolutions.blog...er.
html
> "news.microsoft.com" <nospam@.nospam.com> wrote in message
> news:OFMENhYNIHA.5140@.TK2MSFTNGP05.phx.gbl...
>|||that would only help me (and I dont want to distribute anything).
what I need is for the logical server usage name to be displayed whenever a
developer registers a server.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:5F7B5747-FBF7-44BA-9D5A-5387DCA323CC@.microsoft.com...
> Both SSMS and Enterprise Manager allow you to to logically group servers.
> You might consider creating different groups for PROD, UAT, etc. to
> categorize your servers by environment.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "news.microsoft.com" <nospam@.nospam.com> wrote in message
> news:OFMENhYNIHA.5140@.TK2MSFTNGP05.phx.gbl...
>|||> what I need is for the logical server usage name to be displayed whenever
> a developer registers a server.
I don't have suggestion other than those already mentioned. The Best
Practice is to use mnemonic server/instance names that include the role of
the server but you mentioned that's not an option.
Hope this helps.
Dan Guzman
SQL Server MVP
"news.microsoft.com" <nospam@.nospam.com> wrote in message
news:O9shrmlNIHA.5988@.TK2MSFTNGP02.phx.gbl...
> that would only help me (and I dont want to distribute anything).
> what I need is for the logical server usage name to be displayed whenever
> a developer registers a server.
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:5F7B5747-FBF7-44BA-9D5A-5387DCA323CC@.microsoft.com...
>|||Thanks anyway Dan, always good to know opinions on best practice though.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:C9D2AAAF-D3F1-4293-97FC-951A096736F2@.microsoft.com...
> I don't have suggestion other than those already mentioned. The Best
> Practice is to use mnemonic server/instance names that include the role of
> the server but you mentioned that's not an option.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "news.microsoft.com" <nospam@.nospam.com> wrote in message
> news:O9shrmlNIHA.5988@.TK2MSFTNGP02.phx.gbl...
>
2012年3月29日星期四
2012年3月11日星期日
Disaster/recovery techniques
I have recently installed SQL Server 2000 on a newly acquired Windows
2003 server. The network admins also got Brightstor Agent for SQL
Server to interface with Brightstor ARCserve Backup for Windows
running on our backup server. I think I have a pretty good handle on
how to setup the SQL Server backups using a combination of
full/differential/transaction log backups to handle any recovery
required for the SQL Server databases.
What are the alternatives for backing up the Server itself for use in
recovery? Two approaches come to mind.
The first is not worry about backing up the server, in which case for
a recovery, I would have to reinstall all the software and service
packs to rebuild the environment. This would certainly require that I
have fully documented what applications (Windows 2003 server, SQL
Server, Outlook, Brightstor Agent, etc) and the install options that
were chosen. The rebuild process for this could take some time, and
there may be some issues that I haven't considered.
The second is to fully backup the server including the registry. If
everything were installed to the "C:\" drive, I could maybe get by
with just backing up the "C:\" drive and the registry. I do have a
weekend window where I could down the server to perform this task on a
weekly basis. Then for recovery I could just install an operating
system, restore from the backup of the "C:\" drive and registry and
proceed to my SQL Server recovery. Are there any problems with this
approach?
Finally, are there other techniques that I should consider? Any
websites or newsgroup threads on this topic would be greatly
appreciated.
Thanks Much, Lane LesperanceI prefere the first approach. it's the databases you should back up, not the
server.
Part of a good recovery plan is to document everything, so you can put the
server back to its original configuration before applying your backup files.
you can use the 2nd one, but to me it will take longer, and you need to
really test it on a test box to make sure you can recover your data that
way.
Steve Lin
MCDBA
"Lane Lesperance" <llesperance@.cooperpower.com> wrote in message
news:66feb5c.0404051118.e0472bf@.posting.google.com...
> I have recently installed SQL Server 2000 on a newly acquired Windows
> 2003 server. The network admins also got Brightstor Agent for SQL
> Server to interface with Brightstor ARCserve Backup for Windows
> running on our backup server. I think I have a pretty good handle on
> how to setup the SQL Server backups using a combination of
> full/differential/transaction log backups to handle any recovery
> required for the SQL Server databases.
> What are the alternatives for backing up the Server itself for use in
> recovery? Two approaches come to mind.
> The first is not worry about backing up the server, in which case for
> a recovery, I would have to reinstall all the software and service
> packs to rebuild the environment. This would certainly require that I
> have fully documented what applications (Windows 2003 server, SQL
> Server, Outlook, Brightstor Agent, etc) and the install options that
> were chosen. The rebuild process for this could take some time, and
> there may be some issues that I haven't considered.
> The second is to fully backup the server including the registry. If
> everything were installed to the "C:\" drive, I could maybe get by
> with just backing up the "C:\" drive and the registry. I do have a
> weekend window where I could down the server to perform this task on a
> weekly basis. Then for recovery I could just install an operating
> system, restore from the backup of the "C:\" drive and registry and
> proceed to my SQL Server recovery. Are there any problems with this
> approach?
> Finally, are there other techniques that I should consider? Any
> websites or newsgroup threads on this topic would be greatly
> appreciated.
> Thanks Much, Lane Lesperance
2003 server. The network admins also got Brightstor Agent for SQL
Server to interface with Brightstor ARCserve Backup for Windows
running on our backup server. I think I have a pretty good handle on
how to setup the SQL Server backups using a combination of
full/differential/transaction log backups to handle any recovery
required for the SQL Server databases.
What are the alternatives for backing up the Server itself for use in
recovery? Two approaches come to mind.
The first is not worry about backing up the server, in which case for
a recovery, I would have to reinstall all the software and service
packs to rebuild the environment. This would certainly require that I
have fully documented what applications (Windows 2003 server, SQL
Server, Outlook, Brightstor Agent, etc) and the install options that
were chosen. The rebuild process for this could take some time, and
there may be some issues that I haven't considered.
The second is to fully backup the server including the registry. If
everything were installed to the "C:\" drive, I could maybe get by
with just backing up the "C:\" drive and the registry. I do have a
weekend window where I could down the server to perform this task on a
weekly basis. Then for recovery I could just install an operating
system, restore from the backup of the "C:\" drive and registry and
proceed to my SQL Server recovery. Are there any problems with this
approach?
Finally, are there other techniques that I should consider? Any
websites or newsgroup threads on this topic would be greatly
appreciated.
Thanks Much, Lane LesperanceI prefere the first approach. it's the databases you should back up, not the
server.
Part of a good recovery plan is to document everything, so you can put the
server back to its original configuration before applying your backup files.
you can use the 2nd one, but to me it will take longer, and you need to
really test it on a test box to make sure you can recover your data that
way.
Steve Lin
MCDBA
"Lane Lesperance" <llesperance@.cooperpower.com> wrote in message
news:66feb5c.0404051118.e0472bf@.posting.google.com...
> I have recently installed SQL Server 2000 on a newly acquired Windows
> 2003 server. The network admins also got Brightstor Agent for SQL
> Server to interface with Brightstor ARCserve Backup for Windows
> running on our backup server. I think I have a pretty good handle on
> how to setup the SQL Server backups using a combination of
> full/differential/transaction log backups to handle any recovery
> required for the SQL Server databases.
> What are the alternatives for backing up the Server itself for use in
> recovery? Two approaches come to mind.
> The first is not worry about backing up the server, in which case for
> a recovery, I would have to reinstall all the software and service
> packs to rebuild the environment. This would certainly require that I
> have fully documented what applications (Windows 2003 server, SQL
> Server, Outlook, Brightstor Agent, etc) and the install options that
> were chosen. The rebuild process for this could take some time, and
> there may be some issues that I haven't considered.
> The second is to fully backup the server including the registry. If
> everything were installed to the "C:\" drive, I could maybe get by
> with just backing up the "C:\" drive and the registry. I do have a
> weekend window where I could down the server to perform this task on a
> weekly basis. Then for recovery I could just install an operating
> system, restore from the backup of the "C:\" drive and registry and
> proceed to my SQL Server recovery. Are there any problems with this
> approach?
> Finally, are there other techniques that I should consider? Any
> websites or newsgroup threads on this topic would be greatly
> appreciated.
> Thanks Much, Lane Lesperance
订阅：
博文 (Atom)