flat file source and destination - need fixed width output

I have a text file that is comma delimited and im pulling it in with a flatfile connection manager. I want to read some of the data, then output another flat file but in a fixed column width. What settings do I made to the connection manager of the output flatfile ?Choose a fixed-width format when setting up the destination. And then define your columns.|||

Hi

A solution is:

- Go to advanced properties of output flat file.

- Define the fields as text and the property OutputColumnWith with the size you want

- Export your data to that file and convert it to text.

Raul

|||I had some other steps in the middle, so I took them out just to simplify things. In the connection mgr for my destination, it wants to know the input column widths. Should I really need to bother with this, since in the end, I just want whatever output i get during any previous steps, to simply be output to the flat file as fixed width ?|||Ok, ive managed to get my output in fixed width in the output file, but it appears the lines arent terminating where they should be. What controls where the lines terminate ? I dont have a header row (no column names in the first row), so what, if anything should the "header row" settings be set to ?|||Ive got a data file with values seperated with commas. I want to read in this text file, do a lookup and add the lookup column on the front of the other columns and save the output in a fixed width format, similar to what you would get if you saved the query reqults to a file in sql mgt studio.

What I have so far is just a flat file source , a lookup and a flat file destination.

I can get the output to generate, but there doesnt seem to be any row terminating, its all one big string.

help ?|||Use "Fixed width with Row Delimiters" option for the flat file connection manager.|||

Eric Wisdahl wrote:

Use "Fixed width with Row Delimiters" option for the flat file connection manager.

Where is that option available ? Under the general tab on my flat file conn mgr, I have only the options:
"fixed width"
"delimited"
"ragged right"

If I have fixed width selected, and go to the advanced tab, start entering my own columns, the column delimiter option is greyed out.|||When you are first creating the flat file connection manager it gives you the option of delimited, fixed width, fixed width with row delimiters, ragged right. All that fixed width with row delimiters does is add another column to each record which contains the row delimiter. You can accomplish the same thing by adding it in with the derived column and adding it to the end of your output record.

Flat File Destination - File name

Hello,

I'm trying to send a file with FTP.

In the Flat File connection manager I have to write the name of the file.

Is there any way of deciding at runtime what the name of the file should be?

Thank you.

Yes. Use expressions.

http://blogs.conchango.com/jamiethomson/archive/tags/Expressions/default.aspx

-Jamie

|||

Hi Chaps

I am trying to achieve a similar thing with the FTP Task
ie incorporate the date into the filename when sending the file.

I have set IsRemotePathVariable=True

I have created an expression for the RemotePath:
"/FName"+ (DT_WSTR,4)DatePart("yyyy", GetDate())
+ (DT_WSTR,2)DatePart("mm", GetDate())
+ (DT_WSTR,2)DatePart("dd", GetDate())+".txt"

However, an error is produced:
"Error at FTP Task: Failed to lock variable"/FName2007611.txt"

Should I be linking the expression to a variable ?
and if so how

Any guidance would be very much appreciated.

Regards

JohnJames
|||

Hi,

Just so I understand this correctly, do you use a hard coded file name in the Data Flow Flat File Destination (f.ex. outputfile.txt) and then afterwards in the Control Flow you change the file name (f.ex. outputfile_11_06_2007.txt) by using these expressions?

Thank you.

|||Yes

In the Dataflow I am using a hard-coded filename,
to extract data from SQL Server to a flatfile.
In the Control Flow is the FTP Task where I am trying to add
the Date to filename using an expression.

Regards

JohnJames
|||Why don't you create a variable who's value is an expression. You then use the variable in the data flow and the FTP task. That way you are always guaranteed that the file name is correct.
Saves you from having to rename a file as well..|||Thanks Crispin

I'll give a go and let you know

Regards

JohnJames|||

Hi,

I'm trying to decide the filename of my Flat File Destination at run time by using an expression variable.

I created an expression variable:

Name: FileName_Expression Value: C:\test.txt

However, in the Data Flow in Flat File connection manager, I can't seem to put my variable name inside the "File Name" editbox and I have no idea where to put my expression variable.

Any ideas?

Thank you so much!!!

|||

Mr. Hat,

Use the connectionstring property of the flat file connection manager.

ex. ConnectionString = @.[User::myPath] + "\\ERROR_" + @.[User::FileName_Expression]

(Where myPath is something similar to C:\temp)

NOTE: new questions like this should probably get a new thread as many people will just look past the threads which appear to have already been answered.

Hope this helps.

EWisdahl

|||Wow, it worked! Thanks a lot!! |||

Hi

when i'm trying to set the file name runtime for excel destination by setting expression

ConnectionString : @.[User::ExcelFullFileName]

but getting below error

Error at Data Flow Task [Excel Destination [7689]]: The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.

please can you advice regarding this?|||I believe (but I may be wrong) that the Excel file needs to exist to be referenced by the Connection Manager.sql

Flat file data types - defined from Table?

This question is around how we can get the data types and lengths populated into the flat file source columns.

In Connection Manager, you have your flat file defined. You can choose "Suggest Types...", and the minimum lengths and correct data types will be returned from within the data in the flat file.

Is there some way to automate this data type definition, but coming from the other direction (coming from the destination table that we are loading)?

For example, you have mapped the columns that will be loaded. Can you then reverse engineer the data types and lengths for the columns in the flat file from the destination table?

TIA

No, not possible. Unless you're going to write your own package using the SSIS API. But then, if you're going to do all of that work, SSIS may not be the best fit after all.|||

Phil

Thanks much for your answer. Maybe I'm not thinking flexibly enough regarding the solution.

It seems the flat file will pretty much default to DT_STR with length of 50 for all columns. Obviously some data could be truncated.

Where I'm trying to head is:

1. Assuming your table is mapped correctly to data types and lengths, would it not be best practice to set the same data types and lengths in your flat file definition? Or...does it matter?

2. Again, back to flexible thinking about the problem and solution. Is there another path that I'm not seeing? Perhaps the definition of data types and lengths for the flat file columns is moot, b/c it is also defined (and overridden) at another point, such as during the mapping or transforms?

Thanks again

|||

Alfred Kokintz wrote:

Phil

Thanks much for your answer. Maybe I'm not thinking flexibly enough regarding the solution.

It seems the flat file will pretty much default to DT_STR with length of 50 for all columns. Obviously some data could be truncated.

Where I'm trying to head is:

1. Assuming your table is mapped correctly to data types and lengths, would it not be best practice to set the same data types and lengths in your flat file definition? Or...does it matter?

2. Again, back to flexible thinking about the problem and solution. Is there another path that I'm not seeing? Perhaps the definition of data types and lengths for the flat file columns is moot, b/c it is also defined (and overridden) at another point, such as during the mapping or transforms?

Thanks again

Generally, if a flat file column contains integers, you will want to define it as such up front in the flat file connection manager. The more work you do there, the easier the rest of the puzzle will be.

Flat File created but with too many spaces

My Flat File connection manager is creating a flat file that has way too many spaces between my fields. I am exporting columns from a table which in the end should only produce a fixed length flat file of 100 bytes but there are a ton of spaces between the columns for some reason.

http://www.photopizzaz.biz/junk/4.jpg

http://www.photopizzaz.biz/junk/7.jpg

You're using fixed width and likely the default width, which is 50 characters. You might want to switch to delimited or use a smaller fixed width.|||thanks much, found it.

Flat file connection manager question

Hi,

I am having problems setting up columns in a flat file connection manager.

The text file I am trying to parse is in this format:

col1 col2 col3 col4 [] col1 col2 col3 col4 [] col1 col2 col3 col4

where [] = {LF}

I've tried all of the different column delimiters, but apparently this file does not use any of the built-in delimiters, such as tab. I think there are just blank spaces between the columns.

I've requested that the file be comma-delimited instead, but in the event that this is not possible, how should I handle this situation?

Thank you

Are you sure it isn't a fixed-width format?|||

Actually I think it is.

|||Yep, start there and see how far you get. Try working with either the fixed-width format or the ragged-right format.

Flat file connection manager not parsing file correctly

Hi,

I have a flat file, comma-delimited, with strings in double-quotes.

In the connection manager for the file, I have specified that the Text Qualifier = ""

However, in the preview tab, it still shows the strings as surrounded by the quotes, e.g. "mycol1" whereas it should show mycol1 without the quotes.

Next, when I examine the data in the database after the load, it's messed up there also.

"mycol1" ends up in the database as "mycol1

"mycol2" ends up as "mycol2

This is not right.

I have format set to delimited, header row delimiter crlf, etc.

Any ideas?

Thanks

I sort of see what's happening.

The "mycol1 problem is due to the fact that I have mycol1 set as a string with a length of 6. Because it's not stripping off the double-quotes correctly, it counts the first six characters of "mycol1", which is of course "mycol1. It's counting the first double-quote as a character.

So the question remains, HOW do I get it to recognize the fact that "" are the text delimiters?

I remember setting up this same flat file connection before and it worked, but now it's not.

|||

Nevermind!

The text delimiter is ", not ""!!

doh

sql

Flat File Connection Manager HeaderRowsToSkip not modifiable at runtime?

I have been working with flat file connection managers for a while now, and I have found it very useful to set properties on all types of SSIS objects using expressions that are set to SSIS package variables.

We have recently moved towards using a centralized application configuration infrastructure, so we are now loading up all application configuration information from our own system -- it's actually based off of the 2.0 ConfigurationManager.

I have developed a custom control flow task that will retrieve all of the SSIS variable information from our own application configuration system and set all of the SSIS variables as the first step in a package.

When I have been using this to set the SSIS Variables which are used in expressions for the HeaderRowsToSkip and DataRowsToSkip (there may be others, but I have not tested them yet) properties of flat file connection managers, these values are not being used -- instead it is using the values for the variables that are defined in the package itself (i.e. the default values that I set up in BIDS when developing the package). The ConnectionString property on the flat file connection manager does not exhibit this behavior.

Can anyone provide any insight on this? Is this a bug in SSIS, or is there something that I am missing here?

Thanks in advance.

Sounds like a great big stonking bug to me. Could you log it at Microsoft Connect?

-Jamie

|||certainly will do -- by the way, love your blog -- it's one of my favorite resources for SSIS development issues.|||

Glad to hear it. I really appreciate the feedback.

-Jamie

Flat File Connection Manager does NOT fail

I use Flat File connection manager where I have defined the format of the file as "Ragged Right" (CR,LF Dos file) with no header rows. The columns are fixed width with Row Delimiter "{CR}{LF}".

The problem is when I process a file with incorrect format. The file execution does not throw an error. Instead it throws a warning " There is a partial row at the end of the file.".

How can I force the Flat file connection manager to FAIL if the format of the file is not matched exactly. I would think this would be the default behavior of Connection manager.

ie. If I have Connection manager setup for a dos file with 2 columns. Column 1 is 5 characters long, column 2 is 3 character long, and the end of line characters are CR, LF. However, if I send in file with 10 rows of 1 character and CR LF, the data flow works and processes these rows incorrectly. How can I force the task to fail if incoming file is not in defined format.

The "Ragged Right" format does not have any limitation on the size of the last column (delimited one), so if your file is missing some row delimiters the flat file parser will continue to look for them and probably swallow succeeding row(s).

You can restrict the size of your "ragged right" column by setting the OutputColumnWidth property of those columns on the Advanced page of the Flat File Connection Manager UI. That will make the flat file source fail if the truncation happens. If you would rather to redirect such rows, you can do that by setting "Redirect Row" for Truncation on the Error Output page of the Flat File Source UI, and then define your error flow.

HTH.|||Thanks. It worked.

Flat File Connection Manager

As I have a file whose delimiters can be different. I have need to change the delimiters and filename programatically.

I have come across a way to change the filename using the inbuilt expressions setter. Howver the columns are not listed, possibly because they are on the advanced tab and theoretically each column delimiter could be different.

Will I have to do this through a script or is there an easier method?

As far as I know, this would need need to be handled by a script or a derived column component. You'd need to bring the flat file row in as a single column, then split it up yourself. You could reference a variable in the script or derived column component to determine what delimiter to use.

Here's a few posts that might help with this:

http://blogs.conchango.com/jamiethomson/archive/2006/07/14/4226.aspx

http://agilebi.com/cs/blogs/jwelch/archive/2007/05/07/handling-flat-files-with-varying-numbers-of-columns.aspx

http://agilebi.com/cs/blogs/jwelch/archive/2007/05/15/handling-varying-columns-part-2.aspx

Fixed memory size on MSDE

I would like to limit memory (RAM) usage for MSDE.
Since there is no Enterprise manager - is there another way how to do it?
(-> SQL command?!)
Thank You
PetrHi Petr
Please read about sp_configure in the Books Online.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Petr Stejskal" <petr.stejskal@.txn.cz> wrote in message
news:uoi1VuKnDHA.1884@.TK2MSFTNGP09.phx.gbl...
> I would like to limit memory (RAM) usage for MSDE.
> Since there is no Enterprise manager - is there another way how to do it?
> (-> SQL command?!)
> Thank You
> Petr
>

Firewall Problem

I have opened port 1433 on my firewall, but I am still not able to get
remote clients to connect via query analyser, or enterprise manager.
Are there other ports required to be opened ?Have you checked your remote clients to make sure TCP/IP sockets is the
default protocol? You may have to go SQL Client Network Utility or run
through a SQL Server ODBC System DSN (Control Panel | ODBC Data Sources) and
verify that on the user login credential page that the Client Configuration
that it says TCP/IP sockets.
I did look in SQL Server books online in the Network Libraries topic, and
read this
SQL Server uses UDP port 1434 to establish connections from SQL Server 2000
clients. This socket number is also reserved for SQL Server by Internet
Assigned Number Authority (IANA).
You can download SQL Server books online for free from MS
http://www.microsoft.com/sql/techin.../2000/books.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"AussieRules" <someone@.nowhere.com> wrote in message
news:upbiLWY6DHA.3288@.TK2MSFTNGP11.phx.gbl...

quote:

---

> I have opened port 1433 on my firewall, but I am still not able to get
> remote clients to connect via query analyser, or enterprise manager.
> Are there other ports required to be opened ?
>
>

---

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my Remote database. In Enterprise Manager it won't resolve listing the server and it's tables. I can register and get a connection though. My host said that if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
Stickfigure
Because everyone likes Figures.
can you connect using query analyser? Or osql?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||If it is a firewall issue, and if port 1433 is blocked then the chances are
that ports 8080 and 1222 are blocked also. You might need to take this up
with your firewall administrator.
"Stickfigure" <Stickfigure@.discussions.microsoft.com> wrote in message
news:792F6F89-F318-4E47-99FA-189E9D082BDD@.microsoft.com...
>I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my
>Remote database. In Enterprise Manager it won't resolve listing the server
>and it's tables. I can register and get a connection though. My host said
>that if I am behind the firewall, that it blocks Port 1433. I tried
>switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
> Stickfigure
> Because everyone likes Figures.

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my Remote database. In Enterprise Manager it won't resolve listing the server and it's tables. I can register and get a connection though. My host said that if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
Stickfigure
Can you connect through query analyser to another machine?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my R
emote database. In Enterprise Manager it won't resolve listing the server an
d it's tables. I can register and get a connection though. My host said that
if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. St
ill no luck. I am stuck. Any ideas?
StickfigureCan you connect through query analyser to another machine?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Firewall Port 1443

I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my R
emote database. In Enterprise Manager it won't resolve listing the server an
d it's tables. I can register and get a connection though. My host said that
if I am behind the firewal
l, that it blocks Port 1433. I tried switching the Port to 8080 and 1222. St
ill no luck. I am stuck. Any ideas?
Stickfigure
Because everyone likes Figures.can you connect using query analyser? Or osql?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||If it is a firewall issue, and if port 1433 is blocked then the chances are
that ports 8080 and 1222 are blocked also. You might need to take this up
with your firewall administrator.
"Stickfigure" <Stickfigure@.discussions.microsoft.com> wrote in message
news:792F6F89-F318-4E47-99FA-189E9D082BDD@.microsoft.com...
>I installed SQL Server 2000 Enterprise Trial. I am trying to connect to my
>Remote database. In Enterprise Manager it won't resolve listing the server
>and it's tables. I can register and get a connection though. My host said
>that if I am behind the firewall, that it blocks Port 1433. I tried
>switching the Port to 8080 and 1222. Still no luck. I am stuck. Any ideas?
> Stickfigure
> Because everyone likes Figures.

firehouse mode

SYMPTOMS
If you attempt to make changes to a row in a table
displayed in SQL Server Enterprise Manager (SEM), unless
you scroll down to the end of the table (the last row of
the table), Enterprise Manager returns the following
error:
Cannot start transaction while in firehose mode.
CAUSE
When using SEM to display the rows from a table, all rows
are returned by a "firehose cursor"; however, only the
rows that are displayed have been processed. A "firehose
cursor" refers to how the server sends rows to the client
as fast as the client can process them. Rows that are not
displayed in the Enterprise Manager are not processed and,
therefore, they remain in the network buffer.
The "Cannot start transaction while in firehose mode"
error occurs when an OLE-DB provider attempts to perform a
join transaction with results pending and while not in an
updateable cursor mode.
WORKAROUND
Scroll all the way down to the last row of the table. This
forces all the rows to be processed. You can then edit the
row needed and execute the update.

>--Original Message--
>I just got the following message after trying to update
>records in a sql table:
>"transaction cannot start while in firehouse mode"
>any ideas what the problem is? please advise and thanks
>.
>> Aaron's suggestion did not work.
What does "did not work" mean?
http://www.aspfaq.com/
(Reverse address to reply.)

firehouse mode

SYMPTOMS
If you attempt to make changes to a row in a table
displayed in SQL Server Enterprise Manager (SEM), unless
you scroll down to the end of the table (the last row of
the table), Enterprise Manager returns the following
error:
Cannot start transaction while in firehose mode.
CAUSE
When using SEM to display the rows from a table, all rows
are returned by a "firehose cursor"; however, only the
rows that are displayed have been processed. A "firehose
cursor" refers to how the server sends rows to the client
as fast as the client can process them. Rows that are not
displayed in the Enterprise Manager are not processed and,
therefore, they remain in the network buffer.
The "Cannot start transaction while in firehose mode"
error occurs when an OLE-DB provider attempts to perform a
join transaction with results pending and while not in an
updateable cursor mode.
WORKAROUND
Scroll all the way down to the last row of the table. This
forces all the rows to be processed. You can then edit the
row needed and execute the update.

>--Original Message--
>I just got the following message after trying to update
>records in a sql table:
>"transaction cannot start while in firehouse mode"
>any ideas what the problem is? please advise and thanks
>.
>
> Aaron's suggestion did not work.
What does "did not work" mean?
http://www.aspfaq.com/
(Reverse address to reply.)

Firehose mode

Hi
I'm in Enterprise Manager and have made a change to a row.
When I try to update I get a message that says:
Transaction cannot start, Firehose mode"

Can anyone explain what this is and what it means ?

Thanks

David GreenbergDavid Greenberg (davidgr@.iba.org.il) writes:

Quote:

Originally Posted by

I'm in Enterprise Manager and have made a change to a row.
When I try to update I get a message that says:
Transaction cannot start, Firehose mode"
>
Can anyone explain what this is and what it means ?

It means that you should open a Query Analyzer window and write an UPDATE
statement.

My guess is that EM has at this point not yet retrieved all rows, and
since the result set is still open, the connection does not permit a
new operation to be initiated. Note that this has more implications
than just not being able to update the row. It also means that SQL
Server needs to keep the untrieved rows locked.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Uzytkownik "David Greenberg" <davidgr@.iba.org.ilnapisal w wiadomosci
news:469C9971.7050205@.iba.org.il...

Quote:

Originally Posted by

Hi
I'm in Enterprise Manager and have made a change to a row.
When I try to update I get a message that says:
Transaction cannot start, Firehose mode"
>
Can anyone explain what this is and what it means ?

I don't know exactly what it means. But I usualay solve this problem opening
not whole table but only e.q. TOP 10

br
Bober|||Erland,

Doesn't FIREHOSE mode mean that EM has read the records in a "forward only
cursor" and has no means of updating? Hence the name "firehouse" which is a
rapid stream of data only going 1 way.

Oscar

"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns99707AD4B7BCCYazorman@.127.0.0.1...

Quote:

Originally Posted by

David Greenberg (davidgr@.iba.org.il) writes:

Quote:

Originally Posted by

>I'm in Enterprise Manager and have made a change to a row.
>When I try to update I get a message that says:
>Transaction cannot start, Firehose mode"
>>
>Can anyone explain what this is and what it means ?

>
It means that you should open a Query Analyzer window and write an UPDATE
statement.
>
My guess is that EM has at this point not yet retrieved all rows, and
since the result set is still open, the connection does not permit a
new operation to be initiated. Note that this has more implications
than just not being able to update the row. It also means that SQL
Server needs to keep the untrieved rows locked.
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

|||http://support.microsoft.com/kb/286199
On Jul 23, 8:55 pm, "Oscar Santiesteban"
<o_santieste...@.bellsouth.netwrote:

Quote:

Originally Posted by

Erland,
>
Doesn't FIREHOSE mode mean that EM has read the records in a "forward only
cursor" and has no means of updating? Hence the name "firehouse" which is a
rapid stream of data only going 1 way.
>
Oscar
>
"Erland Sommarskog" <esq...@.sommarskog.sewrote in message
>
news:Xns99707AD4B7BCCYazorman@.127.0.0.1...
>
>
>

Quote:

Originally Posted by

David Greenberg (davi...@.iba.org.il) writes:

Quote:

Originally Posted by

I'm in Enterprise Manager and have made a change to a row.
When I try to update I get a message that says:
Transaction cannot start, Firehose mode"

>

Quote:

Originally Posted by

Quote:

Originally Posted by

Can anyone explain what this is and what it means ?

>

Quote:

Originally Posted by

It means that you should open a Query Analyzer window and write an UPDATE
statement.

>

Quote:

Originally Posted by

My guess is that EM has at this point not yet retrieved all rows, and
since the result set is still open, the connection does not permit a
new operation to be initiated. Note that this has more implications
than just not being able to update the row. It also means that SQL
Server needs to keep the untrieved rows locked.

>

Quote:

Originally Posted by

--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se

>

Quote:

Originally Posted by

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...downloads/books...
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ons/books.mspx- Hide quoted text -

>
- Show quoted text -

|||Jason Lepack (jlepack@.gmail.com) writes:

Quote:

Originally Posted by

http://support.microsoft.com/kb/286199

Ah, that was a very special situation. Thanks for the link, Jason.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx