Showing posts with label message. Show all posts
Showing posts with label message. Show all posts

Tuesday, March 27, 2012

Cannot enter data into database

I'm a SQL newbie and am totally perplexed. I have tried to enter the
following data and I get the subsequent message.
INSERT INTO t_Answer ( AnswerID, AssessmentID, QuestionID, EvaluationValue,
AnswerText, CreationUser_ID, RevisionUser_ID )
VALUES ( 457 , 130, 4, '14', 'testing what I want to do better', 152, 152 )
Server: Msg 241, Level 16, State 1, Line 1
Syntax error converting datetime from character string.
As you can see, I'm not entering any datetime data. I do, however, have two
fields that are date time fields.
I don't know what to do next so that i can enter data in the database.
I've tried to enter info into another table and got the same message.
Thanks for your help,
KarolusHi
At http://www.aspfaq.com/etiquette.asp?id=5006 there is instructions to post
DDL which would tell us what datatypes your columns are.
Check if there are any triggers on this table or invalid defaults e.g.
CREATE TABLE MyDate ( ID INT, ADATE datetime NOT NULL DEFAULT 'Help' )
INSERT INTO MyDate (id) values (1)
gives your error.
John
"Karolus" wrote:

> I'm a SQL newbie and am totally perplexed. I have tried to enter the
> following data and I get the subsequent message.
> INSERT INTO t_Answer ( AnswerID, AssessmentID, QuestionID, EvaluationValue
,
> AnswerText, CreationUser_ID, RevisionUser_ID )
> VALUES ( 457 , 130, 4, '14', 'testing what I want to do better', 152, 152
)
> Server: Msg 241, Level 16, State 1, Line 1
> Syntax error converting datetime from character string.
> As you can see, I'm not entering any datetime data. I do, however, have t
wo
> fields that are date time fields.
> I don't know what to do next so that i can enter data in the database.
> I've tried to enter info into another table and got the same message.
> Thanks for your help,
> Karolus|||Thanks, John, I got the document. Here is the table definition. (Thanks fo
r
the advice.)
CREATE TABLE [t_Answer] (
[AnswerID] [CodeID] NOT NULL ,
[AssessmentID] [CodeID] NOT NULL ,
[QuestionID] [CodeID] NOT NULL ,
[EvaluationValue] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[AnswerText] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[RecordStatusID] [RecordStatusID] NOT NULL ,
[RecordID] [RecordID] IDENTITY (1, 1) NOT NULL ,
[CreationUser_ID] [KeyForeign] NOT NULL ,
[CreationDtm] [DateTmCreated] NOT NULL ,
[RevisionUser_ID] [KeyForeign] NOT NULL ,
[RevisionDtm] [DateTimeRequired] NOT NULL ,
CONSTRAINT [COMMENTID] PRIMARY KEY CLUSTERED
(
[AnswerID],
[AssessmentID],
[QuestionID]
) ON [PRIMARY] ,
CONSTRAINT [fk_Answer_AssessmentID_Assessment] FOREIGN KEY
(
[AssessmentID]
) REFERENCES [t_Assessment] (
[AssessmentID]
),
CONSTRAINT [fk_Answer_QuestionID_QuestionID] FOREIGN KEY
(
[QuestionID]
) REFERENCES [t_QuestionID] (
[QuestionID]
)
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
I hope this information is helpful. I don't understand what I'm screwing up
.
"John Bell" wrote:
> Hi
> At http://www.aspfaq.com/etiquette.asp?id=5006 there is instructions to po
st
> DDL which would tell us what datatypes your columns are.
> Check if there are any triggers on this table or invalid defaults e.g.
> CREATE TABLE MyDate ( ID INT, ADATE datetime NOT NULL DEFAULT 'Help' )
> INSERT INTO MyDate (id) values (1)
> gives your error.
> John
> "Karolus" wrote:
>|||Please supply the definitions of the user-defined types: CodeID,
RecordStatusID, RecordID, KeyForeign, DateTmCreated, and DateTimeRequired.
I suspect the problem is to be found there, or in a default attached to a
user defined type.
"Karolus" <Karolus@.discussions.microsoft.com> wrote in message
news:B32CFD3E-BF21-471D-8E32-F33B5E616DE1@.microsoft.com...
> Thanks, John, I got the document. Here is the table definition. (Thanks
for
> the advice.)
> CREATE TABLE [t_Answer] (
> [AnswerID] [CodeID] NOT NULL ,
> [AssessmentID] [CodeID] NOT NULL ,
> [QuestionID] [CodeID] NOT NULL ,
> [EvaluationValue] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
> [AnswerText] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
> [RecordStatusID] [RecordStatusID] NOT NULL ,
> [RecordID] [RecordID] IDENTITY (1, 1) NOT NULL ,
> [CreationUser_ID] [KeyForeign] NOT NULL ,
> [CreationDtm] [DateTmCreated] NOT NULL ,
> [RevisionUser_ID] [KeyForeign] NOT NULL ,
> [RevisionDtm] [DateTimeRequired] NOT NULL ,
> CONSTRAINT [COMMENTID] PRIMARY KEY CLUSTERED
> (
> [AnswerID],
> [AssessmentID],
> [QuestionID]
> ) ON [PRIMARY] ,
> CONSTRAINT [fk_Answer_AssessmentID_Assessment] FOREIGN KEY
> (
> [AssessmentID]
> ) REFERENCES [t_Assessment] (
> [AssessmentID]
> ),
> CONSTRAINT [fk_Answer_QuestionID_QuestionID] FOREIGN KEY
> (
> [QuestionID]
> ) REFERENCES [t_QuestionID] (
> [QuestionID]
> )
> ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
> GO
>
> I hope this information is helpful. I don't understand what I'm screwing
up.
> "John Bell" wrote:
>
post
EvaluationValue,
152 )
have two|||Hi Karolus,
I agree with John. You may need to check triggers entering values into
RevisionDtm and CreationDtm.
You have four not null fields for that you didn't provide values in
your insert statement,
so you may have triggers for them.
I hope it help you.
Kim|||Hi
CreationDtm and Revisiondtm are not nullable, but you have not supplied a
value in your statement, therefore you would get an error for that but
normally not the one you have stated, therefore I think you may have default
s
in the user defined types DateTimeRequired and DateTmCreated that are
incorrect.
John
"Karolus" wrote:
> Thanks, John, I got the document. Here is the table definition. (Thanks
for
> the advice.)
> CREATE TABLE [t_Answer] (
> [AnswerID] [CodeID] NOT NULL ,
> [AssessmentID] [CodeID] NOT NULL ,
> [QuestionID] [CodeID] NOT NULL ,
> [EvaluationValue] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
> [AnswerText] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
> [RecordStatusID] [RecordStatusID] NOT NULL ,
> [RecordID] [RecordID] IDENTITY (1, 1) NOT NULL ,
> [CreationUser_ID] [KeyForeign] NOT NULL ,
> [CreationDtm] [DateTmCreated] NOT NULL ,
> [RevisionUser_ID] [KeyForeign] NOT NULL ,
> [RevisionDtm] [DateTimeRequired] NOT NULL ,
> CONSTRAINT [COMMENTID] PRIMARY KEY CLUSTERED
> (
> [AnswerID],
> [AssessmentID],
> [QuestionID]
> ) ON [PRIMARY] ,
> CONSTRAINT [fk_Answer_AssessmentID_Assessment] FOREIGN KEY
> (
> [AssessmentID]
> ) REFERENCES [t_Assessment] (
> [AssessmentID]
> ),
> CONSTRAINT [fk_Answer_QuestionID_QuestionID] FOREIGN KEY
> (
> [QuestionID]
> ) REFERENCES [t_QuestionID] (
> [QuestionID]
> )
> ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
> GO
>
> I hope this information is helpful. I don't understand what I'm screwing
up.
> "John Bell" wrote:
>|||Thanks all for your help. I VERY much appreciate it. I've come for Sybase
and am overwhelmed by the difference. Here are the domain definitions and
the code that created the table, t_answers. I assumed that I should provide
a datetime, but that didn't work either...so I'm .
Here's the information:
/ *=======================================
=======================*/
/* Domain: DateTmCreated */
/ *=======================================
=======================*/
sp_addtype DateTmCreated, 'datetime' , 'not null'
go
/ *=======================================
=======================*/
/* Domain: DateTimeNotMandatory */
/ *=======================================
=======================*/
sp_addtype DateTimeNotMandatory, 'datetime'
go
/ *=======================================
=======================*/
/* Domain: DateTimeRequired */
/ *=======================================
=======================*/
sp_addtype DateTimeRequired, 'datetime' , 'not null'
go
create default D_DateTimeRequired
as 'CURRENT TIMESTAMP'
go
sp_bindefault D_DateTimeRequired, DateTimeRequired
go
/ *=======================================
=======================*/
/* Domain: DateTm */
/ *=======================================
=======================*/
sp_addtype DateTm, 'datetime'
go
create default D_DateTm
as 'CURRENT TIMESTAMP'
go
sp_bindefault D_DateTm, DateTm
go
/ *=======================================
=======================*/
/* Table : t_Answer */
/ *=======================================
=======================*/
create table t_Answer (
AnswerID CodeID not null,
AssessmentID CodeID not null,
QuestionID CodeID not null,
EvaluationValue text null,
AnswerText text null,
RecordStatusID RecordStatusID not null,
RecordID RecordID identity,
CreationUser_ID KeyForeign not null,
CreationDtm DateTmCreated not null,
RevisionUser_ID KeyForeign not null,
RevisionDtm DateTimeRequired not null,
constraint COMMENTID primary key (AnswerID, AssessmentID, QuestionID)
)
go
"John Bell" wrote:
> Hi
> CreationDtm and Revisiondtm are not nullable, but you have not supplied a
> value in your statement, therefore you would get an error for that but
> normally not the one you have stated, therefore I think you may have defau
lts
> in the user defined types DateTimeRequired and DateTmCreated that are
> incorrect.
> John
> "Karolus" wrote:
>|||Looks like the error is just the CREATE DEFAULT statements.
CURRENT_TIMESTAMP is a keyword and mustn't be quoted as a string:
CREATE DEFAULT D_DateTm
AS CURRENT_TIMESTAMP
David Portas
SQL Server MVP
--sql

Cannot enable the Service Broker

When I try to enable the Service Broker I receive the following error message:
Cannot enable the Service Broker in database "msdb" because the Service
Broker GUID in the database (01F9916A-21C0-4EA1-A555-A9C7A020C718) does not
match the one in sys.databases (A7B475E6-5781-4FC2-B1E0-B0EF17FFE942).
ALTER DATABASE statement failed. (Microsoft SQL Server, Error: 9776)
So as far as I can understand in the MSDB database the Service Broker GUID
is different from the one in the table sys.databases.
Is there a possibility to correct this so I will be able to enable the
Service Broker?
I want to enable it so I can configure the email part on this SQL server.
If the GUID itself can not be changed is there a way to rebuild the MSDB
database?
Thanks for the info,
LimmerTry:
ALTER DATABASE MSDB SET NEW_BROKER
If SQL Agent is running, you will have to shut it down or this will hang.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Limmer" <Limmer@.discussions.microsoft.com> wrote in message
news:71240018-A03C-4F0D-830A-537F95BBB662@.microsoft.com...
> When I try to enable the Service Broker I receive the following error
> message:
> Cannot enable the Service Broker in database "msdb" because the Service
> Broker GUID in the database (01F9916A-21C0-4EA1-A555-A9C7A020C718) does
> not
> match the one in sys.databases (A7B475E6-5781-4FC2-B1E0-B0EF17FFE942).
> ALTER DATABASE statement failed. (Microsoft SQL Server, Error: 9776)
> So as far as I can understand in the MSDB database the Service Broker GUID
> is different from the one in the table sys.databases.
> Is there a possibility to correct this so I will be able to enable the
> Service Broker?
> I want to enable it so I can configure the email part on this SQL server.
> If the GUID itself can not be changed is there a way to rebuild the MSDB
> database?
> Thanks for the info,
> Limmer
>|||Thanks Roger,
This did the trick.
Limmer
"Roger Wolter[MSFT]" wrote:
> Try:
> ALTER DATABASE MSDB SET NEW_BROKER
> If SQL Agent is running, you will have to shut it down or this will hang.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Limmer" <Limmer@.discussions.microsoft.com> wrote in message
> news:71240018-A03C-4F0D-830A-537F95BBB662@.microsoft.com...
> > When I try to enable the Service Broker I receive the following error
> > message:
> >
> > Cannot enable the Service Broker in database "msdb" because the Service
> > Broker GUID in the database (01F9916A-21C0-4EA1-A555-A9C7A020C718) does
> > not
> > match the one in sys.databases (A7B475E6-5781-4FC2-B1E0-B0EF17FFE942).
> > ALTER DATABASE statement failed. (Microsoft SQL Server, Error: 9776)
> >
> > So as far as I can understand in the MSDB database the Service Broker GUID
> > is different from the one in the table sys.databases.
> > Is there a possibility to correct this so I will be able to enable the
> > Service Broker?
> > I want to enable it so I can configure the email part on this SQL server.
> >
> > If the GUID itself can not be changed is there a way to rebuild the MSDB
> > database?
> >
> > Thanks for the info,
> > Limmer
> >
>
>sql

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?
Either remove them from the master server. Or hack msdb..sysjobs (originating_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?Either remove them from the master server. Or hack msdb..sysjobs (originatin
g_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?Either remove them from the master server. Or hack msdb..sysjobs (originating_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Sunday, March 25, 2012

Cannot deploy to RS2K from Visual Studio 2005

I started using Visual Studio 2005 and when trying to create a SQL Report and
deploy it to a SQL RS 2000 I get this error message "the attemp to connect to
the report server failed. Checked your connection information and that the
report server is a compatible version.
(Microsoft.ReportingServices.Designer)".
Does that mean Visual Studio 2005 is not backward compatible with SQRS2000?
or do I have to modify something in the config of VS2005?
Any ideas?
CarlosYou can deploy 2000 reports to 2005. You cannot deploy 2005 reports to 2000
server.
2005 is backward compatible in the sense that you don't have to modify any
2000 reports for the report to work in 2005 server. However, to use the new
features (multi-select parameters, user run-time sorting etc) you have to
convert the report.
If you think about it, how would 2005 be able to deploy with a 2000 server.
2000 knows nothing about the new features.
You can run side by side for development. If you have to deploy to 2000 then
you need to install RS 2000 report designer and VS 2003 to host the
designer.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:D638ACB1-553D-4AE4-B87F-156C9E622A79@.microsoft.com...
>I started using Visual Studio 2005 and when trying to create a SQL Report
>and
> deploy it to a SQL RS 2000 I get this error message "the attemp to connect
> to
> the report server failed. Checked your connection information and that the
> report server is a compatible version.
> (Microsoft.ReportingServices.Designer)".
> Does that mean Visual Studio 2005 is not backward compatible with
> SQRS2000?
> or do I have to modify something in the config of VS2005?
> Any ideas?
> Carlos|||Thanks Bruce
"Bruce L-C [MVP]" wrote:
> You can deploy 2000 reports to 2005. You cannot deploy 2005 reports to 2000
> server.
> 2005 is backward compatible in the sense that you don't have to modify any
> 2000 reports for the report to work in 2005 server. However, to use the new
> features (multi-select parameters, user run-time sorting etc) you have to
> convert the report.
> If you think about it, how would 2005 be able to deploy with a 2000 server.
> 2000 knows nothing about the new features.
> You can run side by side for development. If you have to deploy to 2000 then
> you need to install RS 2000 report designer and VS 2003 to host the
> designer.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:D638ACB1-553D-4AE4-B87F-156C9E622A79@.microsoft.com...
> >I started using Visual Studio 2005 and when trying to create a SQL Report
> >and
> > deploy it to a SQL RS 2000 I get this error message "the attemp to connect
> > to
> > the report server failed. Checked your connection information and that the
> > report server is a compatible version.
> > (Microsoft.ReportingServices.Designer)".
> >
> > Does that mean Visual Studio 2005 is not backward compatible with
> > SQRS2000?
> > or do I have to modify something in the config of VS2005?
> >
> > Any ideas?
> >
> > Carlos
>
>

Thursday, March 22, 2012

Cannot Deploy Report Model

I'm going through the 2005 SSRS tutorial for creating a report model and I
cannot deploy the model. The message I get is:
The permissions granted to user 'DOMAIN\USER' are insufficient for
performing this operation.
Both the SQL Server 2005 and SSRS are deployed on my machine on which I am
an administrator (both within the windows environment and in SQL Server).
Can someone please help?
Thanks,
JimI would imagine you are part of the Content Manager role on the report
server? Make sure your role on the report server has permission to Manage
Models and View Models. I had this problem when I upgraded from SSRS 2000 to
2005. For some reason none of the report model permissions were set after
the upgrade.
"Jim" wrote:
> I'm going through the 2005 SSRS tutorial for creating a report model and I
> cannot deploy the model. The message I get is:
> The permissions granted to user 'DOMAIN\USER' are insufficient for
> performing this operation.
> Both the SQL Server 2005 and SSRS are deployed on my machine on which I am
> an administrator (both within the windows environment and in SQL Server).
> Can someone please help?
> Thanks,
> Jim

cannot deliver inserts

HI we are using merge replication and now i am getting the
error message as ' cannot deliver inserts to the publisher'
Kiran,
does restarting the agent fix the issue? If not, then are you replicating to
CE - known issue there
(http://support.microsoft.com/default...b;en-us;328314). If neither
of these apply, then please enable logging
(http://support.microsoft.com/?id=312292) and post up further details of the
schema and error message>
Thanks,
Paul Ibison
|||HI paul thanks,
but we are using sql2000 merge replication.
so this article deosn't apply to us.

>--Original Message--
>Kiran,
>does restarting the agent fix the issue? If not, then are
you replicating to
>CE - known issue there
>(http://support.microsoft.com/default.aspx?scid=kb;en-
us;328314). If neither
>of these apply, then please enable logging
>(http://support.microsoft.com/?id=312292) and post up
further details of the
>schema and error message>
>Thanks,
>Paul Ibison
>
>.
>
|||Kiran,
ok, then check that the subscriber can 'see' the publisher using QA. If not,
then it's a connectivity issue, if it can then enable logging and post up
the message.
Regards,
Paul Ibison
|||Hi paul,
it was happening becos of the conflicts we had for that
subscriber. It was taking so long to reconcoile the
conflicts. i ended up recreating subscription and now it
seems fine.
thanks
>--Original Message--
>Kiran,
>ok, then check that the subscriber can 'see' the
publisher using QA. If not,
>then it's a connectivity issue, if it can then enable
logging and post up
>the message.
>Regards,
>Paul Ibison
>
>.
>
|||Kiran,
thanks for the update. Recreating the subscription has removed the conflicts
so you don't experience the same problem straight away. To prevent this
error in future, you might want to create a custom profile for your merge
agent and increase the QueryTimeOut .
Regards,
Paul Ibison

Cannot delete SQL database user

Dear all,
I was trying to delete a user of a SQL database. But it cannot be deleted
and the error message is: "Error 15008: User 'username' does not exist in the
current database."
The database had some problem yesterday and I restored the backup
successfully. But the database user login cannot be deleted. How to solve
this problem?
Thanks in advance.
IvanThere is a big difference between a user and a login. Is this a user or a
login?
On 3/3/05 11:43 PM, in article
80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
> Dear all,
> I was trying to delete a user of a SQL database. But it cannot be deleted
> and the error message is: "Error 15008: User 'username' does not exist in the
> current database."
> The database had some problem yesterday and I restored the backup
> successfully. But the database user login cannot be deleted. How to solve
> this problem?
> Thanks in advance.
> Ivan|||Hi,
It is a "Database User"
Ivan
"Aaron [SQL Server MVP]" wrote:
> There is a big difference between a user and a login. Is this a user or a
> login?
>
> On 3/3/05 11:43 PM, in article
> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
> > Dear all,
> >
> > I was trying to delete a user of a SQL database. But it cannot be deleted
> > and the error message is: "Error 15008: User 'username' does not exist in the
> > current database."
> > The database had some problem yesterday and I restored the backup
> > successfully. But the database user login cannot be deleted. How to solve
> > this problem?
> > Thanks in advance.
> >
> > Ivan
>|||Open Query Analyzer, and with the correct database context, what happens
when you say:
EXEC sp_helpusers
EXEC sp_helpuser 'username'
EXEC sp_helplogins
EXEC sp_helplogin 'username'
?
On 3/3/05 11:59 PM, in article
C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
> Hi,
> It is a "Database User"
> Ivan
> "Aaron [SQL Server MVP]" wrote:
>> There is a big difference between a user and a login. Is this a user or a
>> login?
>>
>> On 3/3/05 11:43 PM, in article
>> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
>> <Ivan@.discussions.microsoft.com> wrote:
>> Dear all,
>> I was trying to delete a user of a SQL database. But it cannot be deleted
>> and the error message is: "Error 15008: User 'username' does not exist in
>> the
>> current database."
>> The database had some problem yesterday and I restored the backup
>> successfully. But the database user login cannot be deleted. How to solve
>> this problem?
>> Thanks in advance.
>> Ivan
>>|||Hi,
I tried to stop the SQL server service and started it again, then I could
delete it.
Thanks a lot and your help is greatly appreciated!
Ivan
"Aaron [SQL Server MVP]" wrote:
> Open Query Analyzer, and with the correct database context, what happens
> when you say:
> EXEC sp_helpusers
> EXEC sp_helpuser 'username'
> EXEC sp_helplogins
> EXEC sp_helplogin 'username'
> ?
>
> On 3/3/05 11:59 PM, in article
> C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
> > Hi,
> >
> > It is a "Database User"
> >
> > Ivan
> >
> > "Aaron [SQL Server MVP]" wrote:
> >
> >> There is a big difference between a user and a login. Is this a user or a
> >> login?
> >>
> >>
> >> On 3/3/05 11:43 PM, in article
> >> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> >> <Ivan@.discussions.microsoft.com> wrote:
> >>
> >> Dear all,
> >>
> >> I was trying to delete a user of a SQL database. But it cannot be deleted
> >> and the error message is: "Error 15008: User 'username' does not exist in
> >> the
> >> current database."
> >> The database had some problem yesterday and I restored the backup
> >> successfully. But the database user login cannot be deleted. How to solve
> >> this problem?
> >> Thanks in advance.
> >>
> >> Ivan
> >>
> >>
>

Cannot delete SQL database user

Dear all,
I was trying to delete a user of a SQL database. But it cannot be deleted
and the error message is: "Error 15008: User 'username' does not exist in the
current database."
The database had some problem yesterday and I restored the backup
successfully. But the database user login cannot be deleted. How to solve
this problem?
Thanks in advance.
Ivan
There is a big difference between a user and a login. Is this a user or a
login?
On 3/3/05 11:43 PM, in article
80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:

> Dear all,
> I was trying to delete a user of a SQL database. But it cannot be deleted
> and the error message is: "Error 15008: User 'username' does not exist in the
> current database."
> The database had some problem yesterday and I restored the backup
> successfully. But the database user login cannot be deleted. How to solve
> this problem?
> Thanks in advance.
> Ivan
|||Hi,
It is a "Database User"
Ivan
"Aaron [SQL Server MVP]" wrote:

> There is a big difference between a user and a login. Is this a user or a
> login?
>
> On 3/3/05 11:43 PM, in article
> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>
|||Open Query Analyzer, and with the correct database context, what happens
when you say:
EXEC sp_helpusers
EXEC sp_helpuser 'username'
EXEC sp_helplogins
EXEC sp_helplogin 'username'
?
On 3/3/05 11:59 PM, in article
C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
> Hi,
> It is a "Database User"
> Ivan
> "Aaron [SQL Server MVP]" wrote:
|||Hi,
I tried to stop the SQL server service and started it again, then I could
delete it.
Thanks a lot and your help is greatly appreciated!
Ivan
"Aaron [SQL Server MVP]" wrote:

> Open Query Analyzer, and with the correct database context, what happens
> when you say:
> EXEC sp_helpusers
> EXEC sp_helpuser 'username'
> EXEC sp_helplogins
> EXEC sp_helplogin 'username'
> ?
>
> On 3/3/05 11:59 PM, in article
> C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>

Cannot delete SQL database user

Dear all,
I was trying to delete a user of a SQL database. But it cannot be deleted
and the error message is: "Error 15008: User 'username' does not exist in th
e
current database."
The database had some problem yesterday and I restored the backup
successfully. But the database user login cannot be deleted. How to solve
this problem?
Thanks in advance.
IvanThere is a big difference between a user and a login. Is this a user or a
login?
On 3/3/05 11:43 PM, in article
80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:

> Dear all,
> I was trying to delete a user of a SQL database. But it cannot be deleted
> and the error message is: "Error 15008: User 'username' does not exist in
the
> current database."
> The database had some problem yesterday and I restored the backup
> successfully. But the database user login cannot be deleted. How to solve
> this problem?
> Thanks in advance.
> Ivan|||Hi,
It is a "Database User"
Ivan
"Aaron [SQL Server MVP]" wrote:

> There is a big difference between a user and a login. Is this a user or a
> login?
>
> On 3/3/05 11:43 PM, in article
> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>|||Open Query Analyzer, and with the correct database context, what happens
when you say:
EXEC sp_helpusers
EXEC sp_helpuser 'username'
EXEC sp_helplogins
EXEC sp_helplogin 'username'
?
On 3/3/05 11:59 PM, in article
C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
> Hi,
> It is a "Database User"
> Ivan
> "Aaron [SQL Server MVP]" wrote:
>|||Hi,
I tried to stop the SQL server service and started it again, then I could
delete it.
Thanks a lot and your help is greatly appreciated!
Ivan
"Aaron [SQL Server MVP]" wrote:

> Open Query Analyzer, and with the correct database context, what happens
> when you say:
> EXEC sp_helpusers
> EXEC sp_helpuser 'username'
> EXEC sp_helplogins
> EXEC sp_helplogin 'username'
> ?
>
> On 3/3/05 11:59 PM, in article
> C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>sql

Cannot delete SQL 2000 backup file

I have a .bak file that I am trying to delete because the backup failed due
to insufficient space on the disk drive. The message I get is that it is
in use by another person or program. I cannot find the person or program.
What should I be looking for? I use native SQL backup.
Message posted via http://www.sqlmonster.com
You may have to stop the SQLServerAgent service so that it will release the
file.
If that doesn't work (try the MSSQLServer service). One of the two is
holding on to the file.
Rick Sawtell
MCT, MCSD, MCDBA
"Debra Camacho-Padron via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:2a3f51e677de49ec92f681f87f14936c@.SQLMonster.c om...
> I have a .bak file that I am trying to delete because the backup failed
due
> to insufficient space on the disk drive. The message I get is that it is
> in use by another person or program. I cannot find the person or program.
> What should I be looking for? I use native SQL backup.
> --
> Message posted via http://www.sqlmonster.com
|||That's what I thought too. I tried both, and it still indicates that the
file is in use.
Message posted via http://www.sqlmonster.com
|||Try using FileMon from sysinternals to see what is accessing
the file:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
-Sue
On Tue, 15 Mar 2005 18:01:24 GMT, "Debra Camacho-Padron via
SQLMonster.com" <forum@.SQLMonster.com> wrote:

>That's what I thought too. I tried both, and it still indicates that the
>file is in use.

Cannot delete SQL 2000 backup file

I have a .bak file that I am trying to delete because the backup failed due
to insufficient space on the disk drive. The message I get is that it is
in use by another person or program. I cannot find the person or program.
What should I be looking for? I use native SQL backup.
Message posted via http://www.droptable.comYou may have to stop the SQLServerAgent service so that it will release the
file.
If that doesn't work (try the MSSQLServer service). One of the two is
holding on to the file.
Rick Sawtell
MCT, MCSD, MCDBA
"Debra Camacho-Padron via droptable.com" <forum@.droptable.com> wrote in
message news:2a3f51e677de49ec92f681f87f14936c@.SQ
droptable.com...
> I have a .bak file that I am trying to delete because the backup failed
due
> to insufficient space on the disk drive. The message I get is that it is
> in use by another person or program. I cannot find the person or program.
> What should I be looking for? I use native SQL backup.
> --
> Message posted via http://www.droptable.com|||That's what I thought too. I tried both, and it still indicates that the
file is in use.
Message posted via http://www.droptable.com|||Try using FileMon from sysinternals to see what is accessing
the file:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
-Sue
On Tue, 15 Mar 2005 18:01:24 GMT, "Debra Camacho-Padron via
droptable.com" <forum@.droptable.com> wrote:

>That's what I thought too. I tried both, and it still indicates that the
>file is in use.

Cannot delete SQL 2000 backup file

I have a .bak file that I am trying to delete because the backup failed due
to insufficient space on the disk drive. The message I get is that it is
in use by another person or program. I cannot find the person or program.
What should I be looking for? I use native SQL backup.
--
Message posted via http://www.sqlmonster.comYou may have to stop the SQLServerAgent service so that it will release the
file.
If that doesn't work (try the MSSQLServer service). One of the two is
holding on to the file.
Rick Sawtell
MCT, MCSD, MCDBA
"Debra Camacho-Padron via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:2a3f51e677de49ec92f681f87f14936c@.SQLMonster.com...
> I have a .bak file that I am trying to delete because the backup failed
due
> to insufficient space on the disk drive. The message I get is that it is
> in use by another person or program. I cannot find the person or program.
> What should I be looking for? I use native SQL backup.
> --
> Message posted via http://www.sqlmonster.com|||That's what I thought too. I tried both, and it still indicates that the
file is in use.
--
Message posted via http://www.sqlmonster.com|||Try using FileMon from sysinternals to see what is accessing
the file:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
-Sue
On Tue, 15 Mar 2005 18:01:24 GMT, "Debra Camacho-Padron via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>That's what I thought too. I tried both, and it still indicates that the
>file is in use.

Cannot delete rows that contain same data

Using SQL Sever 2005 Management Studio I am trying to delete rows that are
duplicated in a table. There is no Primary Key. I get an error message to
the effect that the rows cannot be deleted because it would effect other
rows. If I attempt to change a field in the row I get the same error. In
this application there may be many duplicate rows that will need to deleted
at various times.
Thanks,
Bob HillerNo primary key is often an indication of a data model problem. Even if this
is simply a staging table used as part of an ELT process, you can add a
surrogate key to facilitate set-based processing and use GUI tools.
Do all columns of 'duplicate' rows contain the same values? In SQL 2005,
you can specify a TOP clause on a delete statement to delete only a
specified number of rows like the example below. Similarly, you can use SET
ROWCOUNT in earlier version but need to be careful to execute SET ROWCOUNT 0
afterward.
CREATE TABLE Table1 (Col1 int)
INSERT INTO Table1 VALUES(1)
INSERT INTO Table1 VALUES(1)
INSERT INTO Table1 VALUES(1)
SELECT * FROM Table1
DELETE TOP (2) FROM Table1 WHERE Col1 = 1
SELECT * FROM Table1
Hope this helps.
Dan Guzman
SQL Server MVP
"Bob and Sharon Hiller" <aoklans@.tir.com> wrote in message
news:uLNoND3SGHA.4752@.TK2MSFTNGP10.phx.gbl...
> Using SQL Sever 2005 Management Studio I am trying to delete rows that are
> duplicated in a table. There is no Primary Key. I get an error message to
> the effect that the rows cannot be deleted because it would effect other
> rows. If I attempt to change a field in the row I get the same error. In
> this application there may be many duplicate rows that will need to
> deleted at various times.
> Thanks,
> Bob Hiller
>|||Dan,
Yes, All of the columns contain the same values. Is there any way to delete
these rows by hitting the delete key or right click/delete?
Thanks,
Bob Hiller
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:uHlyng3SGHA.5736@.TK2MSFTNGP10.phx.gbl...
> No primary key is often an indication of a data model problem. Even if
> this is simply a staging table used as part of an ELT process, you can add
> a surrogate key to facilitate set-based processing and use GUI tools.
> Do all columns of 'duplicate' rows contain the same values? In SQL 2005,
> you can specify a TOP clause on a delete statement to delete only a
> specified number of rows like the example below. Similarly, you can use
> SET ROWCOUNT in earlier version but need to be careful to execute SET
> ROWCOUNT 0 afterward.
> CREATE TABLE Table1 (Col1 int)
> INSERT INTO Table1 VALUES(1)
> INSERT INTO Table1 VALUES(1)
> INSERT INTO Table1 VALUES(1)
> SELECT * FROM Table1
> DELETE TOP (2) FROM Table1 WHERE Col1 = 1
> SELECT * FROM Table1
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Bob and Sharon Hiller" <aoklans@.tir.com> wrote in message
> news:uLNoND3SGHA.4752@.TK2MSFTNGP10.phx.gbl...
>|||AFAIK, you can't delete rows using the GUI when all columns have the same
value. This is because the tools generate a DELETE statement behind the
scenes and the row(s) you want to delete is ambiguous when all columns have
the same value. If you must use a GUI, you'll need to add a column to
uniquely identify a row:
ALTER TABLE Table1
ADD TempID int IDENTITY(1, 1)
Hope this helps.
Dan Guzman
SQL Server MVP
"Bob and Sharon Hiller" <aoklans@.tir.com> wrote in message
news:u$RtNV4SGHA.5156@.TK2MSFTNGP10.phx.gbl...
> Dan,
> Yes, All of the columns contain the same values. Is there any way to
> delete these rows by hitting the delete key or right click/delete?
> Thanks,
> Bob Hiller
>|||Bob,
As Dan has already said, you will probably struggle to delete these rows
using a GUI tool (e.g. Enterprise Manager) because there is no key defined
for the table. You should probably first add a key to the table, then do
your DELETE operations, and then, if you really don't want a key any more
you could remove the key definition (and in doing so, re-introduce the
design flaw).
There are probably ways around this, if you're prepared to write your
own SQL DELETEs rather than use a GUI to perform the delete ops. But that
doesn't change the fact that there is a design problem which needs to be
fixed. A correct RDBMS (database) design will always see a field (or set of
fields) defined as a unique key, even on temporary tables. Perhaps the only
exception would be staging tables used to clean data, but those will,
nevertheless, need a key defined at some point during the migration process.
HTH
Robert
"Bob and Sharon Hiller" <aoklans@.tir.com> wrote in message
news:u$RtNV4SGHA.5156@.TK2MSFTNGP10.phx.gbl...
> Dan,
> Yes, All of the columns contain the same values. Is there any way to
> delete these rows by hitting the delete key or right click/delete?
> Thanks,
> Bob Hiller
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:uHlyng3SGHA.5736@.TK2MSFTNGP10.phx.gbl...
>|||The Table I am referring to is just being used for testing. I was using a
random number generator in my program that I developed to send the data to
the table. The random number generator at some point started duplicating
numbers. I am now going to implement the table in production mode and there
will of course be a key. It is very important because I am recording
automotive serial numbers which must be unique.
Thanks,
Bob Hiller
"Robert Ellis" <robe_2k5@.n0sp8m.hotmail.co.uk> wrote in message
news:%23wuSOn4SGHA.424@.TK2MSFTNGP12.phx.gbl...
> Bob,
> As Dan has already said, you will probably struggle to delete these
> rows using a GUI tool (e.g. Enterprise Manager) because there is no key
> defined for the table. You should probably first add a key to the table,
> then do your DELETE operations, and then, if you really don't want a key
> any more you could remove the key definition (and in doing so,
> re-introduce the design flaw).
> There are probably ways around this, if you're prepared to write your
> own SQL DELETEs rather than use a GUI to perform the delete ops. But that
> doesn't change the fact that there is a design problem which needs to be
> fixed. A correct RDBMS (database) design will always see a field (or set
> of fields) defined as a unique key, even on temporary tables. Perhaps the
> only exception would be staging tables used to clean data, but those will,
> nevertheless, need a key defined at some point during the migration
> process.
> HTH
> Robert
>
>
> "Bob and Sharon Hiller" <aoklans@.tir.com> wrote in message
> news:u$RtNV4SGHA.5156@.TK2MSFTNGP10.phx.gbl...
>|||Hey Bob,
Since this sounds like it's an issue of data cleansing for development
work, try something like the following:
SELECT DISTINCT *
INTO newTable
FROM oldTable
TRUNCATE TABLE oldTable
INSERT INTO oldTable
SELECT *
FROM newTable
DROP TABLE newTable
HTH,
Stu|||Bob,
Fair enough mate!
Just a small observation, for what it may be worth, (and yes, I'm being
somewhat pedantic here):
If you've got a scenario where you're first building a test system, and
then shifting to production (which is practically always the case with any
form of software development) then you might as well spend the extra time
developing your test DDL as fully as possible, because doing so will aid you
when it comes to evaluating the behaviour and performance of your client
software. The point here is, if a unqiue constraint had been enforced on
your test table, you're client program would never have been able to insert
those "duplicate" rows -- and so, you'd have been a step ahead...
Wishing you well with your project,
Regards,
Robert
"Bob and Sharon Hiller" <aoklans@.tir.com> wrote in message
news:uWN7VS5SGHA.736@.TK2MSFTNGP12.phx.gbl...
> The Table I am referring to is just being used for testing. I was using a
> random number generator in my program that I developed to send the data to
> the table. The random number generator at some point started duplicating
> numbers. I am now going to implement the table in production mode and
> there will of course be a key. It is very important because I am recording
> automotive serial numbers which must be unique.
> Thanks,
> Bob Hiller
>
> "Robert Ellis" <robe_2k5@.n0sp8m.hotmail.co.uk> wrote in message
> news:%23wuSOn4SGHA.424@.TK2MSFTNGP12.phx.gbl...
>

Cannot delete or edit transfered SQL Server Jobs

Hello,

I have a problem with EM and the msdb. I get an error message 14274
when I try to edit or delete a job. The data in the msdb for the jobs
was generated by a restored backup that came from another machine, and
a different instance of SQL Server. The old default server instance
was called 'SQL_Server' and the new default instance is called
'SDO-SQL'.
The error message states:

Cannot add, update, or delete a job (or its steps or schedules) that
originated from an MSX server.

I don't have a master scheduling server. I get the error
message when attempting to change a job. eg. enable/disable a job,
change the time, delete a job, add a job.

Server is running w2k Server SP4

I tired the following:

USE MSDB

UPDATE sysjobs

SET originating_server = 'SD0-SQL'

From the properties of any job, I can see that the 'Source' is now
correctly identified as 'SDO-SQL', but the problem still remains.

What can I do with these jobs so that I can edit and delete them on
the new server?

Thank you for your help!

CSDunnHi

It looks like you may have already seen

http://support.microsoft.com/defaul...kb;en-us;281642

It suggests that you rename the server back to the old server name rather
than mess with the tables, but if you are trying to update sysjob I would
expect originating_server to be in the form 'server\instance'.

John

"CSDunn" <cdunn@.valverde.edu> wrote in message
news:807dbff7.0405151632.2f68ffe8@.posting.google.c om...
> Hello,
> I have a problem with EM and the msdb. I get an error message 14274
> when I try to edit or delete a job. The data in the msdb for the jobs
> was generated by a restored backup that came from another machine, and
> a different instance of SQL Server. The old default server instance
> was called 'SQL_Server' and the new default instance is called
> 'SDO-SQL'.
> The error message states:
> Cannot add, update, or delete a job (or its steps or schedules) that
> originated from an MSX server.
> I don't have a master scheduling server. I get the error
> message when attempting to change a job. eg. enable/disable a job,
> change the time, delete a job, add a job.
> Server is running w2k Server SP4
> I tired the following:
> USE MSDB
> UPDATE sysjobs
> SET originating_server = 'SD0-SQL'
> From the properties of any job, I can see that the 'Source' is now
> correctly identified as 'SDO-SQL', but the problem still remains.
> What can I do with these jobs so that I can edit and delete them on
> the new server?
> Thank you for your help!
> CSDunn|||John,
Thank you for your help!

CSDunn

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<0lEpc.948$XY4.12507228@.news-text.cableinet.net>...
> Hi
> It looks like you may have already seen
> http://support.microsoft.com/defaul...kb;en-us;281642
> It suggests that you rename the server back to the old server name rather
> than mess with the tables, but if you are trying to update sysjob I would
> expect originating_server to be in the form 'server\instance'.
> John
> "CSDunn" <cdunn@.valverde.edu> wrote in message
> news:807dbff7.0405151632.2f68ffe8@.posting.google.c om...
> > Hello,
> > I have a problem with EM and the msdb. I get an error message 14274
> > when I try to edit or delete a job. The data in the msdb for the jobs
> > was generated by a restored backup that came from another machine, and
> > a different instance of SQL Server. The old default server instance
> > was called 'SQL_Server' and the new default instance is called
> > 'SDO-SQL'.
> > The error message states:
> > Cannot add, update, or delete a job (or its steps or schedules) that
> > originated from an MSX server.
> > I don't have a master scheduling server. I get the error
> > message when attempting to change a job. eg. enable/disable a job,
> > change the time, delete a job, add a job.
> > Server is running w2k Server SP4
> > I tired the following:
> > USE MSDB
> > UPDATE sysjobs
> > SET originating_server = 'SD0-SQL'
> > From the properties of any job, I can see that the 'Source' is now
> > correctly identified as 'SDO-SQL', but the problem still remains.
> > What can I do with these jobs so that I can edit and delete them on
> > the new server?
> > Thank you for your help!
> > CSDunn|||I found another workaround (OS W2K3 Server, SQL Server 2K with SP4):

1. Script out all of the jobs.
2. Update the job source by:
USE MSDB
UPDATE sysjobs
SET originating_server = 'New_Server_Name'
3. Rename the jobs to be deleted.
4. Delete the jobs.
5. Add back the jobs by running the script generated from step 1.

Hope this will work better!

Ray

Tuesday, March 20, 2012

Cannot create subscription in with Report Manager

While on the Report Delivery Options page if I click "Select Schedule" or
"OK" nothing happens; no error message, no postback, nothing in the logs,
nothing in a SQL Trace. I cannot create a File Share nor an e-mail
subcription.
I am able to programmaticaly (using ReportServer WebService and
ASP.NET/VB.NET) create a subscription but not with the Report Manager. Any
ideas?have you checked who you are logged into report manager as. What user. do
they have permissions to create a schedule?
"mbianco21" wrote:
> While on the Report Delivery Options page if I click "Select Schedule" or
> "OK" nothing happens; no error message, no postback, nothing in the logs,
> nothing in a SQL Trace. I cannot create a File Share nor an e-mail
> subcription.
> I am able to programmaticaly (using ReportServer WebService and
> ASP.NET/VB.NET) create a subscription but not with the Report Manager. Any
> ideas?sql

Cannot Create Subscription

Using RS Standard, SP2, I am prevented from creating a subscription on
reports that I am able to schedule for snapshots. The error message says
"Subscriptions cannot be created because the credentials used to run the
report are not stored, the report is using user-defined parameter values, or
if a linked report, the report is no longer valid." There are no linked
reports involved, and there are both report parameters and query parameters,
but all have supplied values or defaults. (Since a snapshot works fine, it
would seem that criteria for a subscription would be satisfied). This is a
major problem for my users who believe subscription delivery is an essential
feature. Please help!
--
Bob RogersThen the only part of the error message your response didn't cover is the
credentials... They must be stored securely in the database... Go to the
datasource, and you may set the connection stuff to be stored in the
database... Then subscriptions can be made.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Rogers" <BobRogers@.discussions.microsoft.com> wrote in message
news:1D97E909-7A7A-4617-ABF0-0610CF43B863@.microsoft.com...
> Using RS Standard, SP2, I am prevented from creating a subscription on
> reports that I am able to schedule for snapshots. The error message says
> "Subscriptions cannot be created because the credentials used to run the
> report are not stored, the report is using user-defined parameter values,
> or
> if a linked report, the report is no longer valid." There are no linked
> reports involved, and there are both report parameters and query
> parameters,
> but all have supplied values or defaults. (Since a snapshot works fine,
> it
> would seem that criteria for a subscription would be satisfied). This is
> a
> major problem for my users who believe subscription delivery is an
> essential
> feature. Please help!
> --
> Bob Rogers|||Thanks for your reply. The database credentials were good; the problem
turned out to be user id being included in the template for report footer --
user id is apparently considered a parameter.
--
Bob Rogers
"Wayne Snyder" wrote:
> Then the only part of the error message your response didn't cover is the
> credentials... They must be stored securely in the database... Go to the
> datasource, and you may set the connection stuff to be stored in the
> database... Then subscriptions can be made.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Bob Rogers" <BobRogers@.discussions.microsoft.com> wrote in message
> news:1D97E909-7A7A-4617-ABF0-0610CF43B863@.microsoft.com...
> > Using RS Standard, SP2, I am prevented from creating a subscription on
> > reports that I am able to schedule for snapshots. The error message says
> > "Subscriptions cannot be created because the credentials used to run the
> > report are not stored, the report is using user-defined parameter values,
> > or
> > if a linked report, the report is no longer valid." There are no linked
> > reports involved, and there are both report parameters and query
> > parameters,
> > but all have supplied values or defaults. (Since a snapshot works fine,
> > it
> > would seem that criteria for a subscription would be satisfied). This is
> > a
> > major problem for my users who believe subscription delivery is an
> > essential
> > feature. Please help!
> > --
> > Bob Rogers
>
>

Monday, March 19, 2012

Cannot create new database in Sql Server Management Studio

I am getting error message when trying to create a new database. I just recently installed sql server express and express mgmt studio. Everything loads up fine and I can enter the name of the database however once I click Ok, I get the error message:

Create failed for Database 'Student'. (Microsoft.SqlServer.Express.Smo)

Additional information:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

CREATE DATABASE permission denied in database 'master'.

(Microsoft SQL Server, Error: 262)

Any help is appreciated.

You are probably not a member of the db_creator role in SQL Server as creating a database require writing some entries in the system catalog (master database).

Cannot create diagrams in Upgraded SQL Server 2000 Database

Dear all,

I am trying to save a newly created diagram in SQL Server 2005 SP1.

The error message is:
-Beginning of pasted error message

===================================

Cannot insert the value NULL into column 'diagram_id', table 'adt_db.dbo.sysdiagrams'; column does not allow nulls. INSERT fails.
The statement has been terminated.
The 'sp_creatediagram' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. (.Net SqlClient Data Provider)

Program Location:

at Microsoft.VisualStudio.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DatabaseDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)

-End of pasted error message

The database I use has been upgraded from SQL Server 2000.

I am running in SQL Server 2000 Compatibility Mode (80) but changing the compatibility mode to SQL Server 2050 (90) does not make any difference with regards to this error.I solved the problem by deleting the table dbo.sysdiagrams and letting SQL Server 2005 re-create it. Apparently, its schema was different.|||

????CONGRATULATIONS!!!!

And thank you very, very much. I had desesperated to resolve this problem with my diagram of forty three tables, that i think that i don′t save it, but you resolve my problem with a simple solution, the eternal "restart", or recreate the table in this case.

Thank you very much another time,

Zapa