Hi
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, th
e
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system accoun
t.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - bu
t
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
Showing posts with label directory. Show all posts
Showing posts with label directory. Show all posts
Sunday, March 11, 2012
Dumb permissions question
Hi
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex
<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
Brian Cryer
www.cryer.co.uk/brian
|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex
<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
Brian Cryer
www.cryer.co.uk/brian
|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegro ups.com...
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
Dumb permissions question
Hi
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> > Hi
> >
> > I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> > horror I notice that that the SQL data directory has permissions set
> > for:
> > Domain\Administrator (full accesss)
> > Domain\Administrators (full accesss)
> > Authenticated users (read,list, read). I guess this isn't a good idea
> > at all!
> >
> > What are the optimum permissions here (I can't seem to get a straight
> > answer). Do I set it for the SQL service to have full control only (at
> > the moment MSSQLSERVER service is logging on using
> > Domain\Administrator). Do I change this account? What about the other
> > SQL Server related services? Please also note I am also using Backup
> > Exec 9 to backup the databases.
> >
> > Any suggestions you may have will be greatly appreciated!
> >
> > Many thanks
> >
> > Alex
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
horror I notice that that the SQL data directory has permissions set
for:
Domain\Administrator (full accesss)
Domain\Administrators (full accesss)
Authenticated users (read,list, read). I guess this isn't a good idea
at all!
What are the optimum permissions here (I can't seem to get a straight
answer). Do I set it for the SQL service to have full control only (at
the moment MSSQLSERVER service is logging on using
Domain\Administrator). Do I change this account? What about the other
SQL Server related services? Please also note I am also using Backup
Exec 9 to backup the databases.
Any suggestions you may have will be greatly appreciated!
Many thanks
Alex<postings@.alexshirley.com> wrote in message
news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> Hi
> I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> horror I notice that that the SQL data directory has permissions set
> for:
> Domain\Administrator (full accesss)
> Domain\Administrators (full accesss)
> Authenticated users (read,list, read). I guess this isn't a good idea
> at all!
> What are the optimum permissions here (I can't seem to get a straight
> answer). Do I set it for the SQL service to have full control only (at
> the moment MSSQLSERVER service is logging on using
> Domain\Administrator). Do I change this account? What about the other
> SQL Server related services? Please also note I am also using Backup
> Exec 9 to backup the databases.
> Any suggestions you may have will be greatly appreciated!
> Many thanks
> Alex
On my SQL Server 2000 database running on Windows 2003 standard server, the
permissions on the SQL data directory are just for Domain\Administrators,
full access. The MSSQLServer service is set to use the local system account.
If your authenticated users have access then you should be able to revoke
that without problem.
I don't know where Backup Exec fits into the picture - I don't use it - but
it shouldn't be backing up the files directly so it shouldn't need any
permissions on the folder.
Hope this is useful.
--
Brian Cryer
www.cryer.co.uk/brian|||Great, thanks for your help Brian...!
Alex
-->
Brian Cryer wrote:
> <postings@.alexshirley.com> wrote in message
> news:1133285607.162678.51170@.g14g2000cwa.googlegroups.com...
> > Hi
> >
> > I'm running SQL Server 2000 on a Windows 2003 SBS server. Much to my
> > horror I notice that that the SQL data directory has permissions set
> > for:
> > Domain\Administrator (full accesss)
> > Domain\Administrators (full accesss)
> > Authenticated users (read,list, read). I guess this isn't a good idea
> > at all!
> >
> > What are the optimum permissions here (I can't seem to get a straight
> > answer). Do I set it for the SQL service to have full control only (at
> > the moment MSSQLSERVER service is logging on using
> > Domain\Administrator). Do I change this account? What about the other
> > SQL Server related services? Please also note I am also using Backup
> > Exec 9 to backup the databases.
> >
> > Any suggestions you may have will be greatly appreciated!
> >
> > Many thanks
> >
> > Alex
> On my SQL Server 2000 database running on Windows 2003 standard server, the
> permissions on the SQL data directory are just for Domain\Administrators,
> full access. The MSSQLServer service is set to use the local system account.
> If your authenticated users have access then you should be able to revoke
> that without problem.
> I don't know where Backup Exec fits into the picture - I don't use it - but
> it shouldn't be backing up the files directly so it shouldn't need any
> permissions on the folder.
> Hope this is useful.
> --
> Brian Cryer
> www.cryer.co.uk/brian
Friday, February 24, 2012
DTS_E_COLUMNDATAOVERFLOWDISKIOBUFFER Error
Hi! I'm a newbie and I'm trying to create a SSIS package which would loop in a directory of comma delimited text files.
Could anybody help? I'm having a problem when I run my package.
[Flat File Source [524]] Error: The column data for column "IndicatorGroupID" overflowed the disk I/O buffer.
[Flat File Source [524]] Error: An error occurred while processing file "\\192.168.0.47\Temp\detail-2864EGGPUSH-20060315.txt" on data row 1.
[DTS.Pipeline] Error: The PrimeOutput method on component "Flat File Source" (524) returned error code 0xC0202092. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Please help...
:)
Try directing all erroring rows into into an error sink using the error output from your flat file source so you can examine them later. I imagine you have some erroneous data in there.
--Jamie
|||Thanks! I've already found the error. You were correct, I was not able to filter my loop. As it happened, it looped through all the files in the directory, even through the unparsed ones.I only needed it to loop through the parsed ones. Thanks again!Friday, February 17, 2012
DTS Unspecified error
I have a DTS to transfer logins from one server to a another server. I have put the syslogins.dat file in the share directory. But this DTS is giving 'Unspecified Error'. Any help would be appreciated.
ThanksI would not try copying a dat file. Use tranfer SQL Objects.|||I guess, the dat file has nothing to do with this DTS. Because, the transfer logins task takes just the source and destination servers. I'm not sure how it transfers the logins and why it should give 'Unspecified error'.|||Are you saying you are not copying the dat? And the DTS is trying to transfer the logins?
What about permissions on both servers?|||I'm not copying the dat file.
What permissions should I check. I ran this DTS from Enterprise Manager. The logins are same in source and destination server.
I just tried to run it through a job and it failed with error 2147467259 (80004005).|||I just tried SQL Server Authentication instead of Windows Authentication and it still gives the same problem. I don't know what the heck this 'Unspecified error' means and this is driving me crazy|||If you have not tried this...
Change the task to something that should have no trouble completeing.
In other words does any work with that DTS?|||Yes. All the other DTS packages execute properly. I just tried 'create table','delete table', 'connection to excel'..etc. and everything just completed fine.
ThanksI would not try copying a dat file. Use tranfer SQL Objects.|||I guess, the dat file has nothing to do with this DTS. Because, the transfer logins task takes just the source and destination servers. I'm not sure how it transfers the logins and why it should give 'Unspecified error'.|||Are you saying you are not copying the dat? And the DTS is trying to transfer the logins?
What about permissions on both servers?|||I'm not copying the dat file.
What permissions should I check. I ran this DTS from Enterprise Manager. The logins are same in source and destination server.
I just tried to run it through a job and it failed with error 2147467259 (80004005).|||I just tried SQL Server Authentication instead of Windows Authentication and it still gives the same problem. I don't know what the heck this 'Unspecified error' means and this is driving me crazy|||If you have not tried this...
Change the task to something that should have no trouble completeing.
In other words does any work with that DTS?|||Yes. All the other DTS packages execute properly. I just tried 'create table','delete table', 'connection to excel'..etc. and everything just completed fine.
Subscribe to:
Posts (Atom)