Re: SQL Server write

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 07/02/04 

Date: Fri, 2 Jul 2004 08:56:58 +0200

Compare the profiler traces between the two installations. If one has a bunch of stored procedure
calls or SQL INSERT/UPDATE/DELETE, where the other doesn't, you have found the problem: the
application. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@discussions.microsoft.com> wrote in message
news:EF5DE628-773F-4C79-9CBC-7D8558434E1B@microsoft.com...
> I mean that when I log in (through the front end) those entries are captured normally in the
database and nothing is being captured.  I don't get any error messages.  A trace through Profiler
shows that it is connecting fine to the correct database and did not display any errors (Although it
shows several "reads" and 0 "writes").  I used the same user in both databases, it has Public, Read,
Write rights.  The application os from a vendor and it is a database that is a backend to this app.
> Is there a way to see the differences between the two installations of SQL server (like a script).
Would that affect it.
>
> Can there be any intermediery layers between the prod server (the one we couldn't write to) and
the test laptop server?
> Thanks
>
> "Aaron [SQL Server MVP]" wrote:
>
> > What does "unable to write new data" mean?  Do you get an error message?  If
> > so, what is it?  What kind of "write" are you trying to do, insert, update,
> > create object, something else?  What user are you connecting as?  What role
> > is this user in?  What database is the action occurring in?
> >
> > -- 
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
> >
> >
> > "Niles" <Niles@discussions.microsoft.com> wrote in message
> > news:9BB7017D-DFA8-4930-AA6C-A65AE8A6EBB7@microsoft.com...
> > > I have an application that was connected to MSDE and I've been trying to
> > connect it to a SQL server 2000.  We succeeded to connect to it and view the
> > database  and previously made entries but are unable to write new data.  The
> > next test was to install  sql server on a laptop and point the app directly
> > to the laptap. That test succeeded.  What could be different between our
> > main SQL server and the new installed one that prevents writing in one and
> > allows writing to the other.
> > >
> > > Thanks
> >
> >
> >

Relevant Pages

  • Re: More date format grief
    ... > production environments against at least five different database ... Many installations use SQL Server and have been running ... Das Internet is nicht fuer gefingerclicken und giffengrabben... ...
    (comp.lang.java.databases)
  • Re: some thoughts on the Slammer fiasco
    ... You make the assumption that everyone using SQL Server is running a big IT ... A software firewall is a perfectly fine answer for a home, or even SOHO, ... in installations with rigid policies around ...
    (microsoft.public.sqlserver.security)
  • Re: SQL2008 Fails VSShellInstalledRule
    ... Visual Studio 2008 SP1 may be required for SQL Server 2008 installations ... If you have to install SQL 2008, deselect all the Visual Studio based components. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Network Interfaces, error: 26
    ... what happens is that SQLExpress is the default name used for its named instance. ... For SQL Server 2000, it's the same. ... but most installations create a named instance which needs to be added in order to ... Just specify you PC name in the connection string ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SQL Network Interfaces, error: 26
    ... In the case of the SQL Express named instance ... For SQL Server 2000, it's the same. ... but most installations create a named instance which needs to be added in ... Just specify you PC name in the connection string ...
    (microsoft.public.dotnet.framework.aspnet)