Open Table Window is Read-only for SQL Query Analyzer

  • I have installed Sql Server 2000 with option of 'Client Tools Only'.  When I tried to click 'Open' of right-click on table object, a 'Open Table Window' is opened with read-only!!!!!  And the 'Add' and 'Delete' are faded out!!!!

    Can somebody help me to solve it!!

  • what kind of access do you have to the database ?

    looks like your permissions are set to read only.

    it might be an idea to have a chat with your DBA

    cheers

    dbgeezer

  • Hate to ask this but does the table have a PRIMARY KEY??

    IF the table doesn't it will be READ-ONLY through QA.

    Let me know.

     

    Thanks,

    AJ



    Good Hunting!

    AJ Ahrens


    webmaster@kritter.net

  • <snip>

    Hate to ask this but does the table have a PRIMARY KEY??

    IF the table doesn't it will be READ-ONLY through QA.

    Let me know.

    Thanks,

    AJ

    </snip>

    Are you sure this is the case ?

    I can't test it as I have the server running on my machine but it sounds very unlikely. A primary key would make no difference as to whether a table should be read-only or not.

    I'd be astonished if this was the case.

    cheers

    dbgeezer

  • I tested it before i replied to your first post with no problems.

    Unless I'm missing something here ?

    I used this:

    create table test3([id] int not null, value varchar(50))

    insert into test3 values(1, 'test')

    (1 row(s) affected)

    cheers

    dbgeezer

  •  

    Trust me on this.  I have already gone through the same thing.

    This is an old issue from ACCESS days where IF the table had no key the system would automatically lock it down.

    Here are two table scripts that you should be able to test and see:

    CREATE TABLE [tblNoKey] (

     [Field1] [INTEGER] NOT NULL ,

     [Field2] [VARCHAR](40) NULL) ON [PRIMARY]

    GO

    CREATE TABLE [tblHasKey] (

     [Field1] [INTEGER] NOT NULL ,

     [Field2] [VARCHAR](40) NULL ,

     CONSTRAINT [PK_tblHasKey] PRIMARY KEY  CLUSTERED

     ([Field1]) WITH  FILLFACTOR = 100  ON [PRIMARY]

    ) ON [PRIMARY]

    GO



    Good Hunting!

    AJ Ahrens


    webmaster@kritter.net

  • INSERT from T-SQL would work regardless of PK exist or not.  QA open table is a different animal



    Good Hunting!

    AJ Ahrens


    webmaster@kritter.net

  • Unbelivable.

    I stand astonished.

    That must be, though, the worst way of entering data into a table ...

    cheers

    dbgeezer

  • I agree with you on the WORST way of entering data.  Quite honestly I have been using SQL since 6.5 and only within the last 2 months learned of this option and can still NOT think of WHY to use it.

    Glad it is going to work out for you.

     



    Good Hunting!

    AJ Ahrens


    webmaster@kritter.net

  • I've tried it.  If the table has the primary key or unique index, then it is able to edit data.  But when I used the Server Explorer of Microsoft .NET, it is able to edit data even it has no any key or index!   However, the Server Explorer of Microsoft .NET depends on my pc's regional settings and the QA does not depend on.

    So I don't know which one is better. I just know that I feel frustrated Anyone can tell me there is a tool with full marks!?

  • You could try having a look at SQL

    cheers

    dbgeezer

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply