Re: How to dump schema script to recreate the database.



In article <FtednX5oWsc7G8TanZ2dnUVZ_saknZ2d@xxxxxxxxxxxxxxxxx>,
siegfried@xxxxxxxxxxx says...
My client's customer gave us a sample IAnywhere database that we can query.
What is the difference between sybase and IAnywhere?

IAnywhere is the subsidiary of Sybase which produces SQLAnywhere (AKA
Adaptive Server Anywhere).


When I click on "about" it says "Adaptive Server Anywhere Network Server
Version 9.0.2.2451". Since it is copyrighted 2004 I assume this is quite
old.

That may be the first GA version of 9.0.2, but there are still regular
updates to 9.0.2, the latest being from just this past October, so it's
not particularly out of date. The latest version that iAnywhere has put
out is 10.1.xxxx, I belive.



Unforunately, the account and password they gave us cannot insert into table
inside a copy of the database I made. I assume there is an admin account
that could grant my user account write access to the tables I need. We do
not know the username or the password for that account, unfortuantely.

The default admin account is dba, pwd sql. I would hope they have
changed it from the default, but it may be worth a try.



(1) Is it true that I need the username and password of some admin account
to grant my user account write access? Many database work this way including
MSAccess and MySQL and MS SQL. Is there a way to break into the datatbase
and get this username and password.

Not without Sybase's help, and they won't do it unless you can prove
that you own the database.


(2) How can I extract the schema from the database (perhaps in the form of
"create table" commands) so I can create a new identical database with a
known admin account that can grant me write access? How would I create a new
database and execute the script on the new database?

Try the "Unload database" command. You may have to look around for the
exact syntax, though. What are you using for your client connections to
the db?

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
.



Relevant Pages

  • Re: Password Protect SQL SERVER
    ... > By default there is a local NT admin account that is also sa. ... There are some 3rd party tools to encrypt the db but it can be a ... > on google for past posts regarding encryption and sql server for more ... >> in our database is their a way we can stop them from ...
    (microsoft.public.sqlserver.security)
  • RE: DB Permissions
    ... I changed some user information thru Control Panel and ... > I was trying to get my PC to auto log in as Admin whenever I start my PC ... > removed the Admin account from the Welcome screen (which I would like to get ... > plus as an added feature, I can no longer open my database. ...
    (microsoft.public.access.security)
  • Re: Password Protect SQL SERVER
    ... By default there is a local NT admin account that is also sa. ... on to their box as the local admin they are essentially sa. ... SQL Server MVP ... > in our database is their a way we can stop them from ...
    (microsoft.public.sqlserver.security)
  • Security
    ... administrator, then took the Admin account and assigned it to the User ... Now I remove all permissions from the User group. ... access my database without the workgroupfile that was created during this ...
    (microsoft.public.access.security)