DB mail not working in sql server 2005

Hi,
from today i get following error on sql server 2005
Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException
Message: There was an error on the connection. Reason: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void OpenConnection(Microsoft.SqlServer.Management.Common.SqlConnectionInfo)
I can not send the mail.I am sending the mails same profile that configured.Before it is working perfectly.Today I send the bulk mails(near about 4000-5000 mails) through the java code. And from that time i can not get any mails.
Please tell me how to solve the problem?

Hello,
Please refer to the following thread:
https://social.technet.microsoft.com/Forums/en-US/c8fa3c2d-9e8a-4886-97bf-264c1b8bc31c/throttling-settings-for-sending-more-that-1500-emails-simultaneously-using-sql-job?forum=exchangesvrsecuremessaging
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Database Mail not working with SQL Server Agent

I'm running SQL Server 2005 Standard edition 64 bit with SP2 on a 64 bit machine.
Database mail does not work with SQL Server Agent. When I configure SQL Server Agent to use database mail the test email button is greyed out and inactive therefore I cannot send emails using operators or for jub success failure etc.
I've read that there was supposed to be a fix for this with SP1 but I have SP2 and still receive the same problem. Please can somebody help as I do not wish to use SQL Mail as a work around due to this becomming redundant in future versions of SQL Server.
Kind Regards

The problems solved
steps:
1)we create a mail profile at at Managment->Database Mail ,of SQL Managment
2)we set this account as "default" at Managment->Database Mail -> Configure Database Mail -> Manage profile security
3)At tab "Alert System" of SQL Server Agent properties , we check the "Enable mail profile" , Mail System=Database Mail, Mail profile = "the profile we already create"
4)we create a new operator at "Operators" of sql agent, where at "notification options" -> "Email name" we put the mail where we want to sent the agent the mails at failured job
5)We go at a specific job, at tab "Notifications" ,we check the "email" check box and then we choose the operator we just create, at the text box next to check box.
I hope not to forget something
Thank You all for the help

XP_DELETE_FILE NOT WORKING IN SQL SERVER 2005 SP2

Hi All,
I have one job in sql 2005 sp2 that deletes backup older than one week.It is not working.I have checked service account permissions on backup folder and all required permissions and authentications are in place.Please let me know how to troubleshoot the
same.
Regards
Rahul

Check the following:
http://stackoverflow.com/questions/212603/sql-server-xp-delete-file-not-deleting-files
QUOTE: "Note that xp_delete_file is broken in SP2 and won't work on report files;"
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Non Clustered Indexing not working for SQL server 2005

I have create two non clustered index on two particular tables. Now the problem is its working fine..but after restarting my server its working stop and then again I have to delete that index and recreate it.

try these links
http://blog.sqlauthority.com/2009/02/07/sql-server-introduction-to-force-index-query-hints-index-hint/
http://blog.sqlauthority.com/2009/02/08/sql-server-introduction-to-force-index-query-hints-index-hint-part2/
http://www.brentozar.com/archive/2013/10/index-hints-helpful-or-harmful/
Hope it Helps!!

EXEC SP_EXECUTESQL not working in sql server 2014

EXEC SP_EXECUTESQL not working in sql server 2014

EXEC SP_EXECUTESQL not working in sql server 2014
Hi Amar,
What's the error when executing this stored procedure?
I have tested it on my local environment, we can run this SP without any problems.
Please provide us more information, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

SQL Server Agent - Job History not being recorded (SQL Server 2005)

I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
returns an error, detailed below.
Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
Many thanks in advance for anyone's time and help with this issue!
Arthur
The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
===================================
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
Server Name: 127.0.0.1,1344
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
at sqlprov.MainForm.ProvisionTasks()

Hi Rama,
Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
active directory controller, etc) so I don't understand how the Windows login cannot be verified.
Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
Many thanks!
Arthur

Addon in Client is not connecting to SQL Server 2005

Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
Does anyone knows how to fix this issue?
Thanks

Hi Alejandro, thanks for your response.
After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
I had checked the SQL to confirm is was allowing remote connections.
Thank you guys.

Distributed transaction using linked server not working in SQL Server 2008 64 bit

Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
My Environment:
Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
None of the mentioned resolutions has solved this problem for me.
I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

Hi All,
I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
In the EventViewer I found Error entry logged by MSDTC saying:
"The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
So I followed suggestion and run:
msdtc -uninstall
msdtc -install
This solved my problems with DTC. Hope it will help someone.
Piotr

Package developed on SQL Server 2005 SP1 not opening in SQL Server 2005 SP2

Recently I have upgraded my system to SQL Server 2005 SP2 version 9.00.3054; I have developed my packages on SQL Server 2005 SP1 version 9.00.2047. I am unable to open all these packages on SQL Serever SP2 version 9.00.3054 it is giving me error.
Error: Error loading Package.dtsx cannot create an instance of the XML Document Object Model. MSXML may not be registered.
Can any body help me in this?
Thanks in advance

Try the search function.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1446338&SiteID=1

Arc is not implemented for SQL Server 2005 physical model

I added the Arc in my relational model, which is supposed to provide that references are mutually exclusive (so only one refering column can be not null). However there is not any implementation for this in the SQL Server 2005 physical model. The SQL code generated simply ignores the Arc and allows any values for the columns covered by Arc. If we check Oracle physical model. then it generates some trigger, which controls how many columns have values assigned - this is actually an implementation of Arc. But there is nothing of this kind for SQL Server model...
By the way, implementing this Arc by trigger looks like to heavy approach. The very simple table level check constraint will do the same job. But this is a different subject though.
Edited by: Otbl on Nov 3, 2011 7:34 PM

Hi Dmitry,
it's fixed in Data Modeler 3.1 EA2.
Philip

Does OBI SE1 work with SQL server 2005

Does anybody know if SQL Server 2005 can be used with OBIEE?
Any responses would be appreciated.

Yes. Create a new database in the physical layer of the rpd and open the "Database" dropdown in the "Data source definition"...not the "SQL Server 2005" entry there.
Cheers,
C.

Working with SQL Server 2005

We are trying to use SQL Server 2005 with JSC2. Got the JDBC driver from Microsoft and added the sqljdbc.jar and created new database server too.
What else to be done to connect ? Want to make use of the interoperability of these products quickly
Thanks
Prasath

Here is URL related to database access FAQ.
http://developers.sun.com/prodtech/javatools/jscreator/reference/faqs/technical/dbaccess/
Take a look at
11. How do I configure data sources for Oracle, Sybase, SQL Server, or DB2 in the Java Studio Creator IDE?

Why is the LookUp object in the Flow Task of my SSIS package going red (and not working) ? Sql Server 2008 R2

I have been working with the Sql Server 2008 R2 SSIS Tutorial at
https://msdn.microsoft.com/en-us/library/ms170419(v=sql.105).aspx
--specifically -- Lesson 1. I have been having some problems with this lesson where the source data from the samples download doesn’t exactly match the data described in the tutorial, and the tables in the tutorial are different from what
is contained in AdventureWorksDW (tutorial refers to DimTime – AdventureWorksDW contains DimDate and no DimTime).
So, after futzing in BI with this tutorial so that I can at least get it to run in Debug – it errors out on the 2nd LookUp object.
Rather than looking for a fix to the problem(s) that I am having between the tutorial and the stuff I downloaded in the samples --
I want “Adapt” the tutorial so I can use the stuff I downloaded and hopefully learn how to use SSIS with the elements (source data and tables) that are present on my workstation.
Here is a description of what is going on for me – which I really don’t understand what is going on in BI – based on the images below – like what columns (from what tables) are they associating to in the OleDB Destination?
Note: the sql in the LookUps here is the sql that I copied from the tutorial.
I probably need to modify these sql statements – so -- the help I am requesting is to make the required modifications/changes
so that I can adapt this tutorial with the stuff that’s on my workstation.
I downloaded the samples and the AdventureWorksDW mdf for Sql Server 2008 R2.
It turns out that in the tutorial it wants me to select a DimTime table, but the version of the AdventureWorksDW db does not contain a DimTime table.
Instead, it contains a DimDate table. So I tried adapting DimDate for the tutorial.
Additionally, the sample data file -- SampleCurrencyData.txt -- has slightly different data types than the types described in the tutorial, so I selected data types for the columns in the datasource text file that would work in BI would to
connect column from source data file to the table.
After finishing all the steps for Lesson 1 -- when I tried debugging the package – and it error'd out on the 2nd Lookup object whichwent red.
 I edited the lookups and the sample Ole DB Destination to "ignore on fail” and I did all
green but the FactCurrencyRate table is not being populated -- as described in the tutorial, so I reset the on error back to default (Fail on error option). And based on this tutorial -- I believe FactCurrencyRate
table is the table which is supposed to be populated with the data from SampleCurrencyData.txt?
In the sample data file that downloaded with all the samples I removed all the data from the text file except for 6 rows, so instead of the original 1100 or so rows, I have only 6 rows of data in the source data file (just to keep things
simple for debugging for now). I did not modify the data itself.
Here is what the (raw) data contained in SampleCurrencyData.txt looks like (from the samples that I downloaded from codeplex) – it’s supposed to be 4 columns of data – float, nvarchar, datetime, float:
0.281690141 USD
6/26/2004 0:00 0.281713948
0.281690141 USD
6/27/2004 0:00 0.281642539
0.281690141 USD
6/28/2004 0:00 0.281761573
0.283286119 USD
6/29/2004 0:00 0.283221933
0.283286119 USD
6/30/2004 0:00 0.283358363
0.281690141 USD
7/1/2004 0:00 0.281682206
Below are images of my BI Layout for Lesson 1 from this tutorial -- the FlatFile and configurations for On Fail Error, A Flow task, the 2 LookUps (CurrencyKey and DataKey), the OleDB Destination configuration, the Design view of the associated tables and
the Debug Run of Lesson 1, and the following error messages. My goal is to figure out what is going on in BI for this tutorial.
Error: 0xC020901E at Extract Sample Currency Data, Lookup Datakey [51]: Row yielded no match during lookup.
Error: 0xC0209029 at Extract Sample Currency Data, Lookup Datakey [51]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
The "component "Lookup Datakey" (51)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Match Output" (53)" specifies failure on error. An error occurred on the specified
object of the specified component. There may be error messages posted before this with more information about the failure.
Error: 0xC0047022 at Extract Sample Currency Data, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED.
The ProcessInput method on component "Lookup Datakey" (51) failed with error code 0xC0209029 while processing input "Lookup Input" (52). The identified component returned an error from the ProcessInput method. The error is specific
to the component, but the error is fatal and will cause the Data Flow task to stop running.
There may be error messages posted before this with more information about the failure.
--this is the flat file
-- SampleCurrencyData.txt (which only contains 6 data rows for my purposes)
--and here is where I assign the data types for the colums of -- SampleCurrencyData.txt
This is the first LookUp Object -- LookUp Currency Key – The DB contains DimCurrency table.
I copied the sql from the tutorial here.
I actually have a DimCurrency table in my copy of AdventureWorksDW.
Here’s the design view of DimCurrency and a sample of the data contained in DimCurrency and the On Fail configuration
I actually have a DimCurrency table in my copy of AdventureWorksDW.
Here’s the design view of DimCurrency and a sample of the data contained in DimCurrency and the On Fail configuration
--Here is what the data looks like in the DimCurrency table
--2nd LookUp object -- LookUp Data Key – this is the LookUp
where BI errors out on Debug
--it appears this lookup is referencing the DimDate table – which I DO have in the DB.
--I can’t find the following sql in the tutorial, so I suppose BI added the sql (did it?)
--Here's how I configured for On Error
--Here is DimDate table in Design view
--Here is a sample of the original data contained in DimData
OleDB Destination
--Here is where I get lost a bit – what is going on in the destination here?
--Here's my On Error configuraino
--and here is the FactCurrencyRate table
--and here is a sample of the data contained in FactCurrencyRate
Rich P

Thank you for your reply. I changed the error handling as you suggested on the 2nd lookup to redirect to unmatched rows. Now I get all greet. I don't have the conditional split as in your diagram. But also, nothing appears to have
happened in the DB. Aren't the rows in my text file supposed to be added to the FactCurrencyRate table?
How do I get a conditional split?
Rich P
OK, sorry I forgot to reply you back.
Conditional Split was just dummy task. Ignore it.
Manipulate the data in such way that you get matching records.
Inside Source, for first 2 rows I put the dates which are available in DimDate.
1.00010001,ARS,7/1/2005 0:00,0.99960016
1.00010001,ARS,2/5/2006 0:00,1.001001001
1.00020004,ARS,9/5/2001 0:00,0.99990001
1.00020004,ARS,9/6/2001 0:00,1.00040016
1.00050025,ARS,9/7/2001 0:00,0.99990001
1.00050025,ARS,9/8/2001 0:00,1.001001001
Then in OLE DB Destination, I loaded the rows to TestFactTable.
(Now, you don't even need NO MATCH OUTPUT as there are matching records here)
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP]

SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

I am working in a Product based company.
We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
I have used "Script Component" in my package.
We will take only DTSX package file to the customer places and run using SQL Agent Job daily.
Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
Who are all(Customer Environments) using SQL 2012, I am facing the below issue
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Still the same package is running fine for some of the customers having SQL 2012.
I am getting the above error only for few customers.
Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

Hi Katherine,
I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
Here is my Simple .net code
/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
public override void PreExecute()
base.PreExecute();
Add your code here for preprocessing or remove if not needed
public override void PostExecute()
base.PostExecute();
Add your code here for postprocessing or remove if not needed
You can set read/write variables here, for example:
Variables.MyIntVar = 100
int counter = 0;
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (counter == 0)
counter = Convert.ToInt32(Row.JurisCount);
Row.JurisKey = counter;
counter = counter + 1;
PAVAN MSBI

DB mail not working in sql server 2005

Similar Messages

Maybe you are looking for