Migrating to SQL 2005: nt4

Showing posts with label nt4. Show all posts

Friday, March 23, 2012

Minimum rights for SQL Agent

Hi,
Here is a problem:
SQL 2000 servers on Win 2000 servers in NT4 Domain
Security restrictions exclude Everyone group from all the shares and
registries.
The SQL agent and SQL Server service accounts should NOT be Local or Domain
Administrative privileges.
What are the minimum rights and registry access required for these accounts
in order to operate?
Any help is greatly appreciated.
Regards,
JDHi,
Do not run SQL Server and SQL Agent services as local system, local
administrator, or domain administrator accounts.
If your services starts based on above, most of the jobs which require an OS
level admin previlages will fail.
Eg:
1. Using XP_CMDSHELL wrting into hard drives, Registry read/write/delete...
2. SQL Agent connection to SQL Server with Admini prev.
Go thru the below link for more information on setting up security,
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/SP3SEC02.ASP
Thanks
Hari
MCDBA
"Bruce Rhoades" <bruce.rhoades@.gdsinc.com> wrote in message
news:eI8S4C0#DHA.2484@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Here is a problem:
> SQL 2000 servers on Win 2000 servers in NT4 Domain
> Security restrictions exclude Everyone group from all the shares and
> registries.
> The SQL agent and SQL Server service accounts should NOT be Local or
Domain
> Administrative privileges.
> What are the minimum rights and registry access required for these
accounts
> in order to operate?
> Any help is greatly appreciated.
> Regards,
> JD
>|||I disagree.
There are a large number of bad side effects if the SQL service account is
NOT a member of the local administrators group on a server. It needs to be
a domain account so you can access domain resources, but not necessarily a
domain admin. If the box is dedicated to SQL, then there is really no
seciruty risk. If not, then you are in for more problems anyway.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Bruce Rhoades" <bruce.rhoades@.gdsinc.com> wrote in message
news:eI8S4C0%23DHA.2484@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Here is a problem:
> SQL 2000 servers on Win 2000 servers in NT4 Domain
> Security restrictions exclude Everyone group from all the shares and
> registries.
> The SQL agent and SQL Server service accounts should NOT be Local or
Domain
> Administrative privileges.
> What are the minimum rights and registry access required for these
accounts
> in order to operate?
> Any help is greatly appreciated.
> Regards,
> JD
>|||See the BOL topic "Setting up Windows Services Accounts" for more details
on the permissions needed. If you're on a cluster then the startup
accounts need to be local admins. There are a subset of activities outlined
in the above topic that also require a local admin. Otherwise, the
account(s) just needs to be added to SQL Server as sysadmins and have the
permissions outlined in the referenced topic. If you set the account
through Enterprise Manager then all the permissions are automatically set
for you.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Wednesday, March 7, 2012

Migration from SQL7 to SQL2000

Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to move my databases over to a SQL 2000 Windows 2003 server. What is the best method. These are two different boxes. Any help is greatly appreciated.
Scott KeeganHave a look here:
http://msdn.microsoft.com/SQL/sqlmigratingdata/default.aspx
--
Andrew J. Kelly SQL MVP
"Scott Keegan" <Scott Keegan@.discussions.microsoft.com> wrote in message
news:3097FD7A-8F81-4BB9-A161-DE24A2FD40F6@.microsoft.com...
> Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to
move my databases over to a SQL 2000 Windows 2003 server. What is the best
method. These are two different boxes. Any help is greatly appreciated.
> Scott Keegan|||Scott
Install SQL Server on Widows 2003 and perfom RESTORE all users databases.
It might be a collation conflict but since SQL Server 2000 you can change it
even per column.
"Scott Keegan" <Scott Keegan@.discussions.microsoft.com> wrote in message
news:3097FD7A-8F81-4BB9-A161-DE24A2FD40F6@.microsoft.com...
> Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to
move my databases over to a SQL 2000 Windows 2003 server. What is the best
method. These are two different boxes. Any help is greatly appreciated.
> Scott Keegan|||Hi,
Migration from SQl 7 to SQl 2000 is straight forward, you can BACKUP and
RESTORE or use
sp_detach_db and sp_attach_db.
You could also probably also use the upgrade wizard .
Look into the below KB articles related to migration:
move the data via backup and restore
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304692
sp_detach_db and sp_attach_db
http://support.microsoft.com/support/kb/articles/q224/0/71.asp
one more option -- the copy database wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274463
PRB: User Logon and/or Permission Errors After Restoring Dump (Q168001)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q168001
Thanks
Hari
MCDBA
"Scott Keegan" <Scott Keegan@.discussions.microsoft.com> wrote in message
news:3097FD7A-8F81-4BB9-A161-DE24A2FD40F6@.microsoft.com...
> Hi, here is my delema, I have SQL 7 running on a NT4 box and I want to
move my databases over to a SQL 2000 Windows 2003 server. What is the best
method. These are two different boxes. Any help is greatly appreciated.
> Scott Keegan|||Is there a priority order on a where clause? Or does SQL check all of the
where clause conditions all of the time? I have a case where I can,
sometimes, hit non-numeric data in a column (caused by some bad
conversions). Right now we have the following where clause:
WHERE convert(integer, ?) BETWEEN convert(integer, low_street_num) AND
convert(integer, high_street_num)
AND (street_name = ? OR street_alias_name = ?)
AND city = ?
AND state_cd = ?
AND zip_cd LIKE ?
AND (juris_cd = ? OR juris_cd IS NULL)
AND (side = ? OR side = 'B')
AND status_cd = 'A'
AND (side = ? OR side = 'B')
AND status_cd = 'A'
I am wondering if we were to change to put the status_cd = 'A' first would
the query skip all entries whose status_cd is not 'A' and not even try to do
the convert(integer) statement at all? Or is it going to try to do the
convert(integer) regardless and my only solution is to make some routine to
fix the non-numeric data or adjust this sql to ensure the data is numeric
before trying to do the convert?
Edward Fultz
Sr. Software Engineer
Pamet Systems
Acton, Ma
www.pametsystems.com|||You cannot trust SQL Server to not hit the bad rows. Not even by pushing the filter inside a derived
table. I've been there. Put the stuff in a temp table and work against that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ed Fultz" <efultz@.yahoo.com> wrote in message news:O6blHRSWEHA.4056@.TK2MSFTNGP11.phx.gbl...
> Is there a priority order on a where clause? Or does SQL check all of the
> where clause conditions all of the time? I have a case where I can,
> sometimes, hit non-numeric data in a column (caused by some bad
> conversions). Right now we have the following where clause:
> WHERE convert(integer, ?) BETWEEN convert(integer, low_street_num) AND
> convert(integer, high_street_num)
> AND (street_name = ? OR street_alias_name = ?)
> AND city = ?
> AND state_cd = ?
> AND zip_cd LIKE ?
> AND (juris_cd = ? OR juris_cd IS NULL)
> AND (side = ? OR side = 'B')
> AND status_cd = 'A'
> AND (side = ? OR side = 'B')
> AND status_cd = 'A'
> I am wondering if we were to change to put the status_cd = 'A' first would
> the query skip all entries whose status_cd is not 'A' and not even try to do
> the convert(integer) statement at all? Or is it going to try to do the
> convert(integer) regardless and my only solution is to make some routine to
> fix the non-numeric data or adjust this sql to ensure the data is numeric
> before trying to do the convert?
>
> --
> Edward Fultz
> Sr. Software Engineer
> Pamet Systems
> Acton, Ma
> www.pametsystems.com
>|||You should be careful to test such a migration thoroughly:
We had a system running on MSSQL7 (MSDE) that we migrated
to MSSQL2000 Ent.Ed.
Restore finished fine, program seemded to run, but after
some days it crashed. Then nothing and then again. We
found out the following:
We built up SQL statements so string values were given as
char(65)+char(66)+...
Now, this sometimes produced queries as big as 8-9kB,
which MSSQL7 handled fine.
MSSQL2000, however, gave sql parse error. This shouldn't
be a problem until the length of the query reaches ~100kB.
Local Microsoft wanted to make this work badly, but
couldn't do it. We had to backtrack to MSSQL7.
>--Original Message--
>Hi, here is my delema, I have SQL 7 running on a NT4 box
and I want to move my databases over to a SQL 2000 Windows
2003 server. What is the best method. These are two
different boxes. Any help is greatly appreciated.
>Scott Keegan
>.
>

Friday, March 23, 2012

Minimum rights for SQL Agent

Wednesday, March 7, 2012

Migration from SQL7 to SQL2000

Migration from SQL7 to SQL2000

Migration from SQL7 to SQL2000

Migrating to SQL 2005

Blog Archive

About Me