Please Help me ->Bruce Loehle-Conger

Hello Bruce, my name's Carlos and i have a big problem, i have two reports
the firtone is the "master report", and this jump to a second report, but
when the second report show, the parameter bar is hidde, and when i back to
the master report, the parameter bar is also hidden.
Could yuo help me please.
Thanks.I had the same problem. I found a work around, but probably not the best way.
Right now I just used the "jump to url" under navigation and put: ="?" &
Globals!ReportFolder & "/report_name"
"Carlos López." wrote:
> Hello Bruce, my name's Carlos and i have a big problem, i have two reports
> the firtone is the "master report", and this jump to a second report, but
> when the second report show, the parameter bar is hidde, and when i back to
> the master report, the parameter bar is also hidden.
> Could yuo help me please.
> Thanks.|||Thanks scraejtp, i will try this and i will tell you the result.
I found a blog where someone suggest to use the parameter rc:parameter=true
in the query string, but don't work for me,
"scraejtp" wrote:
> I had the same problem. I found a work around, but probably not the best way.
> Right now I just used the "jump to url" under navigation and put: ="?" &
> Globals!ReportFolder & "/report_name"
>
> "Carlos López." wrote:
> > Hello Bruce, my name's Carlos and i have a big problem, i have two reports
> > the firtone is the "master report", and this jump to a second report, but
> > when the second report show, the parameter bar is hidde, and when i back to
> > the master report, the parameter bar is also hidden.
> >
> > Could yuo help me please.
> >
> > Thanks.

Please advise re. restoring master/msdb on different server

I'm sure restoring master/msdb on the same server should
be no issue. But restoring on separate hardware might
have these issues (if you know others please tell me):
1: File path (drive letter, file path) different for the
location of the database on the replacement server;
2: Security issues. The separate Windows installation is
sure to have different SID, and since SQL Server security
is tightly integrated with Windows security, what might be
broken, what will the restore take care of, and what needs
to be manually fixed up-and how? (BTW, our installation
uses mixed mode security)
Regarding issue 1: I have experienced that restoring over
an existing database causes the file locations to be
automatically fixed up by the restore, taking the file
locations from the database being overwritten rather than
the locations saved in the backup. Will this work for
master/msdb?
I don't know what to expect regarding issue #2.
Any help appreciated! Thanks!Hi
Try the following:
http://support.microsoft.com/defaul...kb;EN-US;224071
John
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
> I'm sure restoring master/msdb on the same server should
> be no issue. But restoring on separate hardware might
> have these issues (if you know others please tell me):
> 1: File path (drive letter, file path) different for the
> location of the database on the replacement server;
> 2: Security issues. The separate Windows installation is
> sure to have different SID, and since SQL Server security
> is tightly integrated with Windows security, what might be
> broken, what will the restore take care of, and what needs
> to be manually fixed up-and how? (BTW, our installation
> uses mixed mode security)
> Regarding issue 1: I have experienced that restoring over
> an existing database causes the file locations to be
> automatically fixed up by the restore, taking the file
> locations from the database being overwritten rather than
> the locations saved in the backup. Will this work for
> master/msdb?
> I don't know what to expect regarding issue #2.
> Any help appreciated! Thanks!
>|||OK, thank you, these seem to indicate my concerns were
right.
However, all the documentation you pointed me at seems to
assume the original databases are operational; they are
read, or even modified, by these procedures, and
transferred as operational databases.
I need procedures for FAILED systems, i.e., only the
backups are available, not the databases themselves.
Any more help, anyone?
Thanks!

>--Original Message--
>Hi
>Try the following:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;224071
>John
>"Scott" <anonymous@.discussions.microsoft.com> wrote in
message
>news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
the
is
security
be
needs
over
than
>
>.
>|||Hi
I have never tried it, but if you can restore the database into another
database then you can get the files, so you can then follow the procedure.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
> OK, thank you, these seem to indicate my concerns were
> right.
> However, all the documentation you pointed me at seems to
> assume the original databases are operational; they are
> read, or even modified, by these procedures, and
> transferred as operational databases.
> I need procedures for FAILED systems, i.e., only the
> backups are available, not the databases themselves.
> Any more help, anyone?
> Thanks!
>
>
> US;224071
> message
> the
> is
> security
> be
> needs
> over
> than|||!!!
Yeah, that sound right. Ahh, Friday. Sorry for my fuzzy
head. And THANKS for your response.
Don't know the real state of our failed server, so I don't
know if we'll really have to do this. If we DO, I'll
respond and let you know.
Thanks again!
--Scott

>--Original Message--
>Hi
>I have never tried it, but if you can restore the
database into another
>database then you can get the files, so you can then
follow the procedure.
>John
><anonymous@.discussions.microsoft.com> wrote in message
>news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
to
should
might
me):
installation
might
installation
file
for
>
>.
>

Please advise re. restoring master/msdb on different server

I'm sure restoring master/msdb on the same server should
be no issue. But restoring on separate hardware might
have these issues (if you know others please tell me):
1: File path (drive letter, file path) different for the
location of the database on the replacement server;
2: Security issues. The separate Windows installation is
sure to have different SID, and since SQL Server security
is tightly integrated with Windows security, what might be
broken, what will the restore take care of, and what needs
to be manually fixed up-and how? (BTW, our installation
uses mixed mode security)
Regarding issue 1: I have experienced that restoring over
an existing database causes the file locations to be
automatically fixed up by the restore, taking the file
locations from the database being overwritten rather than
the locations saved in the backup. Will this work for
master/msdb?
I don't know what to expect regarding issue #2.
Any help appreciated! Thanks!Hi
Try the following:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071
John
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
> I'm sure restoring master/msdb on the same server should
> be no issue. But restoring on separate hardware might
> have these issues (if you know others please tell me):
> 1: File path (drive letter, file path) different for the
> location of the database on the replacement server;
> 2: Security issues. The separate Windows installation is
> sure to have different SID, and since SQL Server security
> is tightly integrated with Windows security, what might be
> broken, what will the restore take care of, and what needs
> to be manually fixed up-and how? (BTW, our installation
> uses mixed mode security)
> Regarding issue 1: I have experienced that restoring over
> an existing database causes the file locations to be
> automatically fixed up by the restore, taking the file
> locations from the database being overwritten rather than
> the locations saved in the backup. Will this work for
> master/msdb?
> I don't know what to expect regarding issue #2.
> Any help appreciated! Thanks!
>|||OK, thank you, these seem to indicate my concerns were
right.
However, all the documentation you pointed me at seems to
assume the original databases are operational; they are
read, or even modified, by these procedures, and
transferred as operational databases.
I need procedures for FAILED systems, i.e., only the
backups are available, not the databases themselves.
Any more help, anyone?
Thanks!
>--Original Message--
>Hi
>Try the following:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;224071
>John
>"Scott" <anonymous@.discussions.microsoft.com> wrote in
message
>news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
>> I'm sure restoring master/msdb on the same server should
>> be no issue. But restoring on separate hardware might
>> have these issues (if you know others please tell me):
>> 1: File path (drive letter, file path) different for
the
>> location of the database on the replacement server;
>> 2: Security issues. The separate Windows installation
is
>> sure to have different SID, and since SQL Server
security
>> is tightly integrated with Windows security, what might
be
>> broken, what will the restore take care of, and what
needs
>> to be manually fixed up-and how? (BTW, our installation
>> uses mixed mode security)
>> Regarding issue 1: I have experienced that restoring
over
>> an existing database causes the file locations to be
>> automatically fixed up by the restore, taking the file
>> locations from the database being overwritten rather
than
>> the locations saved in the backup. Will this work for
>> master/msdb?
>> I don't know what to expect regarding issue #2.
>> Any help appreciated! Thanks!
>
>.
>|||Hi
I have never tried it, but if you can restore the database into another
database then you can get the files, so you can then follow the procedure.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
> OK, thank you, these seem to indicate my concerns were
> right.
> However, all the documentation you pointed me at seems to
> assume the original databases are operational; they are
> read, or even modified, by these procedures, and
> transferred as operational databases.
> I need procedures for FAILED systems, i.e., only the
> backups are available, not the databases themselves.
> Any more help, anyone?
> Thanks!
>
> >--Original Message--
> >Hi
> >
> >Try the following:
> >http://support.microsoft.com/default.aspx?scid=kb;EN-
> US;224071
> >
> >John
> >
> >"Scott" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
> >> I'm sure restoring master/msdb on the same server should
> >> be no issue. But restoring on separate hardware might
> >> have these issues (if you know others please tell me):
> >>
> >> 1: File path (drive letter, file path) different for
> the
> >> location of the database on the replacement server;
> >>
> >> 2: Security issues. The separate Windows installation
> is
> >> sure to have different SID, and since SQL Server
> security
> >> is tightly integrated with Windows security, what might
> be
> >> broken, what will the restore take care of, and what
> needs
> >> to be manually fixed up-and how? (BTW, our installation
> >> uses mixed mode security)
> >>
> >> Regarding issue 1: I have experienced that restoring
> over
> >> an existing database causes the file locations to be
> >> automatically fixed up by the restore, taking the file
> >> locations from the database being overwritten rather
> than
> >> the locations saved in the backup. Will this work for
> >> master/msdb?
> >>
> >> I don't know what to expect regarding issue #2.
> >>
> >> Any help appreciated! Thanks!
> >>
> >
> >
> >.
> >|||!!!
Yeah, that sound right. Ahh, Friday. Sorry for my fuzzy
head. And THANKS for your response.
Don't know the real state of our failed server, so I don't
know if we'll really have to do this. If we DO, I'll
respond and let you know.
Thanks again!
--Scott
>--Original Message--
>Hi
>I have never tried it, but if you can restore the
database into another
>database then you can get the files, so you can then
follow the procedure.
>John
><anonymous@.discussions.microsoft.com> wrote in message
>news:357a01c3fd86$69962b40$a001280a@.phx.gbl...
>> OK, thank you, these seem to indicate my concerns were
>> right.
>> However, all the documentation you pointed me at seems
to
>> assume the original databases are operational; they are
>> read, or even modified, by these procedures, and
>> transferred as operational databases.
>> I need procedures for FAILED systems, i.e., only the
>> backups are available, not the databases themselves.
>> Any more help, anyone?
>> Thanks!
>>
>> >--Original Message--
>> >Hi
>> >
>> >Try the following:
>> >http://support.microsoft.com/default.aspx?scid=kb;EN-
>> US;224071
>> >
>> >John
>> >
>> >"Scott" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:094d01c3fd71$ab484d80$a601280a@.phx.gbl...
>> >> I'm sure restoring master/msdb on the same server
should
>> >> be no issue. But restoring on separate hardware
might
>> >> have these issues (if you know others please tell
me):
>> >>
>> >> 1: File path (drive letter, file path) different for
>> the
>> >> location of the database on the replacement server;
>> >>
>> >> 2: Security issues. The separate Windows
installation
>> is
>> >> sure to have different SID, and since SQL Server
>> security
>> >> is tightly integrated with Windows security, what
might
>> be
>> >> broken, what will the restore take care of, and what
>> needs
>> >> to be manually fixed up-and how? (BTW, our
installation
>> >> uses mixed mode security)
>> >>
>> >> Regarding issue 1: I have experienced that restoring
>> over
>> >> an existing database causes the file locations to be
>> >> automatically fixed up by the restore, taking the
file
>> >> locations from the database being overwritten rather
>> than
>> >> the locations saved in the backup. Will this work
for
>> >> master/msdb?
>> >>
>> >> I don't know what to expect regarding issue #2.
>> >>
>> >> Any help appreciated! Thanks!
>> >>
>> >
>> >
>> >.
>> >
>
>.
>

plan for box upgrade

sql2k sp3
Im going to be moving sql from one box to a newer one
with better hardware today. This is my plan:
Restore a backup of Master and MSDB onto the new box.
Detach and attach the user db's.
Ive used detach and attach but never in this scenario.
Does anyone see a problem with this?
TIA, ChrisYour plan is perfect, only thing is that the restored
master database will still have entries for user
databases, even if they don't exist on new server yet. I
believe you can get rid of them by issuing drop database
command.
Then start attachig user databases, and then msdb.
hth.
>--Original Message--
>sql2k sp3
>Im going to be moving sql from one box to a newer one
>with better hardware today. This is my plan:
>Restore a backup of Master and MSDB onto the new box.
>Detach and attach the user db's.
>Ive used detach and attach but never in this scenario.
>Does anyone see a problem with this?
>TIA, Chris
>
>.
>|||My plan wasnt to detach and attach msdb at all. It was to
backup/ restore it. Will this still work?
>--Original Message--
>Your plan is perfect, only thing is that the restored
>master database will still have entries for user
>databases, even if they don't exist on new server yet. I
>believe you can get rid of them by issuing drop database
>command.
>Then start attachig user databases, and then msdb.
>
>hth.
>>--Original Message--
>>sql2k sp3
>>Im going to be moving sql from one box to a newer one
>>with better hardware today. This is my plan:
>>Restore a backup of Master and MSDB onto the new box.
>>Detach and attach the user db's.
>>Ive used detach and attach but never in this scenario.
>>Does anyone see a problem with this?
>>TIA, Chris
>>
>>.
>.
>|||you can backup/restore or attach/detach msdb database. or
just rename new mdf and ldf files for msdb on new server
(just for backup) and then copy original mdf/ldf files in
their place when the sql server is not running.
You can do same for master database as well, if you don't
want to use backup/restore.
hth.
>--Original Message--
>My plan wasnt to detach and attach msdb at all. It was to
>backup/ restore it. Will this still work?
>
>>--Original Message--
>>Your plan is perfect, only thing is that the restored
>>master database will still have entries for user
>>databases, even if they don't exist on new server yet. I
>>believe you can get rid of them by issuing drop database
>>command.
>>Then start attachig user databases, and then msdb.
>>
>>hth.
>>--Original Message--
>>sql2k sp3
>>Im going to be moving sql from one box to a newer one
>>with better hardware today. This is my plan:
>>Restore a backup of Master and MSDB onto the new box.
>>Detach and attach the user db's.
>>Ive used detach and attach but never in this scenario.
>>Does anyone see a problem with this?
>>TIA, Chris
>>
>>.
>>.
>.
>

Place a triiger on sysprocesses table

Hi,
I have to set up a trigger on master database sysprocesses, but when I
execute the trigger, I got an error, says "CREATE TRIGGER permission denied
on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody help
me on this?
ThanksYou cannot create triggers on system tables. If you post what you want to ac
hieve, perhaps someone
can reply with a suggestion.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> Hi,
> I have to set up a trigger on master database sysprocesses, but when I
> execute the trigger, I got an error, says "CREATE TRIGGER permission denie
d
> on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody he
lp
> me on this?
> Thanks|||Triggers are not supported on system tables. What exactly are you trying to
achieve?
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> Hi,
> I have to set up a trigger on master database sysprocesses, but when I
> execute the trigger, I got an error, says "CREATE TRIGGER permission
denied
> on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody
help
> me on this?
> Thanks|||I need to audit the sysprocesses table, and if somebody is using MS Access t
o
modify any data on the server, then send out Email alert and kill the
process. Any idea how can I do this without using a trigger?
Thanks.
"Narayana Vyas Kondreddi" wrote:

> Triggers are not supported on system tables. What exactly are you trying t
o
> achieve?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
> news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> denied
> help
>
>|||Just because they connect to the server doesn't mean they are going to
change data. I would suggest you do not allow those particular logins
access the database. Why give them access if you are trying to prevent
it?
If OTOH you are saying that the user requires access to the database
from certain applications, but not others, you might consider using
Application Roles (see Application Roles and sp_addapprole in BOL for
more information).
David Gugick
Imceda Software
www.imceda.com|||This is for SOX audit. I have to provide a way to prove that if anyone did
get into certain data without using the application front end, we can catch
it.
"David Gugick" wrote:

> Just because they connect to the server doesn't mean they are going to
> change data. I would suggest you do not allow those particular logins
> access the database. Why give them access if you are trying to prevent
> it?
> If OTOH you are saying that the user requires access to the database
> from certain applications, but not others, you might consider using
> Application Roles (see Application Roles and sp_addapprole in BOL for
> more information).
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||As David said, look at application roles. If that's not an option, take a
look at APP_NAME() and USER_NAME and few other similar functions to find the
current user name and application name (session based)...
Example:
DECLARE @.CurrentApp varchar(35)
SET @.CurrentApp = APP_NAME()
IF @.CurrentApp <> 'MS SQL Query Analyzer'
PRINT 'This process was not started by a SQL Query Analyzer query session.'
Sasan Saidi, MSc in cs
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Hong Wang" wrote:
[vbcol=seagreen]
> This is for SOX audit. I have to provide a way to prove that if anyone did
> get into certain data without using the application front end, we can catc
h
> it.
> "David Gugick" wrote:
>

Place a triiger on sysprocesses table

Hi,
I have to set up a trigger on master database sysprocesses, but when I
execute the trigger, I got an error, says "CREATE TRIGGER permission denied
on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody help
me on this?
ThanksYou cannot create triggers on system tables. If you post what you want to achieve, perhaps someone
can reply with a suggestion.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> Hi,
> I have to set up a trigger on master database sysprocesses, but when I
> execute the trigger, I got an error, says "CREATE TRIGGER permission denied
> on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody help
> me on this?
> Thanks|||Triggers are not supported on system tables. What exactly are you trying to
achieve?
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> Hi,
> I have to set up a trigger on master database sysprocesses, but when I
> execute the trigger, I got an error, says "CREATE TRIGGER permission
denied
> on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody
help
> me on this?
> Thanks|||I need to audit the sysprocesses table, and if somebody is using MS Access to
modify any data on the server, then send out Email alert and kill the
process. Any idea how can I do this without using a trigger?
Thanks.
"Narayana Vyas Kondreddi" wrote:
> Triggers are not supported on system tables. What exactly are you trying to
> achieve?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
> news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> > Hi,
> >
> > I have to set up a trigger on master database sysprocesses, but when I
> > execute the trigger, I got an error, says "CREATE TRIGGER permission
> denied
> > on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody
> help
> > me on this?
> >
> > Thanks
>
>|||Just because they connect to the server doesn't mean they are going to
change data. I would suggest you do not allow those particular logins
access the database. Why give them access if you are trying to prevent
it?
If OTOH you are saying that the user requires access to the database
from certain applications, but not others, you might consider using
Application Roles (see Application Roles and sp_addapprole in BOL for
more information).
David Gugick
Imceda Software
www.imceda.com|||This is for SOX audit. I have to provide a way to prove that if anyone did
get into certain data without using the application front end, we can catch
it.
"David Gugick" wrote:
> Just because they connect to the server doesn't mean they are going to
> change data. I would suggest you do not allow those particular logins
> access the database. Why give them access if you are trying to prevent
> it?
> If OTOH you are saying that the user requires access to the database
> from certain applications, but not others, you might consider using
> Application Roles (see Application Roles and sp_addapprole in BOL for
> more information).
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||As David said, look at application roles. If that's not an option, take a
look at APP_NAME() and USER_NAME and few other similar functions to find the
current user name and application name (session based)...
Example:
DECLARE @.CurrentApp varchar(35)
SET @.CurrentApp = APP_NAME()
IF @.CurrentApp <> 'MS SQL Query Analyzer'
PRINT 'This process was not started by a SQL Query Analyzer query session.'
--
Sasan Saidi, MSc in cs
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Hong Wang" wrote:
> This is for SOX audit. I have to provide a way to prove that if anyone did
> get into certain data without using the application front end, we can catch
> it.
> "David Gugick" wrote:
> > Just because they connect to the server doesn't mean they are going to
> > change data. I would suggest you do not allow those particular logins
> > access the database. Why give them access if you are trying to prevent
> > it?
> >
> > If OTOH you are saying that the user requires access to the database
> > from certain applications, but not others, you might consider using
> > Application Roles (see Application Roles and sp_addapprole in BOL for
> > more information).
> >
> >
> > --
> > David Gugick
> > Imceda Software
> > www.imceda.com
> >
> >

Place a triiger on sysprocesses table

Hi,
I have to set up a trigger on master database sysprocesses, but when I
execute the trigger, I got an error, says "CREATE TRIGGER permission denied
on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody help
me on this?
Thanks
You cannot create triggers on system tables. If you post what you want to achieve, perhaps someone
can reply with a suggestion.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> Hi,
> I have to set up a trigger on master database sysprocesses, but when I
> execute the trigger, I got an error, says "CREATE TRIGGER permission denied
> on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody help
> me on this?
> Thanks
|||Triggers are not supported on system tables. What exactly are you trying to
achieve?
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> Hi,
> I have to set up a trigger on master database sysprocesses, but when I
> execute the trigger, I got an error, says "CREATE TRIGGER permission
denied
> on object 'sysprocesses', database 'master', owner 'dbo'." Can anybody
help
> me on this?
> Thanks
|||I need to audit the sysprocesses table, and if somebody is using MS Access to
modify any data on the server, then send out Email alert and kill the
process. Any idea how can I do this without using a trigger?
Thanks.
"Narayana Vyas Kondreddi" wrote:

> Triggers are not supported on system tables. What exactly are you trying to
> achieve?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Hong Wang" <HongWang@.discussions.microsoft.com> wrote in message
> news:7515D739-3472-4D43-9D81-80E1C0744893@.microsoft.com...
> denied
> help
>
>
|||Just because they connect to the server doesn't mean they are going to
change data. I would suggest you do not allow those particular logins
access the database. Why give them access if you are trying to prevent
it?
If OTOH you are saying that the user requires access to the database
from certain applications, but not others, you might consider using
Application Roles (see Application Roles and sp_addapprole in BOL for
more information).
David Gugick
Imceda Software
www.imceda.com
|||This is for SOX audit. I have to provide a way to prove that if anyone did
get into certain data without using the application front end, we can catch
it.
"David Gugick" wrote:

> Just because they connect to the server doesn't mean they are going to
> change data. I would suggest you do not allow those particular logins
> access the database. Why give them access if you are trying to prevent
> it?
> If OTOH you are saying that the user requires access to the database
> from certain applications, but not others, you might consider using
> Application Roles (see Application Roles and sp_addapprole in BOL for
> more information).
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||As David said, look at application roles. If that's not an option, take a
look at APP_NAME() and USER_NAME and few other similar functions to find the
current user name and application name (session based)...
Example:
DECLARE @.CurrentApp varchar(35)
SET @.CurrentApp = APP_NAME()
IF @.CurrentApp <> 'MS SQL Query Analyzer'
PRINT 'This process was not started by a SQL Query Analyzer query session.'
Sasan Saidi, MSc in cs
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Hong Wang" wrote:
[vbcol=seagreen]
> This is for SOX audit. I have to provide a way to prove that if anyone did
> get into certain data without using the application front end, we can catch
> it.
> "David Gugick" wrote: