Script Task, Debugger Stops And Waits Indefinitely
Jul 7, 2006
Hello,
I have MS SQL Server 2005 with SP1 installed, version 9.0.2047
I am trying to debug a Script Task in SSIS.
I have break point on the first line of the code.
SSIS runs and eventually launches MS Visual Studio for Applications.
Line with the break point is highlighted in yellow.
After that Visual Studio is frozen. F5, F11 or any other key press produces a popup which says the following:
Delay notification.
Microsoft Visual Studio for Applications is waiting for an operation to complete. If you regularly encounter this delay during normal usage please report this problem to Microsoft. Please include a description of the work you were doing in Microsoft Visual Studio for Applications and when possible instructions how to reproduce this delay.
If Microsoft Visual Studio for Applications is waiting on another application you can switch to that application now, or you can continue waiting for this operation to complete.
The popup has to buttons: [Switch to€¦] and [Continue Waiting]
None of the buttons allows to proceed.
Any idea what causes Microsoft Visual Studio for Applications to a complete halt?
We are running sql 6.5 with Serv. pack 4. All of our Prod. database are backedup weekly via scheduled tasks. On occasion the dump of a particular database will cause 1 of 2 things: 1. The db dump seems to work correctly but stops sql executive service. 2. The db dump seems to work correctly but sends an alert email msg to me indicating that it failed. The msg in the email is "NO Message".
Has anyone experienced either of these 2 problems or have any solutions?
This would actually be funny if I weren't under serious time constraints right now. I have an SSIS project with several script tasks in the control flow. I put breakpoints in one of them to allow me to step through and see whats going on. However, when I start the project, the IDE brings up the script editor for a different script task. The breakpoints in this task are actually on the same line numbers as the task I need to debug but the code is all wrong. I checked the task for which the code is being displayed and there are no breakpoints there.
I'm trying to put together an SSIS package that will look in one directory for 2 distinctly named .csv files. The files will then be loaded into 2 tables.Â
The first task I execute is a SQL Task that checks to see if the tables I'm loading the data into are empty. If the tables have data, the package stops executing. If they are empty, the package continues to execute.
What is the best way to send an email out from SSIS if the package stops on the first step?Â
I`m using IIS7..At present, our company has come not a difference indeyo of operating the server using Classic ASP recently we met a big problem : session is increases indefinitely. 503.3 - ASP.net has a queue is full. The phrase occurs continuously. Is there any solution for check problems? or how can i see what source code page makes the problem (ex. 123.asp : session 300. 234.asp : session 4000).
Iam new to this forum, Hello to all... Iam facing a problem in my application. Have recently noticed that my primary key column which is an " identity " with increment 1 being set. But now iam noticing a various jumps in the number instead of 1. The numbers in the jump is not consistent. Has anyone faced this kinda problem. ?????
My intention is to include a sql job to schedule for shrinking log files to half of its original log file size (if half of their original size is greater than 5MB)
The code is below. But while executing the code it is keeps on running indefinitely. can somebody throw some light what cause it to go into an indefinite loop.
Thanks Babu
code: ==== DECLARE db_file_name CURSOR FOR SELECT name , ceiling(size/128.0) * 0.5 FROM master..sysaltfiles Where rtrim(lower(filename)) like '%.ldf'
DECLARE @f_name varchar(128), @new_f_size int
OPEN db_file_name FETCH NEXT FROM db_file_name INTO @f_name,@new_f_size WHILE @@FETCH_STATUS = 0 BEGIN If ( @new_f_size > 5) BEGIN DBCC SHRINKFILE ( @f_name, @new_f_size ) FETCH NEXT FROM db_file_name INTO @f_name,@new_f_size END END CLOSE db_file_name deallocate db_file_name
We see an unusual case where a query seems to be taking a long time (more than 30 minutes) as shown by the Java thread dump (below) - however the SQL server DB does'nt show any corresponding Connection for the query at the lower layer.
The JDBC layer seems to be "in progress" as far as processing the results of the query are concerned. If the Connection was dropped or had a failure we should have seen a corresponding SQLException in the JDBC layer - which is also not the case.
Any tips on how to debug this? Is there a timeout set on the JDBC Connection which causes it to wait before it detects any failures?
thanks
"JMS Session Delivery Thread" daemon prio=6 tid=0x0000000006434780 nid=0x868 run nable [0x0000000020d6e000..0x0000000020d6f860] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.microsoft.sqlserver.jdbc.DBComms.receive(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePrep aredStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedState mentExecutionRequest.executeStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source ) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unkno wn Source) - locked <0x00000000955574e0> (a com.microsoft.sqlserver.jdbc.TDSWriter)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate (Unknown Source) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Del egatingPreparedStatement.java:101) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Del egatingPreparedStatement.java:101) at org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAc cessImpl.java:213) at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(Persistenc eBrokerImpl.java:2021) at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro kerImpl.java:977) at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro kerImpl.java:1014) at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro kerImpl.java:884) at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeAndLinkOneToOne (PersistenceBrokerImpl.java:1074) at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeReferences(Pers istenceBrokerImpl.java:1050) at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(Persistenc eBrokerImpl.java:1981) at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro kerImpl.java:977) at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro kerImpl.java:1014) at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro kerImpl.java:884) at org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(Delegati ngPersistenceBroker.java:220) at org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(Delegati ngPersistenceBroker.java:220) at org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(Delegati ngPersistenceBroker.java:220) at com.serus.db.ojbutils.SerusPersistenceBrokerHandle.store(SerusPersist enceBrokerHandle.java:178) at com.serus.common.OJBDAOUtil.store(OJBDAOUtil.java:636) at com.serus.dao.wip.AbsWipDAO.saveDTO(AbsWipDAO.java:251) at com.serus.dao.wip.tx.LotTXDAO.saveLotTx(LotTXDAO.java:56) at com.serus.manager.wip.txprocessing.AbstractTxProcessorImp.storeLotTx( AbstractTxProcessorImp.java:1380) at com.serus.manager.wip.txprocessing.LotTxProcessingMoveStage.storeLotT x(LotTxProcessingMoveStage.java:802) at com.serus.manager.wip.tx.LotTxManager.saveLotTx(LotTxManager.java:248 ) at com.serus.manager.wip.tx.LotTxXMLProcessor.parseMessageOriginal(LotTx XMLProcessor.java:137) at com.serus.manager.wip.tx.LotTxXMLProcessor.parseMessage(LotTxXMLProce ssor.java:78) at com.serus.events.listener.SerusJMSListener.onSerusMessage(SerusJMSLis tener.java:197) at com.serus.events.listener.AbstractEventListener.onMessage(AbstractEve ntListener.java:53) at progress.message.jimpl.Session.deliver(Unknown Source) at progress.message.jimpl.Session.run(Unknown Source) at progress.message.jimpl.Session$SessionThread.run(Unknown Source)
Last Sunday on our Primary server I saw some blocking and the First spid that blocked everything was waiting on LogBuffer wait. At that time the server was not running hot and our DB is on SSD's. There was no memory pressure(1 TB of memory on the server) It is strange why we should get LogBuffer wait when we are running on the fastest disks possible and there was not much action going on the DB.
Hello to all,I have a small question.I call the SP outer the DB. The procedure deletes some record in tableT1.The table T1 has a trigger after delete.This is very importand for me, that the SP will be finished ASAP,that's why, I do not want, and I do not need to wait for a trigger.Does the SP will be finished, after the trigger is finished?Means, does the SP "waits" for a trigger?I think it is like that. Is it anyhow possible, to set the trigger (orthe procedure) that it want's be waiting for a result of triggerexecution?Thank You for kindly replyMateusz
I have a query that keeps on waiting with a wait type of SOS_SCHEDULER_YIELD. I have checked for the CPU pressure as well, and there is nothing else running. The query outline is given below.
Select a,b,c,d....
FROM tableA A inner join tableB B on A.a = B.b
inner join tableC on B.c = C.c
where
a.x not in (SELECT x from tableX where y = '???')
I have restored the copy of prod DB on a DEV box and ran the query which runs fine. But the prod box which is more powerful chokes. DEV is a 4CPU/4GB box and PROD is 8CPU/32GB box. All other DB and Server settings are exactly the same. DEV is SQL 2005 Standard ed SP2. Prod is a SQL 2005 Enterprise ed SP2.
Back in the days of SQL 7.0 I used a lot of ODBC SELECT querying form VB applications, in which I implemented NOLOCK in order to prevent the primary business applications from being locked out of tables once the queries were run.
Now, quite a few years later, I'm busying myself converting a lot of old Access based forms and queries to TSQL on SQL-Server 2000, and wonder aimlessly why NOLOCK queries (simple select ones) are imensely slower than a standars select clause.
SELECT * FROM employees
This would be much much faster than the code below, but users would get "The current record could not be accessed, as it is being used by another user", evidently because I'm locking the record while producing the output.
SELECT * FROM employees (nolock)
So this could should - as I remember it - do a dirty read on table, not obstructing other users and give me a snapshot of date as they are, although they might be locked for edit.
Could anyone explain to me why the nOLOCK query fials to give me any output? It is as if the nolock request is waiting for the table/records to free? In which case I'll never be able to run a query.
About a month ago I setup mirroring with our DB, High safety with automatic failover. Ever since the lock waits per minute in the DB went from maybe 2-5 per minute to 22-25 per minute. I am not sure if this was expected or what; but sometimes it spikes even higher than that.
Does this sound off the charts to anyone or normal for mirroring?
I am trying to find out what could be causing this issue. Why would we be waiting on cpu when its barely being used. Signal waits are varying from 35 to 55% and cpu usage is only at 5% usage.We are using Windows Server 2012 with SQl Server 2012 Standard edition with cpu5. There are 3 instances on the server each with max memory 50gb memory and the server has a total of 190gb memory. The machine is a 12 core machine with hyperthreading enabled.
I have a 2GHZ cpu with 1GB of RAM. I occassionally see very slow (long) queries against a local SQL Server 2005 Express (SP2) database. The issue occurs against different SQL Queries, but all queries are rather basic select statements Perfmon shows that the SQL Server counter for the "MEMORY GRANT QUEUE WAIT Avg MS" gets extremely high (25000+ ms). Perfmon also also shows that PAGING is not occuring, and the system is not under unsual stress. The problem is not reproducible with MSDE.
Has anyone seen this issue, or have any recommendations for a next course of action?
Anyone know of any third party T-SQL debuggers for stepping through stored procedures? I understand there is one with VB6, but a student in my class doesn't work with VB. TIA.
Hi, I've just read in books on line that in Query Analyser there is a debugger tool. Unfortunately I can't work out how to access and use it. Can any one send me some info on this please.
Once I open my TSQL Debugger all the icons are disables ( Step Into , Step Over ). This is the fisrt time I am using it can you please point be in the right direction.
This happens after giving the Input parameters in the Dubug Window for the Stored Procedure and when I click the EXECUTE button.
NOTE : This happeds when I lauch the Debugger from the ClIENT Machines. If I run the debugger on the server directly it works fine. Am I missing any of the DLLs
I'm trying to get the T-SQL Debugger to work between SQL Server 7 and Visual Studio 6.0.
First of all, I am confused by the various articles I have read in MSDN. Some indicate that the debugger will work in Visual Basic and some indicate Visual Interdev. Does it work in both environments? After following all of the steps listed in the MSDN articles I cannot get the T-SQL Debugger to appear in my Add-Ins window in Visual Basic. Is there something else I need to do?
Secondly, I can see my stored procedures in Visual Interdev and once I open one in the editor the only commands enabled on the DEBUG menu are Clear All Breakpoints, Breakpoints... and Processes.... According to one of the MSDN articles I should see all of the DEBUG menu commands enabled. Any ideas what I can do to get the rest of the menu commands enabled?
Also, I can set a breakpoint in a stored procedure by clicking in the gray area to the left of the line of code where I want the debugger to stop. The red dot appears next to the line of code. But when I execute the stored procedure the debugger asks for the parameters but never stops at the breakpoint. It runs the stored procedure to completion.
I would appreciate any ideas on how to get this working.
Can anyone tell me besttool for debugging the Stored Procedure user friendly. We are using Powerbuilder/Sql Server 6.5 as back end. we got lots of stored procedures and I am having tough time in debugging. I actually moved from Oracle and don't know much about Sqlserver just started learning.
If anyone tell me best tool,method for doing then I will be very greatful
I can get the debugger to work: I get a message:"sp debugging may not work if you log as as Local System Account" whileSQL Service is configured to run as a service. You can open Event Viwerto see details." (Viwer means "Viewer" this is not one of my typos...)My text book says that this message means there is a problem that canbe fixed in the SQL Server registration node (just under the servergroup in Enterprise Manager), Properties dialog, Security tab, Start UpService.The book says to enter a valid user account and password in the StartUp Service area. However, there is in my case a "LocalSystem" and anencrypted password entered in this area and and I have no idea howthese got in there.I assume the latter are default settings from when SQL wasinstalled...Can I can this to "sa" and no password? I'm afraid tochange the existing setting if I don't understand what it is and whereit came from..Thank you **very** much for help...I would like to use the debugger.J.
Hi,When I debug our sp by using T-SQL Debugger, I got following error.Server: Msg 229, Level 14, State 5, Procedure sp_sdidebug, Line 1[Microsoft][ODBC SQL Server Driver][SQL Server]EXECUTE permissiondenied on object 'sp_sdidebug', database 'master', owner 'dbo'.and when I grant the permission of sp_sdidebug, I got following error.Server: Msg 4610, Level 16, State 1, Line 1You can only grant or revoke permissions on objects in the currentdatabase.I am using following statement to grant the permission.GRANT EXECUTEON sp_sdidebugTO myuserHere, I want to clear, myuser is I, which one i log QA.and myuser has public and dbowner permission--Rahul
I'm using the Transact-SQL Debugger for the first time here.I go to Object Browser, find my stored procedure, right click andchoose "Debug".The "Debug Procedure" window comes up, and I click on the Executebutton.The Debug environment comes up and automatically executes myprocedure. It doesn't allow me to single step through the code.What am I missing here?All of the "step" buttons, "restart", and "stop debugging" buttonsare dimmed out.Thanks.Ken
I am using Visual Studio 2005, and I go to server explorer and make a new connection to a database. I select a stored procedure and right mouse click.
There is no menu item called "Step Into ... " in the pop up menu. So what am I missing? Do I have to install or set up something in order to use Transact SQL Debugger?
Any pointer or answer is greatly appreciated. Thanks a lot.
I installed the SQL 2000 trial as a local server on a standalone XP Pro system. When use the debugger, it executes the stored procedure without allowing me to step into the code.
I am trying to debug a t-SQL function. I am supposed to have both Enterprise Manager for SQL 2000, and Management Studio for SQL 2005, on my computer. In the books-online for SQL 2000 there is a reference to a T-SQL debugger which does all the things that you'd expect: checkpoints, ablility to stop and examine data, etc. I don't seem to have books-online for SQL 2005 - I merely get "help on Help" which is rather useless.Anyway, how do I get this debugger to work? I can't find anything in either Enterprise Manager or Management Studip.Thanks, Robert Barnes
hi all I'm working on a complicated activex script which is a part of a DTS package. Are there some debuggers around that could help make the task easier? Specifically I'm looking for an ActiveX script debugger. Can somebody point me to a tutorial or something? Regards
Transact-sql debugger comes with sqlserver 2000. I checked my server and all the dll;s are loaded correctly, sqldbreg process is running. I also configured the client correctly. How do I invoke this debugger? Which settings you change to get to the toolbar for the debugger in query anayl..
At Sql Server Live, I saw Sharon Dooley using the debugger in Query Analyzer, but now that I've tried it I can't step an sp, instead, I get....Quote:
SP debugging may not work properly if you log on as 'Local System account' while SQL Server is configured to run as a service. You can open Event Viwer to see details.
Do you wish to continue?
End Quote:
I'm logged in at a W2Kpro box connectig via client tools to a W2KSVR box via Integrated NT security. SS2K is NOT installed locally.
