Can i put sql sever on my computer and have the db on a mapped drive on our company network?
Mapped Drive -No;
Logical Drive (LUN) -Yes
Does your network have a NAS or SAN? (That would work.) Just mapping to a file server does not.
sql
Showing posts with label company. Show all posts
Showing posts with label company. Show all posts
Wednesday, March 21, 2012
Friday, February 24, 2012
Local Groups and Access.
I'm trying to prototype some reports, and having difficulties granting access
to users, connecting to my LocalHost.
I work for a company that uses LDAP.
I have RS running on my LocalHost, and would like to grant access to users
to Report Manager so they can render reports.
In the Computer management > Local Users & Groups > Groups: I see Users,
Guests. Can I add these group(s) in the Report Manager using 'New Role
Assignment', and assign a Role, like Browser, then will a unknown user be
able to visit the site and render some reports.
Thanks,
rwiethornI'm getting closer, the user can see the reportmanger but cannot run a report.
Here is what I did:
I created a user on my local machine, call him Bob. I then created a group
on my local machine, called ReportViewers, and added Bob to the group. I then
added the group to ReportManager, gave it a Content Manager role, and for
'Configure site-wide security', System Role Assignments, assigned the group
as System Users.
However, they can not view the report. Ther error points to the Datasource.
The Datasource is supposed to pull a recordset from the AdventureWorks
catalog. It uses the SA account. When I look at the datasource in the
ReportManager, the credentials are saved (user name: sa and its password).
So why would that not return the results from the AdventureWorks database?
Do I neeed to add the local group also to the Database and catalog?
Do I need to add the IUSR_machine account to the database?
Do I need to add the ASPNET account to the group?
All help is appreciated,
thanks, confused,
rwiethorn
"rwiethorn" wrote:
> I'm trying to prototype some reports, and having difficulties granting access
> to users, connecting to my LocalHost.
> I work for a company that uses LDAP.
> I have RS running on my LocalHost, and would like to grant access to users
> to Report Manager so they can render reports.
> In the Computer management > Local Users & Groups > Groups: I see Users,
> Guests. Can I add these group(s) in the Report Manager using 'New Role
> Assignment', and assign a Role, like Browser, then will a unknown user be
> able to visit the site and render some reports.
> Thanks,
> rwiethorn
to users, connecting to my LocalHost.
I work for a company that uses LDAP.
I have RS running on my LocalHost, and would like to grant access to users
to Report Manager so they can render reports.
In the Computer management > Local Users & Groups > Groups: I see Users,
Guests. Can I add these group(s) in the Report Manager using 'New Role
Assignment', and assign a Role, like Browser, then will a unknown user be
able to visit the site and render some reports.
Thanks,
rwiethornI'm getting closer, the user can see the reportmanger but cannot run a report.
Here is what I did:
I created a user on my local machine, call him Bob. I then created a group
on my local machine, called ReportViewers, and added Bob to the group. I then
added the group to ReportManager, gave it a Content Manager role, and for
'Configure site-wide security', System Role Assignments, assigned the group
as System Users.
However, they can not view the report. Ther error points to the Datasource.
The Datasource is supposed to pull a recordset from the AdventureWorks
catalog. It uses the SA account. When I look at the datasource in the
ReportManager, the credentials are saved (user name: sa and its password).
So why would that not return the results from the AdventureWorks database?
Do I neeed to add the local group also to the Database and catalog?
Do I need to add the IUSR_machine account to the database?
Do I need to add the ASPNET account to the group?
All help is appreciated,
thanks, confused,
rwiethorn
"rwiethorn" wrote:
> I'm trying to prototype some reports, and having difficulties granting access
> to users, connecting to my LocalHost.
> I work for a company that uses LDAP.
> I have RS running on my LocalHost, and would like to grant access to users
> to Report Manager so they can render reports.
> In the Computer management > Local Users & Groups > Groups: I see Users,
> Guests. Can I add these group(s) in the Report Manager using 'New Role
> Assignment', and assign a Role, like Browser, then will a unknown user be
> able to visit the site and render some reports.
> Thanks,
> rwiethorn
Monday, February 20, 2012
Local admin needed for DBA??
Its been proposed at my company that the DBA's no longer have WINNT Admin
rights to the SQL Servers. I don't know that Im totally opposed to it as long
as I can get my job done. What things would a DBA not be able to do if he was
not an Admin on the box? The two things Im really not sure of are replication
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisRFull Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR|||This is a multi-part message in MIME format.
--080001010205040905060400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:
>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps to
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>
--080001010205040905060400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Plus you wouldn't be able to start & stop services on the SQL
boxes (something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.<br>
<br>
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Hilary Cotter wrote:
<blockquote cite="midee8xk9xFGHA.532@.TK2MSFTNGP15.phx.gbl" type="cite">
<pre wrap="">Full Text Search is hosed.
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://support.microsoft.com/kb/295051/en-us</a>">http://support.microsoft.com/kb/295051/en-us">http://support.microsoft.com/kb/295051/en-us</a>
There are encryption problems
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://support.microsoft.com/kb/314636/en-us</a>">http://support.microsoft.com/kb/314636/en-us">http://support.microsoft.com/kb/314636/en-us</a>
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
</pre>
</blockquote>
</body>
</html>
--080001010205040905060400--
rights to the SQL Servers. I don't know that Im totally opposed to it as long
as I can get my job done. What things would a DBA not be able to do if he was
not an Admin on the box? The two things Im really not sure of are replication
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisRFull Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR|||This is a multi-part message in MIME format.
--080001010205040905060400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:
>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps to
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>
--080001010205040905060400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Plus you wouldn't be able to start & stop services on the SQL
boxes (something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.<br>
<br>
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Hilary Cotter wrote:
<blockquote cite="midee8xk9xFGHA.532@.TK2MSFTNGP15.phx.gbl" type="cite">
<pre wrap="">Full Text Search is hosed.
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://support.microsoft.com/kb/295051/en-us</a>">http://support.microsoft.com/kb/295051/en-us">http://support.microsoft.com/kb/295051/en-us</a>
There are encryption problems
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://support.microsoft.com/kb/314636/en-us</a>">http://support.microsoft.com/kb/314636/en-us">http://support.microsoft.com/kb/314636/en-us</a>
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
</pre>
</blockquote>
</body>
</html>
--080001010205040905060400--
Local admin needed for DBA??
Its been proposed at my company that the DBA's no longer have WINNT Admin
rights to the SQL Servers. I don't know that Im totally opposed to it as lon
g
as I can get my job done. What things would a DBA not be able to do if he wa
s
not an Admin on the box? The two things Im really not sure of are replicatio
n
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisRFull Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR|||Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:
>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps t
o
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>
rights to the SQL Servers. I don't know that Im totally opposed to it as lon
g
as I can get my job done. What things would a DBA not be able to do if he wa
s
not an Admin on the box? The two things Im really not sure of are replicatio
n
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisRFull Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR|||Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:
>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps t
o
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>
Local admin needed for DBA??
Its been proposed at my company that the DBA's no longer have WINNT Admin
rights to the SQL Servers. I don't know that Im totally opposed to it as long
as I can get my job done. What things would a DBA not be able to do if he was
not an Admin on the box? The two things Im really not sure of are replication
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisR
Full Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR
|||Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:
>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps to
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>
rights to the SQL Servers. I don't know that Im totally opposed to it as long
as I can get my job done. What things would a DBA not be able to do if he was
not an Admin on the box? The two things Im really not sure of are replication
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisR
Full Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR
|||Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:
>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps to
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>
local access to replication logs (was "Does anyone have a clever solution")
We have a SQL Server database that runs a website on our server, however the company that we are running the website for requested that they have a replicated local version at their business. Everything is working fine.
However they have requested that they have access to the replication logs. They want to have the details of the recent replication details so they can see if changes they have made on their side has been transferre across successfully they also want a table with all the details in of the changes that have ever happened. Can anyone suggest a good way of doing this?
Thanks EdStructure changes or data cheanges.
If they're changing the structure I think it's a much bigger deal...|||I've had to do the same thing at my company, what I did was put triggers on the replicated tables (on the subscriber side). The triggers wrote all insert/updates into a "Log" table which our customer could access throgh Crystal reports.|||Thanks I thik I'll go with the trigger solution, Thanks Ed
However they have requested that they have access to the replication logs. They want to have the details of the recent replication details so they can see if changes they have made on their side has been transferre across successfully they also want a table with all the details in of the changes that have ever happened. Can anyone suggest a good way of doing this?
Thanks EdStructure changes or data cheanges.
If they're changing the structure I think it's a much bigger deal...|||I've had to do the same thing at my company, what I did was put triggers on the replicated tables (on the subscriber side). The triggers wrote all insert/updates into a "Log" table which our customer could access throgh Crystal reports.|||Thanks I thik I'll go with the trigger solution, Thanks Ed
Subscribe to:
Posts (Atom)