sql server new users:
Hi all,
I have inherited a custom build application that is being nominated to
get replaced by something else (which is not known for know).
The company who created the application is gone and while the
application was reasonable good it won't run with XP SP2.
The application uses a database on my 2003EE MSSQL2000SE server.
Our secretary made a capitalization fault while inserting data via the
application.
Within the application it is not possible to correct this.
Thats why I thought I change it directly in the database, after making
sure that word was not indexed by other tables but is unique, I
copied/backuped the database and tried to change the cells from
"haastrecht-brug" to "Haastrecht" and a other cell in the same row from
3080 to 3079.
So I opened my Enterprise Manager located the table/row and changed it,
it seems like it changes it but when refetching it the changes are not
committed.
The strange thing is that it doesn't give any error or warnings, it all
seems to do it but after refetching these are still the old values.
What have I tried so far:
Checking for locks
Adapting the rights, on the row/table/database
Logging on as SA & Administrator
Try to change it with a update query in Enterprise Manager and Query
Analyzer
Logging to look for errors
Trying it via ODBC
Googled (including groups)on keywords like: sa, not committed,
rollbacked, prevent change, security
Tried it on the original, copy and on another server.
It seems that this is database specific because with the same tools I
can change data on other databases.
I am not a developer nor DBA but I am interested in the subject so if
anybody can guide me to find my answer I would be extremely grateful, I
do have a workaround created (in the report generator I replace the two
values) but I am still interested in how you can create this kind of
database security and how I can force a commit anyway.
Thanks in advance.
--
