Re: exporting into a SQL Server schema
- From: "Mary Chipman [MSFT]" <mchip@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 18 May 2009 08:44:53 -0700
It's not a bug, that's the way SQL Server security works -- objects
created by sysadmin are owned by dbo. The fully-qualified name of all
objects goes like this: databaseName.schema.object. Access already
knows the database name from the connection string, so all you need to
specify is schema.object.
The best solution to the problem would be to have someone who is in
the dbo/sysadmin role create the table. Then all you need is
permission to insert data. If this is something that you do
repeatedly, then create an extra column in the SQL Server table that
indicates the datetime the data was inserted.
--Mary
On Fri, 15 May 2009 14:04:44 -0700 (PDT), myotheraccount
<levtoma@xxxxxxxxx> wrote:
I'm not sure if this belongs here or in MSSQL Server - probably both..
I'm trying to export a table from Access into SQL Server. The issue
is that I want to export it into the dbo schema. Since I log into SQL
Server using windows authentication through my AD group and I my group
does not have sysadmin privelages, the schema is defaulted to my
username (It is unclear if this is a bug in SQL Server, but it sure
seems that way to me.)
Is there any way I can specify the schema name when exporting? If I
enter dbo.Table1 as my table name to export to, I get an error
message: "The object name 'dbo.Table1' you entereed doesn't follow
Microsoft Office Access object-name rules."
Any ideas?
Thanks
- Follow-Ups:
- Re: exporting into a SQL Server schema
- From: Albert D. Kallal
- Re: exporting into a SQL Server schema
- References:
- exporting into a SQL Server schema
- From: myotheraccount
- exporting into a SQL Server schema
- Prev by Date: RE: Can data pulled populate a Word doc?
- Next by Date: RE: Backend as email attachment
- Previous by thread: exporting into a SQL Server schema
- Next by thread: Re: exporting into a SQL Server schema
- Index(es):
Relevant Pages
|