Is there anything special needed to administer a 64 bit SQL Server ? We are
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..
There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tools
and functionality. If you could work with 2005, you might be happier.
Bob Hodgman
"Hassan" wrote:
> Is there anything special needed to administer a 64 bit SQL Server ? We are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>
Showing posts with label administer. Show all posts
Showing posts with label administer. Show all posts
Thursday, February 9, 2012
Anything specific about SQL 2000 64 bit ?
Is there anything special needed to administer a 64 bit SQL Server ? We are
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tool
s
and functionality. If you could work with 2005, you might be happier.
Bob Hodgman
"Hassan" wrote:
> Is there anything special needed to administer a 64 bit SQL Server ? We ar
e
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tool
s
and functionality. If you could work with 2005, you might be happier.
Bob Hodgman
"Hassan" wrote:
> Is there anything special needed to administer a 64 bit SQL Server ? We ar
e
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>
Anything specific about SQL 2000 64 bit ?
Is there anything special needed to administer a 64 bit SQL Server ? We are
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tools
and functionality. If you could work with 2005, you might be happier.
--
Bob Hodgman
"Hassan" wrote:
> Is there anything special needed to administer a 64 bit SQL Server ? We are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>
looking forward to deploying 64 bit on some servers and wanted to know if
there is anything I need to be aware of from an admin perspective,
installation,configuring, troubleshooting,etc..There is a doucment for 64 bit sql server, you can read it before moving to
64 bit platform.
Thanks, Regards, Vincent
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23QRBWFKmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> Is there anything special needed to administer a 64 bit SQL Server ? We
> are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>|||There are two pretty important things you should be aware of relating to
administering a 64-bit instance of SQL 2000.
1) You cannot run DTS packages on the 64-bit instance. You have to have a
32-bit instance that will run the DTS packages against the 64-bit instance
databases.
2) The administrative tools (Enterprise Manager and Query Analyzer, for
example) have no 64-bit editions. Again, you have to run these tools on a
32-bit machine and connect to your 64-bit instance.
If you are planning on running 64-bit SQL 2000, I'm guessing you have an
Itanium machine (I think the 64-bit SQL 2000 edition is only for Itaniums).
SQL 2005 has both Itanium and x64 versions, with a more complete set of tools
and functionality. If you could work with 2005, you might be happier.
--
Bob Hodgman
"Hassan" wrote:
> Is there anything special needed to administer a 64 bit SQL Server ? We are
> looking forward to deploying 64 bit on some servers and wanted to know if
> there is anything I need to be aware of from an admin perspective,
> installation,configuring, troubleshooting,etc..
>
>
Anyone who has permission to edit SPs can administer MS SQL server!
Hi!
One weekend a guy from development placed some sp_configure
instructions inside a procedure that is used by one of the jobs. So I
got this on the server:
Date Source Message
2004-06-06 16:17:27.16 spid91 Configuration option 'set working set
size' changed from 1 to 0. Run the RECONF
2004-06-06 16:17:27.25 spid91 Configuration option 'min memory per
query (KB)' changed from 4096 to 0. Run th
2004-06-06 16:17:27.36 spid91 Configuration option 'max worker
threads' changed from 255 to 0. Run the RECONF
2004-06-06 16:17:27.47 spid91 Configuration option 'max degree of
parallelism' changed from 2 to 0. Run the R
2004-06-06 16:17:27.58 spid91 Configuration option 'cost threshold for
parallelism' changed from 10 to 0. Run
2004-06-06 16:17:27.80 spid91 Configuration option 'remote access'
changed from 1 to 0. Run the RECONFIGURE s
2004-06-06 16:17:27.91 spid91 Configuration option 'remote proc trans'
changed from 1 to 0. Run the RECONFIGU
2004-06-06 16:17:28.02 spid91 Configuration option 'nested triggers'
changed from 1 to 0. Run the RECONFIGURE
This means that anyone who has permission to edit SPs can administer
MS SQL server! Such people can crush server, grant any rights to
themselves, etc. etc. Is there a way to block such activity?
Thanks.Hi,
I recommend you to configure the application specific jobs under the user
with only access
previlages to application tables.
If your job owner is "SA" or a user with SYSADMIN fixed role, you cant
restrict the access.
How to give the job owner:-
1. Doble click above the job
2. In the general tab, change the OWNER to a application user with less
previlages.
THis will restrict to run the adminstrative commands.
Other alternative is , Verify the procedures for admin commands before you
implement it to production. But you have spend time to search each
SP's which needs to be scheduled as a job.
Thanks
Hari
MCDBA
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0406080057.33c61cbc@.posting.google.com...
> Hi!
> One weekend a guy from development placed some sp_configure
> instructions inside a procedure that is used by one of the jobs. So I
> got this on the server:
> Date Source Message
> 2004-06-06 16:17:27.16 spid91 Configuration option 'set working set
> size' changed from 1 to 0. Run the RECONF
> 2004-06-06 16:17:27.25 spid91 Configuration option 'min memory per
> query (KB)' changed from 4096 to 0. Run th
> 2004-06-06 16:17:27.36 spid91 Configuration option 'max worker
> threads' changed from 255 to 0. Run the RECONF
> 2004-06-06 16:17:27.47 spid91 Configuration option 'max degree of
> parallelism' changed from 2 to 0. Run the R
> 2004-06-06 16:17:27.58 spid91 Configuration option 'cost threshold for
> parallelism' changed from 10 to 0. Run
> 2004-06-06 16:17:27.80 spid91 Configuration option 'remote access'
> changed from 1 to 0. Run the RECONFIGURE s
> 2004-06-06 16:17:27.91 spid91 Configuration option 'remote proc trans'
> changed from 1 to 0. Run the RECONFIGU
> 2004-06-06 16:17:28.02 spid91 Configuration option 'nested triggers'
> changed from 1 to 0. Run the RECONFIGURE
> This means that anyone who has permission to edit SPs can administer
> MS SQL server! Such people can crush server, grant any rights to
> themselves, etc. etc. Is there a way to block such activity?
> Thanks.
One weekend a guy from development placed some sp_configure
instructions inside a procedure that is used by one of the jobs. So I
got this on the server:
Date Source Message
2004-06-06 16:17:27.16 spid91 Configuration option 'set working set
size' changed from 1 to 0. Run the RECONF
2004-06-06 16:17:27.25 spid91 Configuration option 'min memory per
query (KB)' changed from 4096 to 0. Run th
2004-06-06 16:17:27.36 spid91 Configuration option 'max worker
threads' changed from 255 to 0. Run the RECONF
2004-06-06 16:17:27.47 spid91 Configuration option 'max degree of
parallelism' changed from 2 to 0. Run the R
2004-06-06 16:17:27.58 spid91 Configuration option 'cost threshold for
parallelism' changed from 10 to 0. Run
2004-06-06 16:17:27.80 spid91 Configuration option 'remote access'
changed from 1 to 0. Run the RECONFIGURE s
2004-06-06 16:17:27.91 spid91 Configuration option 'remote proc trans'
changed from 1 to 0. Run the RECONFIGU
2004-06-06 16:17:28.02 spid91 Configuration option 'nested triggers'
changed from 1 to 0. Run the RECONFIGURE
This means that anyone who has permission to edit SPs can administer
MS SQL server! Such people can crush server, grant any rights to
themselves, etc. etc. Is there a way to block such activity?
Thanks.Hi,
I recommend you to configure the application specific jobs under the user
with only access
previlages to application tables.
If your job owner is "SA" or a user with SYSADMIN fixed role, you cant
restrict the access.
How to give the job owner:-
1. Doble click above the job
2. In the general tab, change the OWNER to a application user with less
previlages.
THis will restrict to run the adminstrative commands.
Other alternative is , Verify the procedures for admin commands before you
implement it to production. But you have spend time to search each
SP's which needs to be scheduled as a job.
Thanks
Hari
MCDBA
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0406080057.33c61cbc@.posting.google.com...
> Hi!
> One weekend a guy from development placed some sp_configure
> instructions inside a procedure that is used by one of the jobs. So I
> got this on the server:
> Date Source Message
> 2004-06-06 16:17:27.16 spid91 Configuration option 'set working set
> size' changed from 1 to 0. Run the RECONF
> 2004-06-06 16:17:27.25 spid91 Configuration option 'min memory per
> query (KB)' changed from 4096 to 0. Run th
> 2004-06-06 16:17:27.36 spid91 Configuration option 'max worker
> threads' changed from 255 to 0. Run the RECONF
> 2004-06-06 16:17:27.47 spid91 Configuration option 'max degree of
> parallelism' changed from 2 to 0. Run the R
> 2004-06-06 16:17:27.58 spid91 Configuration option 'cost threshold for
> parallelism' changed from 10 to 0. Run
> 2004-06-06 16:17:27.80 spid91 Configuration option 'remote access'
> changed from 1 to 0. Run the RECONFIGURE s
> 2004-06-06 16:17:27.91 spid91 Configuration option 'remote proc trans'
> changed from 1 to 0. Run the RECONFIGU
> 2004-06-06 16:17:28.02 spid91 Configuration option 'nested triggers'
> changed from 1 to 0. Run the RECONFIGURE
> This means that anyone who has permission to edit SPs can administer
> MS SQL server! Such people can crush server, grant any rights to
> themselves, etc. etc. Is there a way to block such activity?
> Thanks.
Subscribe to:
Posts (Atom)