Re: Strongly Type Datasets

"db_owner" is a role, not a schema; "dbo" is a schema.

When you look at the name of the table in the Object Explorer (of Management
Studio), what is it? Is it dbo.TableName, or WebManagerV2.TableName?

"Chris" <nospam@xxxxxxxxxx> wrote in message
news:O7PiG6KoHHA.5052@xxxxxxxxxxxxxxxxxxxxxxx
Sorry I must be missing something. When you say "check for default
schema", I can't find it it. It is SQL 2005. I have gone to the login
propeties page of the login (in SQL 2005), gone to user mapping and put
the default scheme over to do_owner but the sql scripts generated are
still this same in VS 2005


"KJ" <n_o_s_p_a__M@xxxxxxxx> wrote in message
news:O7IrnYJoHHA.1476@xxxxxxxxxxxxxxxxxxxxxxx
Which version of SQL Server? If 2005, go to the properties page of the
login you are using (via Management Studio), and check the value for
Default Schema for that login. My guess is that it's not dbo. But this is
just a guess.

"Chris" <nospam@xxxxxxxxxx> wrote in message
news:OxkTYdHoHHA.4124@xxxxxxxxxxxxxxxxxxxxxxx
No I can't find it. Any clues where abouts I might find it. I have
looked on the properties on of the dataset etc.

"KJ" <n_o_s_p_a__M@xxxxxxxx> wrote in message
news:OFjUR$GoHHA.716@xxxxxxxxxxxxxxxxxxxxxxx
Is there a setting for the database "Schema Name" somewhere on the
properties of the data set? That's what's being prepended to the table
name.

"Chris" <nospam@xxxxxxxxxx> wrote in message
news:OdiLaBGoHHA.4412@xxxxxxxxxxxxxxxxxxxxxxx
I am trying to create a strongly typed dataset is VS 2005 with the VS
creating the stored procedures. It won't create the stored procedures.
The SQL script it generates is based on a SQL login so the script looks
something like:

DROP PROCEDURE WebManagerV2.WEB_PAGE_UPDATE

these scripts won't work until I change the script to:

DROP PROCEDURE dbo.WEB_PAGE_UPDATE

What am I doing wrong? I suspect I doing my connectionstring wrong in
some way or my permissions are wrong in SQL Server.

Regards, Chris.











.

Relevant Pages

  • Re: EXEC master..xp_cmdshell Prevention
    ... > I found that my web application did use a connection string in a file ... > stored procedures for every SQL statement would be impractical. ... I have created a new login account ...
    (microsoft.public.sqlserver.security)
  • Re: EXEC master..xp_cmdshell Prevention
    ... stored procedures for every SQL statement would be impractical. ... I have created a new login account ... > sounds as though either a) your connection string isn't what you think it ...
    (microsoft.public.sqlserver.security)
  • Re: Cannot Open SQL Server Table in Access.ADP File.
    ... I dont think that SQL Server will take 'veiw dependencies' into effect; ... Generate Script Wizard did not work on my original database, ... After fixing some of my tables and a few stored procedures and views, ...
    (microsoft.public.access.adp.sqlserver)
  • Abusing poor programming techniques in webserver scripts V 1.0
    ... $login = Request.Form ... fool the database parser. ... verified in the script of access to the database, ... The SQL statement will be parsed by the database manager, ...
    (SecProg)
  • Re: problems using a database script
    ... Create User MyAdmin For Login MyAdmin with Default_schema ... SQL Server has principals on two levels: 1) on the server level, ... There are two kinds of logins: SQL logins and Windows logins. ... In your case you have script the database on server, ...
    (comp.databases.ms-sqlserver)