If there are problems with the file, the support can see the data without needing access to the file.įor this process, the format stored procedure, s_bcpMasterSysobjects, will insert into the table using an identifier and the BCP will extract using the same identifier. The data extracted can be presented to a user for viewing from the database. 
It gives a record of the data extracted – if the file is lost it can be recreated. This gives you added features that can be valuable on systems that are performing a lot of extracts: To get round all of these problems, use the stored procedure to insert into a table then, from the BCP, extract from that table. All in all, this method should be used with caution and comments (warnings) placed in the stored procedure for the aid of future maintenance. Particularly if data is flagged as exported then the flagging will be performed on the first call and no data will be extracted for the second call. This needs to be taken into account when considering how long the process will take and its impact on your system.Īs the stored procedure is executed twice it should not contain any updates of permanent data. There is a potential problem with this though: it means that the stored procedure is executed twice, once for the format and once to extract the data – due to the fmtonly setting, both these calls will produce a resultset. Look at this execution using the profiler and you will see set fmtonly off followed by set fmtonly on. 
Is anyone aware of what might be causing this on my machine?
The author was unable to replicate this error. The stored procedure executed fine outside the BCP, but when I tried to run the above command I received an error:Įrror = Function sequence error This was the only piece of code that I failed to get working. Note that the column terminator is not used since the resultset is a single column.
0 kommentar(er)
