ddl statement is not allowed

Can someone help me with this.
I have installed the trail version of SQL Server 2005 on a 2003 server
box alongside an existing installation of SQL Server 2000. I can
connect to and create new databases but cannot create tables within the
database with create table statements. I get the error 'DDL statement
is not allowed'. MDAC is at version 2.82.1830.0
I have used the same installation executable to install the same trail
version of SQL server 2005 on a different XP box with no previous SQL
Server 2000 instance on it and everything works fine there.
I have searched high and low for meaningful information on what may be
causing this and how to fix it but with no success. Anyone have any
hints, tips, ideas and best of all a solution.
Thanks in advance
RobI would guess that you have a DDL trigger that prohibits this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<rob.graveley@.tribalgroup.co.uk> wrote in message
news:1157539667.114946.82400@.m79g2000cwm.googlegroups.com...
> Can someone help me with this.
> I have installed the trail version of SQL Server 2005 on a 2003 server
> box alongside an existing installation of SQL Server 2000. I can
> connect to and create new databases but cannot create tables within the
> database with create table statements. I get the error 'DDL statement
> is not allowed'. MDAC is at version 2.82.1830.0
> I have used the same installation executable to install the same trail
> version of SQL server 2005 on a different XP box with no previous SQL
> Server 2000 instance on it and everything works fine there.
> I have searched high and low for meaningful information on what may be
> causing this and how to fix it but with no success. Anyone have any
> hints, tips, ideas and best of all a solution.
> Thanks in advance
> Rob
>|||Aye, that's what I thought too but there are no database level triggers
and no system level triggers. Select * from sys.triggers returns no
records
Rob
Tibor Karaszi wrote:
[vbcol=seagreen]
> I would guess that you have a DDL trigger that prohibits this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <rob.graveley@.tribalgroup.co.uk> wrote in message
> news:1157539667.114946.82400@.m79g2000cwm.googlegroups.com...|||rob.graveley@.tribalgroup.co.uk wrote:
> Can someone help me with this.
> I have installed the trail version of SQL Server 2005 on a 2003 server
> box alongside an existing installation of SQL Server 2000. I can
> connect to and create new databases but cannot create tables within the
> database with create table statements. I get the error 'DDL statement
> is not allowed'. MDAC is at version 2.82.1830.0
> I have used the same installation executable to install the same trail
> version of SQL server 2005 on a different XP box with no previous SQL
> Server 2000 instance on it and everything works fine there.
> I have searched high and low for meaningful information on what may be
> causing this and how to fix it but with no success. Anyone have any
> hints, tips, ideas and best of all a solution.
> Thanks in advance
> Rob
>
Are you sure you're connecting to the SQL 2005 instance?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, absolutely. From SQL Server Management Studio I have the option
of connecting to the database engine of <my_server_name> or
<my_server_nqme>\MICROSOFT##SSEE
The later is the SQL Server 2005 instance and that is the instance I am
connecting to.
Rob
Tracy McKibben wrote:

> rob.graveley@.tribalgroup.co.uk wrote:
> Are you sure you're connecting to the SQL 2005 instance?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Weird... Do you get this error if you execute a CREATE TABLE statement in a
query window? Can you
check out the edition etc. for the instance? Use @.@.VERSION and also SERVERPR
OPERTY(), see BOL for
the later.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<rob.graveley@.tribalgroup.co.uk> wrote in message
news:1157546679.445244.127540@.e3g2000cwe.googlegroups.com...
> Yes, absolutely. From SQL Server Management Studio I have the option
> of connecting to the database engine of <my_server_name> or
> <my_server_nqme>\MICROSOFT##SSEE
> The later is the SQL Server 2005 instance and that is the instance I am
> connecting to.
> Rob
> Tracy McKibben wrote:
>
>|||Yea, that is exactly where I get it and from any app that connects
through and tries to run a ddl statement.
select@.@.version returns:
'Microsoft SQL Server 2005 - 9.00.2045.00 (Intel X86) Apr 4 2006
01:20:26 Copyright (c) 1988-2005 Microsoft Corporation Embedded
Edition (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1) '
select serverproperty('Edition') returns: Embedded Edition (Windows)
select serverproperty('EngineEdition') return: 4 (Express) - now this
one is odd 'cause I had downloaded the full trial version and not the
express trial version. The same install exe installs this Express
version on my 2003 box with SQL Server 2000 on it and the Enteprise
edition on my XP box.
Rob
Tibor Karaszi wrote:
[vbcol=seagreen]
> Weird... Do you get this error if you execute a CREATE TABLE statement in
a query window? Can you
> check out the edition etc. for the instance? Use @.@.VERSION and also SERVER
PROPERTY(), see BOL for
> the later.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <rob.graveley@.tribalgroup.co.uk> wrote in message
> news:1157546679.445244.127540@.e3g2000cwe.googlegroups.com...|||Lines: 90
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
NNTP-Posting-Host: h243n2fls33o1111.telia.com 217.209.181.243
Xref: leafnode.mcse.ms microsoft.public.sqlserver.server:11660
What worries me is "Embedded". My guess is that you have the Embedded versio
n of SQL Server. I think
that this is the one that 3:rd party apps can ship with their app and the do
esn't allow storing any
data except for the data used by that app. The error when executing DDL seem
to support my
assumption.
Now, why and how you got this on your machine beats me. Perhaps you have sev
eral instances and by
mistake connect to the wrong (embedded) instance?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<rob.graveley@.tribalgroup.co.uk> wrote in message
news:1157549089.658370.26230@.i3g2000cwc.googlegroups.com...
> Yea, that is exactly where I get it and from any app that connects
> through and tries to run a ddl statement.
> select@.@.version returns:
> 'Microsoft SQL Server 2005 - 9.00.2045.00 (Intel X86) Apr 4 2006
> 01:20:26 Copyright (c) 1988-2005 Microsoft Corporation Embedded
> Edition (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1) '
> select serverproperty('Edition') returns: Embedded Edition (Windows)
> select serverproperty('EngineEdition') return: 4 (Express) - now this
> one is odd 'cause I had downloaded the full trial version and not the
> express trial version. The same install exe installs this Express
> version on my 2003 box with SQL Server 2000 on it and the Enteprise
> edition on my XP box.
> Rob
> Tibor Karaszi wrote:
>
>