aMSDeveloper (2/2/2011)

---

Hi

We have transaction replication from Primary to couple read-only servers. These read-only servers are used mainly for reporting. So, couple of questions:

1. I have read somewhere that if a...

you gave him read access to the database but he is trying to run a dbcc command which required elevated access.

what permission did you give him exactly? read-only or...

in my environment, in production, dev only get RO access if they can provide a business justification, which they can most of the time and approval from PM.

also, avoid using...

This would be based on group policy set by your network/domain admin.

have you tried setting the user's default database to the user database.

if they have access to modify other database then they could of inherited perm from another group.

run the upgrade advisor.

high availability, clustering, and database mirroring. even said.

if they don't believe, accidentally take down a prod server and watch them panic.

subcription expires by default. your replication setup script should make it never expire.

see: if_PostLink('http://www.sqlservercentral.com/Forums/FindPost164673.aspx')

check here

http://www.iopus.com/guides/winscheduler.htm

despag (1/28/2011)

---

We cannot make use of xp_cmdshell. It has been deleted from our extended procedures list for security reasons.

This is the error I get:

HResult 0x2, Level 16, State 1

Named...

What's the error?

from your bit of code, you are trying to make a call to a cmdline app, I don't see anywhere where you are making use of xp_cmdshell.

xp_cmdshell...

despag (1/26/2011)

---

While the follwing example is possible

:SETVAR DB_NAME_ASSIGN "TEST TEXT"

:SETVAR DB_NAME_TEXT "EXPECT INSERT OF DB_NAME_ASSIGN HERE: "

/*Get output*/

SELECT '$(DB_NAME_TEXT)' + '$(DB_NAME_ASSIGN)' AS OUTPUT

/* Delivers:

EXPECT INSERT OF DB_NAME_ASSIGN HERE: TEST...

require 4 parts for linked server, so it should be <server>.<database>.<schema>.<table>

sp_addlinkedserver 'serverA'

exec serverA...sp_who2 <= to test that your linked server work.

or install another instance of SQL on the same box. then you can run the upgrade advisor on this new instance to see what issue you might face when...

another thing you can do is:

1. backup the database like you are doing now

2. use windows task schedule to fire off a .bat file that will copy the files over...