I'm trying to debug stored procedure code with SSDT, but the debugger don't stop at the breakpoint.
I imported the schema of northwind database from Denali to a new database project and used Run to publish it to localdb.
So, I inserted a breakpoint in SalesByCategory stored procedure, opened a new query window, write an execute statement and started the execution with debug.
The debugger stop at the exec statement, but never get into the stored procedure. I'm using a breakpoint in the stored procedure, already tryed F5, F11, nothing works.
Application Debugging option in localdb is checked.
The operating system is windows server 2008 R2. I'm still using CTP 3.
SSIS 2008 when I develop and debug in BIDS sometimes ignores debug break point.
The script component is in the main control flow and at some point the breakpoint did work.
If, for example, I create a new project and copy my script component there the debug breakpoint will work.So it's absolutely *random* when it works and when it does not.
Below is my BIDS detail:
Microsoft Visual Studio 2008 Version 9.0.30729.4462 QFE Microsoft .NET Framework Version 3.5 SP1 Installed Edition: IDE Standard Enterprise Library v5 Configuration Editor  4.0
My SQLAgent keeps failing with a DR. Watson message(see above) with differen addresses. Sometimes the SQL Agent will restart and other times it stays down.
I get no messages in the Agent Log or the SQL Server log. I get one message in the NT Event Log "SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly".
Running NT 4 sp 5 w SQL 7 w sp 2. If you look at the NT Services, it shows that SQLAgent is still running. But SQL Enterprise manager shows it stopped.
If you try to look at a scheduled job or a DTS package, you get the message that SQL Agent is starting and to try back later.
Have stopped the NT Services SQL Agent and then tried to start it with Enterprise manager. No luck. Only way that I have found to get out of this mess is to restart the server.
I am still pretty new to SSIS, SQL, and DOT NET. I came from the UNIX world. I have a SSIS package. On the Control Flow one of the Items I have is a Script Task. I was able to successfully set breakpoints in the Script Task and they worked fine. I could step through the script and check values in variables. Life was good.
Now something happened. I set the breakpoint, from the menu I select €œstart with debugging€? and I get the following window:
----------------------------- - Visual Studio Just-In-Time Debugger
An unhandled exception (€˜System.Runtime.InteropServices.COMException€™) occurred in DTAttach.exe [3380].
Possible Debuggers:
New instance of Microsoft CLR Debugger 2003 New instance of Visual Studio .NET 2003 New instance of Visual Studio 2005
[_] set the currently selected debugger as the default [_] Manually choose the debugging engines
Do you want to debug using the selected debugger?
----------------------------------------------------------- I have tried selecting Yes, but that doesn€™t work. If I delete all breakpoints the package runs fine. I greatly appreciate your help.
I'm having an issue with trying to delete breakpoints in my SSIS package. I think the breakpoints were created when I added dataviewers through my process, however the breakpoints were not deleted when I removed the dataviewers. It would then appear that my process would not halt on ANY breakpoints - orphaned or valid.
Furthermore, whenever I tried deleting the breakpoints manually, my whole IDE would crash. I got around the issue by closing the dtsx page first, then deleting the breakpoints, and reopening my dtsx.
Are these valid bugs with SSIS? Has anyone else experienced this? I'm running this against a SQL Server 2005 database using VStudio 2005 as an IDE.
I have a child package which is executed several times within the same SSIS ETL. I have placed a break point on one of the child package's tasks, set to trigger on a PreExecute() event. The first time the child package is invoked, the breakpoint is triggered. However, on each successive invocation the breakpoint is ignored. Does anybody know if this behaviour is normal? Thanks in advance!
I ran into a variety of problems trying to set a script task breakpoint in a package containing multiple script tasks. The debugger apparently treats the breakpoint as if it were set in ALL tasks in the package, not just the one in which it is actually set.
At best this results in hitting breakpoints in scripts where they are not set and at worst the debugger brings up the "Send error report" dialog and quits (while the package continues to run). The latter seems to happen most often when the script with the breakpoint has more lines than an earlier script and the breakpoint is set at a line number that exceeds the number of lines in the earlier script--it bombs when the earlier, shorter script starts.
To get the debugger to work under these circumstances I had to add some nonsense code like
While False Dim i as Integer = 0 End While to every script, at the same line number near the beginning of the script (line 40, for example). I then set a breakpoint on the middle statement in one of the scripts (doesn't matter which) to cause the debugger to open at runtime. It doesn't hit the breakpoint because the line is never executed. If the breakpoint is set on a line that can be executed in any script in the package, bad things tend to happen. I then add a "stop" statement to the script that I want to debug. This only works if the debugger is already open, hence the dummy breakpoint above. This workaround is usable, but I am debugging a package that has quite a few scripts and having to insert dummy code in all of them at a fixed line number is rather inconvenient. I would really like to see breakpoints work the way one would expect--only in the scripts where they are set. Is there some other, easier way around this problem? Is there at least an easier way to get the debugger to open so that "stop" will work?
Hi, I am unsure whether i can delete some system created tables from a database.
I was testing replication and then used the wizard to disable it all. I am however left with three tables that are replication based that have not been deleted. they are : MSreplication_subscriptions MSsubscriptions_agents MSsubscriptions_properties
these tables are causing problems with some third party software due to the length of their names. I have tried to 'Exec sp_rename' but i get an error saying the objects are not valid for this operation.
Can i just delete them or will this cause problems if i want to start up replication in the future?
In query analyser, I can stop a script with the "return" statement butif the script contains multiple batches (separated by GO) then thereturn statement only stops the current batch.Is there a way to stop the whole script?
Anyone got any "gotchas" or "nightmares" they want to share out of experience where the services have been shutdown without the proper forethought?
I'm trying to put a case in for a SQL DBA to be paged and to be in charge of shutting down the services and/or put together a checklist of things to verify first.
While I realize shutting down the services is supposed to be a graceful shutdown process I'm willing to bet there are a host of considerations.
hi, i am having sql7 with sp2. Recently our server got bounced back. No body stopped the server, there are no work load at that time. Server suddenly stopped and started. It is weired. Can anyone have any clues , how it happened and why it happened. Thanks!
Recently upgraded a 6.5 server to a 7.0 server. (same server) When we try to stop the 6.5 service, the 7.0 service stops too. Why is this happening? Aren't the 6.5 and 7.0 installations supposed to be independent of each other once the upgrade is done.
Further we would like to uninstall the 6.5 server from the machine as it is no longer being used. What considerations need be taken into account in our scenario.
I've been running SQL Server for 5 years now and have not seen the following.
We have a scheduled night run task where we do various maintenance functions as well as print out the issued insurance policies for the day. All indications are that the run completed except that I did not get an email notification of success or failure.
When I went to enterprise manager, under jobs the night run seems to be stuck in the mode of "Performing completion actions". I cannot get it our of this mode back to "Not running". Trying to stop the task has no effect.
Any ideas/suggestions??
Thanks in advance.
Cheers, Mike Byrd Information Systems Manager Texas Windstorm Insurance Association Austin, Texas
What is the command to stop a stored procedure from continuing to run? I have a procedure that has a problem, and due to a bug it runs wild in some scenarios, so I need to be able to stop it.
I have searched google and have found no real answer to this....
We are creating a database to support an application which is loading in data as part of the cutover from their current db to SQL Server.
The datafile is around 56GB and when the data processing occurs, as its not just inserts, the transaction logs fills out to around 65GB, and probably more, just that we ran out of space. So question is, is there a workaround for stopping the logging of this processing at all. I have seen that bulk-logged mode may be used, but the option with TABLOCK must be used, and there is no way to get hands on code which performs this processing.
Is there a way to turn off transaction loggin at any point?
I have a SQL Server agent that keeps stopping for no reason. It happens about every other day. I have to go in on the server and manually start it. What would cause this to happen? We have about 50+ computers that need to sync with the server and do so successfully without having to manually start the agent every other day. How do we fix it?
We have a console.php which takes in SQL queries and displays them in aresult.php webpage.Sometimes the query takes minutes to execute or crashes the PHPapplication. Is it possible to cancel a query during execution?If yes, how does one go about it.The PHP Console is used by multiple users simultaneously.The queries are executed on a Remote Database.
My problem is primarily with SQL backup but the instant question is with mirroring in SQL 2005. I have a log file that is out of control and I need to do a backup with truncate_only, but this is command is evidently disallowed while mirroring is enabled. Is it possible to temporarily deactivate or remove mirroring in order to get the backup log under control? Is it possible to do that and then 'resume' mirroring?
A secondary issue is that I don't think mirroring is actually working at this point in time anyway. In the Mirroring section of the database properties the Status window says "No connection: cannot connect to the mirror server instance," so the question of stopping and restarting may be moot.
How does one reestablish mirroring if the connection is lost?
Lots of questions, I know... I'm reading up on it, but I'm obviously not the guy who set it up in the first place! Thanks in advance for any help...
Maybe I'm just totally not getting it, but can someone tell me how to stop/start the distribution agent? The Books Online document - "How to: Start and Stop a Replication Agent (SQL Server Management Studio)" - shows how to stop/start the Snapshot Agent, Log Reader Agent and Queue Reader Agent, but not the Distribution Agent. Is it that stopping one of these agents in turn stops the Distribution Agent. I am trying to work through how to add an article to a peer-to-peer topology and need to stop the agent as part of that.
Hi am trying to create a snapshot (Merge replication) - My database is approx 6GB and one of my tables has 14.5M records - I have a total of 1500 articles to replicate.
When I start creating the snapshot - it seems to just stop on the Table that has the 14.5M records. When I delete all the data in that table it works fine. I have also check disk space and also the log files and tempdb size and all seem ok.
I am using SQL 2005 with the latest SP
Is there any form of verbose logging that I could enable to let me see what is going on
I cannot set a breakpoint in a Script task and have it complete successfully. I am running Vista 32-bit and only the workstation tools for SQL Server 2005 SP2. The steps to recreate are:
1) Create a new SSIS project/package. 2) Add a Script Task. 3) Set a breakpoint in the Script Task. 4) Run the package.
When I remove the breakpoint, the script task succeeds. When I put it back the task fails. The execution results say "Error: The script files failed to load." I completely uninstalled all SQL Server 2005-related entries using the Programs and Features control panel, rebooted, reinstalled the Workstation Tools, then applied a freshly-downloaded SQL Server 2005 SP2 and rebooted. If I change "RecompileScriptIntoBinaryCode" to false the script fails whether there's a breakpoint or not. If it's true (the default), the script only fails when a breakpoint is set. I would like to be able to set a breakpoint to assist in debugging the package. For the time being, I can move the package to a different (non-Vista) OS, where it works fine, but I would like to be able to develop and debug on Vista.
I am using a drop down list box to select values from an SQL 2000 DB. I have put a record into the table which says"...Select Item"I used the dots so that It will apear at the top of the list and therefore display at startup. I also have a gridview to allow users to edit and delete from the same table.I am worried that a user may accidently delete the "...Select Item" row from the table.Can anyone think of a way round this? Is it possible with SQL Server 2000 to stop a single record from being deleted?Any help would be most appreciated.ThanksPaul
What problems could be invoked by stopping SQL Server and copying a user databases data and log files and pasting these files over existing files on another machine.
Ex: MyDB on Server1 MyDB on Server2 Stop SQL Server Server1 and Server2 Copy Server1.MyDB files Over write Server2.MyDB files Start SQL Server Server1 and Server2
Make sense. This scenerio seems to work but wonder what side affects could result.
If I stop MSSQLServer service on my SQL7 server using net stop and then restart it seconds later with net start, how will this affect my users ? Will they notice this ? Gets disconnected ?
