[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.inetserver.asp.db

michael kors factory outlet as58

Katadedajab

12/26/2013 2:06:00 PM

<a href=http://ibmu.org/><b&... kors bags outlet</b></a>If the affected individual comes back then she or he usually really yours. If he / she doesn't, wish him skillfull There is this : do nothing more than nobody who loves him more than you Never despair.<a href=http://freebyb.com/><b&... kors outlet</b></a>I think that going to be the websites all around the going to be the a minumum of one hand allows students to educate yourself regarding share their knowledge,all of which allows for to learn more about maximize academic performance. On going to be the all the other hand,students can addicted for more information regarding your corporation.<a href=http://freebyb.com/><b&... kors outlet</b></a>Congratulations! It is because never too age - old for more information regarding learn. graduation is not very the end including learning.to explore going to be the contrary,some of these is the fact that a good deal more knowledge waiting our way of life to learn more about master it.<a href=http://ibmu.org/><b&... kors outlet</b></a>its allow you to have ultimate and reliable process to explore refuse spam websites!its aware the user exactly how comment unnecessary and send going to be the your small business to educate yourself regarding spam categary<a href=http://ibmu.org/><b&... kors purses</b></a>Can you point me to explore an internet site products or services or at least software that helps finding new blogs and forum posts related for more information about our SEO keywords. If its a software a resource box needs to learn more about run all over the a Mac
6 Answers

William Vaughn

8/9/2007 5:29:00 PM

0

Ah, I don't have the time and you don't have the patience to wait until I
do... ;)
Nothing is ever "always bad" just as nothing is "always good". XML has its
place. It's just been misused by too many that should know better.
Client transactions put too much schema-dependent, business-rule-dependant
code on the client. I think more logic should be run from a common platform.
I discuss these issues in most of my books--even the latest. See Chapter 1
that discusses architectures...

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Lit" <sql_agentman@hotmail.com> wrote in message
news:eDMn4Fq2HHA.728@TK2MSFTNGP05.phx.gbl...
> William,
>
> What about when you have to process and send lists?
> I know I can send XML to SQL
> Is it always a bad reason to do client transactions?
> Can you tell me more about your "bad" experience of client transactions I
> am all ears.
> I would love to hear some good or bad stories so I can decide what to do.
>
> Thank you,
>
> Lit
>
>
>
> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
> news:O%23fHn8h2HHA.5164@TK2MSFTNGP05.phx.gbl...
>> If it were me I would probably call a stored procedure that started the
>> transaction ran all of the SPs, handled the exceptions, channeled the
>> logic and returned success or failure via RETURN... but that's just me.
>> I'm not a fan of client-side transactions...
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant, Dad, Grandpa
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com
>> www.betav.com/blog/billva
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> "Lit" <sql_agentman@hotmail.com> wrote in message
>> news:e0$W7bg2HHA.6072@TK2MSFTNGP03.phx.gbl...
>>> Hello,
>>>
>>> using ADO.NET 2.0, VS.NET 2005, SQL2005
>>> I need to execute several Stored Procedures under one transaction. Can
>>> I use just one transaction or have to use multiple ( then commit or
>>> rollback all )
>>> How does it work with ADO.NET
>>>
>>> Ado.Tran
>>> SP1 Called
>>> loop
>>> SP2 Called
>>> SP3 Called
>>> loop
>>> SP4 Called
>>> loop
>>> Sp5 Called
>>> Etc... etc...
>>>
>>> if any error
>>> rollback transaction ( or all transactions )
>>> else
>>> committe Transaction ( or all Transactions )
>>>
>>> Thanks for any help or other Ideas
>>>
>>> Lit
>>>
>>>
>>>
>>>
>>
>
>

CSharp Agentman

8/9/2007 5:49:00 PM

0

William,

You are right about "always", What is the name of your latest book?

Thank you,

Lit

"William Vaughn" <billvaNoSPAM@betav.com> wrote in message
news:efidUrq2HHA.3400@TK2MSFTNGP03.phx.gbl...
> Ah, I don't have the time and you don't have the patience to wait until I
> do... ;)
> Nothing is ever "always bad" just as nothing is "always good". XML has its
> place. It's just been misused by too many that should know better.
> Client transactions put too much schema-dependent, business-rule-dependant
> code on the client. I think more logic should be run from a common
> platform.
> I discuss these issues in most of my books--even the latest. See Chapter 1
> that discusses architectures...
>
> hth
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "Lit" <sql_agentman@hotmail.com> wrote in message
> news:eDMn4Fq2HHA.728@TK2MSFTNGP05.phx.gbl...
>> William,
>>
>> What about when you have to process and send lists?
>> I know I can send XML to SQL
>> Is it always a bad reason to do client transactions?
>> Can you tell me more about your "bad" experience of client transactions I
>> am all ears.
>> I would love to hear some good or bad stories so I can decide what to do.
>>
>> Thank you,
>>
>> Lit
>>
>>
>>
>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>> news:O%23fHn8h2HHA.5164@TK2MSFTNGP05.phx.gbl...
>>> If it were me I would probably call a stored procedure that started the
>>> transaction ran all of the SPs, handled the exceptions, channeled the
>>> logic and returned success or failure via RETURN... but that's just me.
>>> I'm not a fan of client-side transactions...
>>>
>>> --
>>> ____________________________________
>>> William (Bill) Vaughn
>>> Author, Mentor, Consultant, Dad, Grandpa
>>> Microsoft MVP
>>> INETA Speaker
>>> www.betav.com
>>> www.betav.com/blog/billva
>>> Please reply only to the newsgroup so that others can benefit.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> __________________________________
>>> Visit www.hitchhikerguides.net to get more information on my latest
>>> book:
>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>> -----------------------------------------------------------------------------------------------------------------------
>>>
>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>> news:e0$W7bg2HHA.6072@TK2MSFTNGP03.phx.gbl...
>>>> Hello,
>>>>
>>>> using ADO.NET 2.0, VS.NET 2005, SQL2005
>>>> I need to execute several Stored Procedures under one transaction. Can
>>>> I use just one transaction or have to use multiple ( then commit or
>>>> rollback all )
>>>> How does it work with ADO.NET
>>>>
>>>> Ado.Tran
>>>> SP1 Called
>>>> loop
>>>> SP2 Called
>>>> SP3 Called
>>>> loop
>>>> SP4 Called
>>>> loop
>>>> Sp5 Called
>>>> Etc... etc...
>>>>
>>>> if any error
>>>> rollback transaction ( or all transactions )
>>>> else
>>>> committe Transaction ( or all Transactions )
>>>>
>>>> Thanks for any help or other Ideas
>>>>
>>>> Lit
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>


William Vaughn

8/9/2007 6:08:00 PM

0

"Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)" (Addison
Wesley).
I hope it helps.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Lit" <sql_agentman@hotmail.com> wrote in message
news:Oqz%23Y2q2HHA.2752@TK2MSFTNGP06.phx.gbl...
> William,
>
> You are right about "always", What is the name of your latest book?
>
> Thank you,
>
> Lit
>
> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
> news:efidUrq2HHA.3400@TK2MSFTNGP03.phx.gbl...
>> Ah, I don't have the time and you don't have the patience to wait until I
>> do... ;)
>> Nothing is ever "always bad" just as nothing is "always good". XML has
>> its place. It's just been misused by too many that should know better.
>> Client transactions put too much schema-dependent,
>> business-rule-dependant code on the client. I think more logic should be
>> run from a common platform.
>> I discuss these issues in most of my books--even the latest. See Chapter
>> 1 that discusses architectures...
>>
>> hth
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant, Dad, Grandpa
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com
>> www.betav.com/blog/billva
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> "Lit" <sql_agentman@hotmail.com> wrote in message
>> news:eDMn4Fq2HHA.728@TK2MSFTNGP05.phx.gbl...
>>> William,
>>>
>>> What about when you have to process and send lists?
>>> I know I can send XML to SQL
>>> Is it always a bad reason to do client transactions?
>>> Can you tell me more about your "bad" experience of client transactions
>>> I am all ears.
>>> I would love to hear some good or bad stories so I can decide what to
>>> do.
>>>
>>> Thank you,
>>>
>>> Lit
>>>
>>>
>>>
>>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>>> news:O%23fHn8h2HHA.5164@TK2MSFTNGP05.phx.gbl...
>>>> If it were me I would probably call a stored procedure that started the
>>>> transaction ran all of the SPs, handled the exceptions, channeled the
>>>> logic and returned success or failure via RETURN... but that's just me.
>>>> I'm not a fan of client-side transactions...
>>>>
>>>> --
>>>> ____________________________________
>>>> William (Bill) Vaughn
>>>> Author, Mentor, Consultant, Dad, Grandpa
>>>> Microsoft MVP
>>>> INETA Speaker
>>>> www.betav.com
>>>> www.betav.com/blog/billva
>>>> Please reply only to the newsgroup so that others can benefit.
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> __________________________________
>>>> Visit www.hitchhikerguides.net to get more information on my latest
>>>> book:
>>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>>> -----------------------------------------------------------------------------------------------------------------------
>>>>
>>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>>> news:e0$W7bg2HHA.6072@TK2MSFTNGP03.phx.gbl...
>>>>> Hello,
>>>>>
>>>>> using ADO.NET 2.0, VS.NET 2005, SQL2005
>>>>> I need to execute several Stored Procedures under one transaction.
>>>>> Can I use just one transaction or have to use multiple ( then commit
>>>>> or rollback all )
>>>>> How does it work with ADO.NET
>>>>>
>>>>> Ado.Tran
>>>>> SP1 Called
>>>>> loop
>>>>> SP2 Called
>>>>> SP3 Called
>>>>> loop
>>>>> SP4 Called
>>>>> loop
>>>>> Sp5 Called
>>>>> Etc... etc...
>>>>>
>>>>> if any error
>>>>> rollback transaction ( or all transactions )
>>>>> else
>>>>> committe Transaction ( or all Transactions )
>>>>>
>>>>> Thanks for any help or other Ideas
>>>>>
>>>>> Lit
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>

CSharp Agentman

8/9/2007 6:56:00 PM

0

William,

This is NOT going to help me right now, it may in the future?
I am under time constraint to get things going.
I was only looking for some good pattern or guidelines to what would be best
to send large lists to SQL2005 via ADO.NET 2.0 ( Max of 3000 rows )

Thank You,

Lit

"William Vaughn" <billvaNoSPAM@betav.com> wrote in message
news:ufDr8Ar2HHA.5832@TK2MSFTNGP02.phx.gbl...
> "Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)"
> (Addison Wesley).
> I hope it helps.
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "Lit" <sql_agentman@hotmail.com> wrote in message
> news:Oqz%23Y2q2HHA.2752@TK2MSFTNGP06.phx.gbl...
>> William,
>>
>> You are right about "always", What is the name of your latest book?
>>
>> Thank you,
>>
>> Lit
>>
>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>> news:efidUrq2HHA.3400@TK2MSFTNGP03.phx.gbl...
>>> Ah, I don't have the time and you don't have the patience to wait until
>>> I do... ;)
>>> Nothing is ever "always bad" just as nothing is "always good". XML has
>>> its place. It's just been misused by too many that should know better.
>>> Client transactions put too much schema-dependent,
>>> business-rule-dependant code on the client. I think more logic should be
>>> run from a common platform.
>>> I discuss these issues in most of my books--even the latest. See Chapter
>>> 1 that discusses architectures...
>>>
>>> hth
>>>
>>> --
>>> ____________________________________
>>> William (Bill) Vaughn
>>> Author, Mentor, Consultant, Dad, Grandpa
>>> Microsoft MVP
>>> INETA Speaker
>>> www.betav.com
>>> www.betav.com/blog/billva
>>> Please reply only to the newsgroup so that others can benefit.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> __________________________________
>>> Visit www.hitchhikerguides.net to get more information on my latest
>>> book:
>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>> -----------------------------------------------------------------------------------------------------------------------
>>>
>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>> news:eDMn4Fq2HHA.728@TK2MSFTNGP05.phx.gbl...
>>>> William,
>>>>
>>>> What about when you have to process and send lists?
>>>> I know I can send XML to SQL
>>>> Is it always a bad reason to do client transactions?
>>>> Can you tell me more about your "bad" experience of client transactions
>>>> I am all ears.
>>>> I would love to hear some good or bad stories so I can decide what to
>>>> do.
>>>>
>>>> Thank you,
>>>>
>>>> Lit
>>>>
>>>>
>>>>
>>>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>>>> news:O%23fHn8h2HHA.5164@TK2MSFTNGP05.phx.gbl...
>>>>> If it were me I would probably call a stored procedure that started
>>>>> the transaction ran all of the SPs, handled the exceptions, channeled
>>>>> the logic and returned success or failure via RETURN... but that's
>>>>> just me. I'm not a fan of client-side transactions...
>>>>>
>>>>> --
>>>>> ____________________________________
>>>>> William (Bill) Vaughn
>>>>> Author, Mentor, Consultant, Dad, Grandpa
>>>>> Microsoft MVP
>>>>> INETA Speaker
>>>>> www.betav.com
>>>>> www.betav.com/blog/billva
>>>>> Please reply only to the newsgroup so that others can benefit.
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>> __________________________________
>>>>> Visit www.hitchhikerguides.net to get more information on my latest
>>>>> book:
>>>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>>>> -----------------------------------------------------------------------------------------------------------------------
>>>>>
>>>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>>>> news:e0$W7bg2HHA.6072@TK2MSFTNGP03.phx.gbl...
>>>>>> Hello,
>>>>>>
>>>>>> using ADO.NET 2.0, VS.NET 2005, SQL2005
>>>>>> I need to execute several Stored Procedures under one transaction.
>>>>>> Can I use just one transaction or have to use multiple ( then commit
>>>>>> or rollback all )
>>>>>> How does it work with ADO.NET
>>>>>>
>>>>>> Ado.Tran
>>>>>> SP1 Called
>>>>>> loop
>>>>>> SP2 Called
>>>>>> SP3 Called
>>>>>> loop
>>>>>> SP4 Called
>>>>>> loop
>>>>>> Sp5 Called
>>>>>> Etc... etc...
>>>>>>
>>>>>> if any error
>>>>>> rollback transaction ( or all transactions )
>>>>>> else
>>>>>> committe Transaction ( or all Transactions )
>>>>>>
>>>>>> Thanks for any help or other Ideas
>>>>>>
>>>>>> Lit
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>


William Vaughn

8/9/2007 7:47:00 PM

0

Okay, there is no good way to use ADO.NET query classes to do bulk uploads.
There are other ways however. The SqlBulkCopy class can take anything you
can expose with a DataReader (DataTable to DataReader is supported in 2.0)
and send it to SQL Server in a single high-speed operation.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Lit" <sql_agentman@hotmail.com> wrote in message
news:Oaencbr2HHA.5980@TK2MSFTNGP04.phx.gbl...
> William,
>
> This is NOT going to help me right now, it may in the future?
> I am under time constraint to get things going.
> I was only looking for some good pattern or guidelines to what would be
> best to send large lists to SQL2005 via ADO.NET 2.0 ( Max of 3000 rows )
>
> Thank You,
>
> Lit
>
> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
> news:ufDr8Ar2HHA.5832@TK2MSFTNGP02.phx.gbl...
>> "Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)"
>> (Addison Wesley).
>> I hope it helps.
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant, Dad, Grandpa
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com
>> www.betav.com/blog/billva
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> "Lit" <sql_agentman@hotmail.com> wrote in message
>> news:Oqz%23Y2q2HHA.2752@TK2MSFTNGP06.phx.gbl...
>>> William,
>>>
>>> You are right about "always", What is the name of your latest book?
>>>
>>> Thank you,
>>>
>>> Lit
>>>
>>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>>> news:efidUrq2HHA.3400@TK2MSFTNGP03.phx.gbl...
>>>> Ah, I don't have the time and you don't have the patience to wait until
>>>> I do... ;)
>>>> Nothing is ever "always bad" just as nothing is "always good". XML has
>>>> its place. It's just been misused by too many that should know better.
>>>> Client transactions put too much schema-dependent,
>>>> business-rule-dependant code on the client. I think more logic should
>>>> be run from a common platform.
>>>> I discuss these issues in most of my books--even the latest. See
>>>> Chapter 1 that discusses architectures...
>>>>
>>>> hth
>>>>
>>>> --
>>>> ____________________________________
>>>> William (Bill) Vaughn
>>>> Author, Mentor, Consultant, Dad, Grandpa
>>>> Microsoft MVP
>>>> INETA Speaker
>>>> www.betav.com
>>>> www.betav.com/blog/billva
>>>> Please reply only to the newsgroup so that others can benefit.
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> __________________________________
>>>> Visit www.hitchhikerguides.net to get more information on my latest
>>>> book:
>>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>>> -----------------------------------------------------------------------------------------------------------------------
>>>>
>>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>>> news:eDMn4Fq2HHA.728@TK2MSFTNGP05.phx.gbl...
>>>>> William,
>>>>>
>>>>> What about when you have to process and send lists?
>>>>> I know I can send XML to SQL
>>>>> Is it always a bad reason to do client transactions?
>>>>> Can you tell me more about your "bad" experience of client
>>>>> transactions I am all ears.
>>>>> I would love to hear some good or bad stories so I can decide what to
>>>>> do.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Lit
>>>>>
>>>>>
>>>>>
>>>>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>>>>> news:O%23fHn8h2HHA.5164@TK2MSFTNGP05.phx.gbl...
>>>>>> If it were me I would probably call a stored procedure that started
>>>>>> the transaction ran all of the SPs, handled the exceptions, channeled
>>>>>> the logic and returned success or failure via RETURN... but that's
>>>>>> just me. I'm not a fan of client-side transactions...
>>>>>>
>>>>>> --
>>>>>> ____________________________________
>>>>>> William (Bill) Vaughn
>>>>>> Author, Mentor, Consultant, Dad, Grandpa
>>>>>> Microsoft MVP
>>>>>> INETA Speaker
>>>>>> www.betav.com
>>>>>> www.betav.com/blog/billva
>>>>>> Please reply only to the newsgroup so that others can benefit.
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>> __________________________________
>>>>>> Visit www.hitchhikerguides.net to get more information on my latest
>>>>>> book:
>>>>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>>>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>>>>> -----------------------------------------------------------------------------------------------------------------------
>>>>>>
>>>>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>>>>> news:e0$W7bg2HHA.6072@TK2MSFTNGP03.phx.gbl...
>>>>>>> Hello,
>>>>>>>
>>>>>>> using ADO.NET 2.0, VS.NET 2005, SQL2005
>>>>>>> I need to execute several Stored Procedures under one transaction.
>>>>>>> Can I use just one transaction or have to use multiple ( then commit
>>>>>>> or rollback all )
>>>>>>> How does it work with ADO.NET
>>>>>>>
>>>>>>> Ado.Tran
>>>>>>> SP1 Called
>>>>>>> loop
>>>>>>> SP2 Called
>>>>>>> SP3 Called
>>>>>>> loop
>>>>>>> SP4 Called
>>>>>>> loop
>>>>>>> Sp5 Called
>>>>>>> Etc... etc...
>>>>>>>
>>>>>>> if any error
>>>>>>> rollback transaction ( or all transactions )
>>>>>>> else
>>>>>>> committe Transaction ( or all Transactions )
>>>>>>>
>>>>>>> Thanks for any help or other Ideas
>>>>>>>
>>>>>>> Lit
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>

CSharp Agentman

8/9/2007 9:29:00 PM

0

William,

I am hoping this is it.
I found an example of importing to an entire table.
I am hoping to be able to insert into a exiting table that has an identity
field.

Thanks for taking the time I appreciate it.

Lit


"William Vaughn" <billvaNoSPAM@betav.com> wrote in message
news:eYG9Z4r2HHA.5696@TK2MSFTNGP02.phx.gbl...
> Okay, there is no good way to use ADO.NET query classes to do bulk
> uploads. There are other ways however. The SqlBulkCopy class can take
> anything you can expose with a DataReader (DataTable to DataReader is
> supported in 2.0) and send it to SQL Server in a single high-speed
> operation.
>
> hth
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "Lit" <sql_agentman@hotmail.com> wrote in message
> news:Oaencbr2HHA.5980@TK2MSFTNGP04.phx.gbl...
>> William,
>>
>> This is NOT going to help me right now, it may in the future?
>> I am under time constraint to get things going.
>> I was only looking for some good pattern or guidelines to what would be
>> best to send large lists to SQL2005 via ADO.NET 2.0 ( Max of 3000 rows )
>>
>> Thank You,
>>
>> Lit
>>
>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>> news:ufDr8Ar2HHA.5832@TK2MSFTNGP02.phx.gbl...
>>> "Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)"
>>> (Addison Wesley).
>>> I hope it helps.
>>>
>>> --
>>> ____________________________________
>>> William (Bill) Vaughn
>>> Author, Mentor, Consultant, Dad, Grandpa
>>> Microsoft MVP
>>> INETA Speaker
>>> www.betav.com
>>> www.betav.com/blog/billva
>>> Please reply only to the newsgroup so that others can benefit.
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> __________________________________
>>> Visit www.hitchhikerguides.net to get more information on my latest
>>> book:
>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>> -----------------------------------------------------------------------------------------------------------------------
>>>
>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>> news:Oqz%23Y2q2HHA.2752@TK2MSFTNGP06.phx.gbl...
>>>> William,
>>>>
>>>> You are right about "always", What is the name of your latest book?
>>>>
>>>> Thank you,
>>>>
>>>> Lit
>>>>
>>>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>>>> news:efidUrq2HHA.3400@TK2MSFTNGP03.phx.gbl...
>>>>> Ah, I don't have the time and you don't have the patience to wait
>>>>> until I do... ;)
>>>>> Nothing is ever "always bad" just as nothing is "always good". XML has
>>>>> its place. It's just been misused by too many that should know better.
>>>>> Client transactions put too much schema-dependent,
>>>>> business-rule-dependant code on the client. I think more logic should
>>>>> be run from a common platform.
>>>>> I discuss these issues in most of my books--even the latest. See
>>>>> Chapter 1 that discusses architectures...
>>>>>
>>>>> hth
>>>>>
>>>>> --
>>>>> ____________________________________
>>>>> William (Bill) Vaughn
>>>>> Author, Mentor, Consultant, Dad, Grandpa
>>>>> Microsoft MVP
>>>>> INETA Speaker
>>>>> www.betav.com
>>>>> www.betav.com/blog/billva
>>>>> Please reply only to the newsgroup so that others can benefit.
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>> __________________________________
>>>>> Visit www.hitchhikerguides.net to get more information on my latest
>>>>> book:
>>>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>>>> -----------------------------------------------------------------------------------------------------------------------
>>>>>
>>>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>>>> news:eDMn4Fq2HHA.728@TK2MSFTNGP05.phx.gbl...
>>>>>> William,
>>>>>>
>>>>>> What about when you have to process and send lists?
>>>>>> I know I can send XML to SQL
>>>>>> Is it always a bad reason to do client transactions?
>>>>>> Can you tell me more about your "bad" experience of client
>>>>>> transactions I am all ears.
>>>>>> I would love to hear some good or bad stories so I can decide what to
>>>>>> do.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Lit
>>>>>>
>>>>>>
>>>>>>
>>>>>> "William Vaughn" <billvaNoSPAM@betav.com> wrote in message
>>>>>> news:O%23fHn8h2HHA.5164@TK2MSFTNGP05.phx.gbl...
>>>>>>> If it were me I would probably call a stored procedure that started
>>>>>>> the transaction ran all of the SPs, handled the exceptions,
>>>>>>> channeled the logic and returned success or failure via RETURN...
>>>>>>> but that's just me. I'm not a fan of client-side transactions...
>>>>>>>
>>>>>>> --
>>>>>>> ____________________________________
>>>>>>> William (Bill) Vaughn
>>>>>>> Author, Mentor, Consultant, Dad, Grandpa
>>>>>>> Microsoft MVP
>>>>>>> INETA Speaker
>>>>>>> www.betav.com
>>>>>>> www.betav.com/blog/billva
>>>>>>> Please reply only to the newsgroup so that others can benefit.
>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>> rights.
>>>>>>> __________________________________
>>>>>>> Visit www.hitchhikerguides.net to get more information on my latest
>>>>>>> book:
>>>>>>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>>>>>>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>>>>>>> -----------------------------------------------------------------------------------------------------------------------
>>>>>>>
>>>>>>> "Lit" <sql_agentman@hotmail.com> wrote in message
>>>>>>> news:e0$W7bg2HHA.6072@TK2MSFTNGP03.phx.gbl...
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> using ADO.NET 2.0, VS.NET 2005, SQL2005
>>>>>>>> I need to execute several Stored Procedures under one transaction.
>>>>>>>> Can I use just one transaction or have to use multiple ( then
>>>>>>>> commit or rollback all )
>>>>>>>> How does it work with ADO.NET
>>>>>>>>
>>>>>>>> Ado.Tran
>>>>>>>> SP1 Called
>>>>>>>> loop
>>>>>>>> SP2 Called
>>>>>>>> SP3 Called
>>>>>>>> loop
>>>>>>>> SP4 Called
>>>>>>>> loop
>>>>>>>> Sp5 Called
>>>>>>>> Etc... etc...
>>>>>>>>
>>>>>>>> if any error
>>>>>>>> rollback transaction ( or all transactions )
>>>>>>>> else
>>>>>>>> committe Transaction ( or all Transactions )
>>>>>>>>
>>>>>>>> Thanks for any help or other Ideas
>>>>>>>>
>>>>>>>> Lit
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>