Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
bojesphob
Starting Member
2 Posts |
Posted - 2009-06-18 : 20:36:05
|
So.....I have a project in VS.Net that accesses SQL Server 2008. I also have all of the data access functionality going through a stored procedure for each and every item. Yesterday, I was working on the project and went to test a stored procedure that inserts data into a table, and it attempted to, said it was successful, but when I attempt to look at the data it inserted into the table, I saw that said transaction didn't exist. Now, I found that the identity field that I have in that table had advanced one, so it inserted, but did not keep the record. But, I went in and ran the same exact query in Enterprise Manager and it inserted fine. After much racking of the brains, I finally remembered that I could see, in detail, everything I would want to know about what's going on in the data realm by using SQL Profiler, including rollbacks and whatnot. Well, I finally figured out why the records weren't going in:TM: Begin Tran completed BEGIN TRANSACTION .Net SqlClient Data Provider RPC:Starting exec dbo.InsertRedemptionManualEdit @iMemberId=xxxx,@iLocationId=x,@iExplanationId=x,@iDateOfRequest='2009-06-16 00:00:00' RPC:Completed exec dbo.InsertRedemptionManualEdit @iMemberId=xxxx,@iLocationId=x,@iExplanationId=x,@iDateOfRequest='2009-06-16 00:00:00'TM: Rollback Tran starting ROLLBACK TRANSACTION .Net SqlClient Data Provider Now, why, oh why, would ADO.Net take it upon itself to Rollback the transaction that I just ran?????? Or is this a setting in SQL?? It does this when I'm in the .xsd Preview Data for that stored procedure, and it does it when I actually run the website that I'm working on as well! Also, this occurs on three different systems, one that I just installed Visual Studio on this afternoon and created a new project with nothing in it but a connection and an xsd file, with just one insert connection in it. It's also happening on two separate SQL 2008 servers as well. Anyone have any ideas?? This had to happen when we are supposed to go live with this site next week, and it's taken me almost 2 days to figure out where the failure is! Any help would be GREATLY appreciated! |
|
bojesphob
Starting Member
2 Posts |
Posted - 2009-06-19 : 13:24:18
|
Nevermind, this ended up being an I d 10 T error. |
|
|
|
|
|
|
|