More Related Resource Links

Hello,
I'm consuming a web service through assemblies in a Sql Server 2005 database. The client was made with VB.net 2005. Everything was fine in the deploy phase but once I compile the assembly generated in my sql server database and try to execute
the CLR stored procedure defined in the assembly it crashes throwing the following error:
Error: There was an error generating the XML document.
Inner Exception: Item has already been added. Key in dictionary: 'SqlCifin.InfoComercial.ParametrosConsultaDTO' Key being added: 'SqlCifin.InfoComercial.ParametrosConsultaDTO'
Where SqlCifin is the name of the assembly, InfoComercial is the web reference namespace and ParametrosConsultaDTO is a complex type defined in the WSDL to encapsulate the request parameters.
I tried almost everything but nothing seems to work: Already checked the enviroment variables and .
I would appreciate any help you can provide me.
PD: I'm using WSE 3.0.
Thanks,
Andres Diab.

Hi everybody,
I hope some of you will be able to help me regarding this datetime problem. The query in the stored procedure doesn't accept DD/MM/YYYY format, although all dates are being saved in the format of DD/MM/YYYY hh:mm:ss.
Example of query that throws the error:
@sDate = '31/8/2010'
@eDate = '1/9/2010'
SELECT * FROM tb_Schedule where scheduledate >= @sDate and scheduledate <= @eDate
Error: The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value
FYI, the SQL Server 2005 is defaulted to British English(2057)for all logins and the DB server itself and my server Regional and Language is set to English (United Kingdom).
Any help will be appreciated.
Thank you very much.

I have a stored procedure that creates a dynamic query. Sometimes the query is not built because there are no elements in the dynamic query. When the aspx page loads the SqlDataSource throws an error that the query is malformed. How can I catch this error, and handle it with a default message, before it returns the error to the aspx page?

I have as stored procedure which executes a dynamic SQL at the end. The dynamic SQL inserts into a temporary table declared at the begining of the procedure. When i execute the proc, it executes for a while and then gives me a truncation error.

When i test the code witht out the proc, it works fine and come back with the result set. I am not able to figure out what culd be the issue.

Kindly assist me in this..I have tried setting all colum lenghts to very high values then required but still it does not work when i execute the proc.

I am using a CLR stored procedure to call a webservice. I have marked the project as strongly named assembly and also created a serialization assembly using Generate Serialization assembly in VS 2008. It created both files which I copied on to the
database server. I have created assemblies of both

We have been presenting an issue randomly since we changed our replication to use custom stored procedures for replication.

We have several offices which replicate to our central datacenter, each of this offices have different data corresponding only to their site and we centralize the data from all databases in only one database.

We use custom stored procedures for some tables only for the insert method, but randomly the update method of that table drops and I have to create again. We have been set the replication by using the 'replication support only' method so it only creates
the replications sp. All our articles have the create update, insert and delete stored procedures for replication.

We have done traces for this and the replications is generating the drop but it doesn't recreate the procedure. It only occurs for the articles with custom procs for insert.

I am wirting a stored procedure, which basically just has some SQL Statements. In one line I am Casting to XML and inserting. Everything works good, but if an un formatted XML comes in the whole SP fails. I want to know a mechanism where by I can control
this so what ever records are well formatted should pass through, and the ones that fail should be recorded in some other table something like Error table to just insert ID of the records that failed. Any suggestions. So end result is that SP should run successfully
for well formatted XML documents and record ID in some other table for Failed ones.

I have implemented a stored procedure in SQL Server 2005. I need to capture the possible errors. I have written an Insert To ... Select statement, so I read a row block from a Table1 to insert it into a Table2. But I could have an error, f.e. a conversion
error. I want to capture the row of the block that has generated the error for the insert. Is it possible? How?

I have a report which uses a stored procedure to retreive a resource intensive dataset from a Data Warehouse. With a small scope it renders in SharePoint no problem, but when a larger scope is specified ShrePoint throws this non-descript error.

I can execute the procedure in SQL Server Management Studio, and though it takes 2+ minutes with the larger scope (30 sec with smaller) it does return the data. Similarly, in Business Intelligence Development Studio it returns the rendered report with
data after 2-3 minutes.

Only in SharePoint and only with a larger dataset does this occur. Timeout is set at 30 minutes and it occurs long before then. SSRS server has over 12 gigs memory, running SQL Server 2008, SharePoint 2007 is in integrated mode. No
errors in SharePoint server or SSRS server logs. Ideas?

I have a report which uses a stored procedure to retreive a resource intensive dataset from a Data Warehouse. With a small report it renders in SharePoint no problem, but when a larger scope is specified ShrePoint throws this non-descript error.

I can execute the procedure in SQL Server Management Studio, and though it takes 2+ minutes with the larger scope (30 sec with smaller) it does return the data. Similarly, in Business Intelligence Development Studio it returns the rendered report with
data after 2-3 minutes.

Only in SharePoint and only with a larger dataset does this occur. Timeout is set at 30 minutes and it occurs long before then. SSRS server has over 12 gigs memory, running SQL Server 2008, SharePoint 2007 is in integrated mode. No
errors in SharePoint server or SSRS server logs. Ideas?