Re: One Web Service updates SQL, another can't?
From: Tom Moreau (tom_at_dont.spam.me.cips.ca)
Date: 10/26/04
- Next message: Kalen Delaney: "Re: EXEC in stored procedure"
- Previous message: Magnus Blomberg: "EXEC in stored procedure"
- In reply to: Steve Ricketts: "Re: One Web Service updates SQL, another can't?"
- Next in thread: Steve Ricketts: "Re: One Web Service updates SQL, another can't?"
- Reply: Steve Ricketts: "Re: One Web Service updates SQL, another can't?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 26 Oct 2004 13:15:51 -0400
If it's connecting as sa - which, BTW, is a bad thing - then the security is
essentially bypassed. The next thing I'd do is run a profiler trace and try
and see what's coming at your server. Hopefully, you can run the web
service in debug mode to step through it.
-- Tom --------------------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinnaclepublishing.com "Steve Ricketts" <steve@velocedge.com> wrote in message news:uw%23Fp63uEHA.2172@TK2MSFTNGP14.phx.gbl... I'm sending raw SQL and should have told you that I was opening the database as "sa". db_denydatawriter for sa is not checked. Does that help? sr "Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message news:uichWz3uEHA.2520@TK2MSFTNGP15.phx.gbl... > Assuming that you're using raw T-SQL - not stored procs - I'd look at who is > a member of the db_denydatawriter role in the problem database. Another > thing to look at is the permissions for that user in EM. That may tell you > if there are any explicit DENY's. > > -- > Tom > > --------------------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA > SQL Server MVP > Columnist, SQL Server Professional > Toronto, ON Canada > www.pinnaclepublishing.com > > > "Steve Ricketts" <steve@velocedge.com> wrote in message > news:eZ5PcW3uEHA.3828@TK2MSFTNGP12.phx.gbl... > I have a production and development system both running on one PC under W2K > with SQL7sp4. One Web Service can access and update the SQL Server 7 > database fine. Another instance of the same Web Service code, accessing a > different, but identical database, can read but not update records. It > seems like whichever Web Service I start first is allowed to read and write, > but the other has only read permissions. > > Is there a exclusive, read-only, permissions setting that I've missed > somewhere? The problem is simply the second Web Service can't write to SQL, > but why is the big question. Any help would be greatly appreciated, I'm > into days on this one! > > Thanks, > > Steve Ricketts > >
- Next message: Kalen Delaney: "Re: EXEC in stored procedure"
- Previous message: Magnus Blomberg: "EXEC in stored procedure"
- In reply to: Steve Ricketts: "Re: One Web Service updates SQL, another can't?"
- Next in thread: Steve Ricketts: "Re: One Web Service updates SQL, another can't?"
- Reply: Steve Ricketts: "Re: One Web Service updates SQL, another can't?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|