Relational State Sequences and SQL Server CLR Aggregate functions

Posted on August 26, 2013 by Bob L

My research on continuous improvement problem solving frameworks has convinced me that a problem system must possess complete data about the processes it is trying to learn from including how all the items within a solution attempt have changed. I call this process “relational state tracking”. Note, that tracking all of the information does not mean the system will have to use all of this in order to gain self-improvement and optimization. In fact, the goal of doing complete information tracking isn’t so much to analyze all of the data, but to analyze in multiple small test cases what data is needed for larger cases applying the full set of data for smaller test cases.  The idea is that in order to achieve noise reduction needed for rapid prediction, one must have lots of noise to learn from.

For example, in the Tower of Hanoi puzzle, tracking the state changes between discs and pegs as they relate to having certain values in a certain sequence provides patterns that can be utilized as the number of discs grow.  My doctoral project includes a scenario whereby the goal of a general purpose solver is to find solution for puzzles without any prior knowledge of the puzzle except that required to perform a simulation to search out all possible branches to meet a goal. The motivation for this is to determine feasibility for software to discover solutions to problems where the original solution is not known ahead of time purely by pattern recognition and deduction based on the simulations. The purpose of this blog entry is not to get into my research concerning my doctoral scenario but just to share how this sort of state tracking can be implemented via .NET CLR in SQL Server.

In my case, I want to be able to pull together multiple sequences that represent the truth-falsity of if a particular disc’s peg property (what peg was the disc was on at a certain move) changed to a particular value. The goal is to roll-up all the places where the disc’s peg changed to provide a view of which discs moved on each move regardless of peg. This can help predict what disc to move for larger instances even if we are not certain of what the correct peg should be.

In order to do this, I created 3 aggregation functions using the SQL 2012 Data Tools CLR project. The 3 functions are BinaryStringOr, BinaryStringAnd, BinaryStringXor.  I actually only need the BinaryStringOr for my scenario, but went ahead and created the other ones.  I initially tried to leverage .NET bit strings and use math functions with SQL but the complexity of this became too time-consuming given the relatively small amount of data. So, even though the performance is much worse, I found it easier to just utilize strings containing 1 and 0. This could be done more efficiently using bit strings, however the concept is similar since even bit strings will grow too large to be treated mathematically and will need to be treated bit-by-bit. Even simply 64 bits in a row is too long for a SQL bigint.

The code is shown below for the BinaryStringOr – the code simply checks if the current aggregated string as each new string is received contains a 1 or if the new string contains a 1. In either case, then the result is a 1 to the output string. The practical application of this is to determine if a disc was moved to any peg on any move and set a bit to indicate a state change of the disc. This can also be done for the peg as it correlates to any disc moving onto it. For this code to work, I had to implement the IBinarySeialize rather than the default Format.Native since we are aggregating into a string rather a numeric type.

using System;
using System.Data;
using System.Data.SqlClient;
using System.Data.SqlTypes;
using Microsoft.SqlServer.Server;

[Serializable]
//[Microsoft.SqlServer.Server.SqlUserDefinedAggregate(Format.Native)]
[Microsoft.SqlServer.Server.SqlUserDefinedAggregate(Format.UserDefined, MaxByteSize = 8000)]
public struct BinaryStringOr : IBinarySerialize
{
    private SqlString outString;
    private int outLen;

    public void Init()
    {
        outString = “”;
        outLen = 0;
    }

    public void Read(System.IO.BinaryReader r)
    {
        outString = r.ReadString();
    }

    public void Write(System.IO.BinaryWriter w)
    {

        w.Write(outString.Value);
    }

    public void Accumulate(SqlString Value)
    {
        if (outString == “” & !Value.IsNull)
        {
            outString = Value.Value;
            outLen = Value.Value.Length;
        }
        SqlString newOutString = outString;

        if (!Value.IsNull)
        {
            newOutString = “”;
            for (int i = 0; i < Value.Value.Length; i++)
            {
                if (outString.Value.Substring(i, 1) == “1”
                                || Value.Value.Substring(i, 1) == “1”)
                {
                    newOutString = newOutString + “1”;
                }
                else
                {
                    newOutString = newOutString + “0”;
                }

            }
        }
        outString = newOutString;
    }

    public void Merge(BinaryStringOr Group)
    {
        outString = Group.outString;
    }

    public SqlString Terminate()
    {
        return outString;
    }

}

For example, given the following sequences for the discs on different pegs from a game with simply 3 discs, what would the output state sequence be for all state changes made by the disc? This sequence shows the intersection of the disc and a specific peg as a sequence. This is illustrated below:

Disc    Peg    Sequence Map

Disc    Peg    MoveStates
1    1    0000100
1    2    0010000
1    3    1000001
2    1    0000000
2    2    0100000
2    3    0000010
3    1    0000000
3    2    0000000
3    3    0001000

 

For the above, we need to find the sequence for the discs across all pegs. Using the aggregate function from above, we get the following changes for each disc over the sequence of 7 moves required for the optimal solution:

1    1010101
2    0100010
3    0001000

We can see the practicality of this for getting closer to predicting the solution for larger number of discs as the pattern is simply expanded for 4 discs over 15 moves for the optimal solution.

1    101010101010101
2    010001000100010
3    000100000001000
4    000000010000000

The use of the aggregate function is shown below:

SELECT
        InstanceVariableNumber as Disc,
        dbo.BinaryStringOr(MoveStates)
       
    FROM [Games].[InstanceVariableValueStates]
    GROUP BY
    InstanceVariableNumber
    where Games.InstanceVariableCount = 3

A fairly simple machine learning algorithm should be able to spot that that the pattern for the smallest disc is to change state every other move and the next large disc every fourth move, the third every 8th interval and so on.

When the peg states are also examined for patterns for disc counts from 3 to 6, only a couple of the patterns need to be identified and the rest can be deduced due to the standard rules of play effectively generating a rule that only allows 1 choice so that the sequence can be generated instantly. From there, all that is needed is a reversal process to generate the query criteria that reflects the relational sequences.

Peg    Sequence
1    0000100
2    0110000
3    1001011
1    000010000110000
2    100101100000100
3    011000011001011
1    0000100001100000100101100000100
2    0110000110010110000010000110000
3    1001011000001001011000011001011
1    000010000110000010010110000010000110000110010110000010000110000
2    100101100000100101100001100101100000100001100000100101100000100
3    011000011001011000001000011000011001011000001001011000011001011

Posted in Artificial Intelligence, Machine learning, Problem Solving | Tagged | Leave a comment

Concept for a High-Performance Database (HPD)

Posted on August 24, 2013 by Bob L

Recently, I’ve been studying Microsoft PDW as part of an ETL integration project. This got me thinking about the distributed database computing paradigm and scaling out performance for SQL Server for OLTP purposes. PDW utilizes multiple compute nodes that are all running SQL instances to help scale very large database implementation, but the main purpose of PDW is as an OLAP-type repository for a BI infrastructure and not as a mechanism to host OLTP databases.

Interfacing with PDW requires interacting with a layer that sits on top of the standard T-SQL interface for both DDL and DML purposes. PDW provides a syntax so that the database can be defined in a distributed fashion (i.e. replicating out dimension type data and hash-partitioning fact-type data) and queried so that the distributed compute nodes are put to work to bring back the data. More about PDW is on the Microsoft site at http://www.microsoft.com/en-us/sqlserver/solutions-technologies/data-warehousing/pdw.aspx.   PDW has made progress in facilitating shorter times for very large queries and enabling larger databases, but it is not really a HPC solution for OLTP databases. It is oriented to  support very large queries on very large databases mainly from other servers in a BI infrastructure rather than a being a user-centric transactional database supporting thousands of simultaneous users. 

In addition to PDW, SQL Server 2014 is on the horizon with Hekaton (http://research.microsoft.com/pubs/193594/Hekaton%20-%20Sigmod2013%20final.pdf) to enable higher-performance database processing including OLTP scenarios. Hekaton provides a mechanism to map tables directly to memory and rely exclusively on high-throughput logging to ensure integrity. It will be interesting to see how Hekaton is utilized by organizations or it also becomes more integrated into the BI aspects of SQL Server including PDW.

My belief is that even though enabling components are present, there does not seem to be an obvious design pattern for a high-performance SQL Server OLTP database for very low latency that includes very large/scalable storage requirements. Such databases have generally involved large amounts of custom development to implement. An example of such a project was the MySpace implementation which involved 440 different SQL Server database instances (http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?casestudyid=4000004532).   I hope to test out over the next few months a solution outlined below which has the benefit of supporting standard drivers and database interfaces within SQL Server without the need for database sharding (http://www.codefutures.com/database-sharding/) that normally entails significant application development to manage. The goal is to utilize standard SQL Server database implementation techniques on top of the Windows Server storage infrastructure to incorporate distributed storage over high-speed networking.

Some of my previous posts have focused on PCIE SSD benefits including the use of Fusion-IO cards within a single server. I was able to achieve over 5 GB/s database backup throughput – enough to nearly saturate even a 56Gb InfiniBand connection, the highest-throughput network configuration that supports standard server protocols in data centers. Windows Server 2012 has made significant advances in SMB which can be leveraged by ISCSI interfaces which can sit on top of InfiniBand providing potentially 56Gb/s throughput.  This enabling of high-speed networking over the ISCSI interface effectively allows high-speed storage devices hosted on multiple nodes to achieve very low latency and high-throughput. This inspired the idea for the HPD (High Performance Database).

The design goal is simple – utilize standard SQL Server tools and Microsoft platform components to build a database on a single SQL Server instance which could be clustered or mirrored, but leverage high-performance storage devices not only on the hosting node, but on distributed nodes to support very large OLTP databases. The technique for leveraging the distributed storage is via ISCSI over InfiniBand. Previous to this I had played with ISCSI to create a SQL Cluster so knew that this would work.

I almost gave up on the HPD idea, because of concerns about the processing cycles required on the single SQL Server instance to deal with the high-speed data interactions with the networked nodes, but then noticed this white paper – http://www.mellanox.com/related-docs/whitepapers/WP_Scalable_Storage_InfiniBand_Final.pdf

This paper along with some other research indicating that much of the work involved with storage retrieval with the latest SMB and ISCSI fully leverage the data hosting nodes makes me think that the idea is worth testing out. The key enabler is that much of the processing is done natively in the Mellanox cards rather than requiring server resources. This is especially true when utilizing the RDMA interface as discussed in this article (http://embedded-computing.com/pdfs/Mellanox.Apr07.pdf). The below diagram from the Mellanox paper  illustrates the concept:

image

The paper includes the following comment with the graphic:

VSA based appliances are being used to enhance the performance of clustered databases by providing a “Fan-In” approach. High-end SMP machines, like the HP DL 580, can process more transactions than can be handled by local storage or a dedicated SAN. A solution is to provide a virtual RAID across disks from five physical storage servers. In this example, InfiniBand was able to saturate the IO bus of the DL580.In this configuration, performance was 23Gb/s with 2.5M Random IOPs. An equivalent storage configuration with Fibre Channel would require 50 FC wires!

Based on this, utilizing a robust SQL Server instance on a machine with high number of cores and large amount of memory (i.e. 2 TB RAM, 144 cores) could utilize a dozen or so other servers to achieve ultra high OLTP performance, greater than any benchmarks based on purely local storage or the use of a large SAN even with multiple high-speed HBAs.  Distributing the PCIE SSD out to the various nodes which function only as file servers supporting ISCSI and mapping the ISCSI drives to the SQL Server database has the potential to provide higher throughput than a monolithic structure where the database server is attached to a traditional SAN for storage – even in the case where the SAN is hosting SSD devices.

I am very busy on multiple projects currently, but my next skunk-works project will be to take my 2 smaller servers that have PCIE SSD Fusion-io cards and connect them together via InfiniBand. I will configure one server as the SQL Server database instance to utilize both the local PCIE SSD as well as the PCIE SSD on the other server via InfiniBand using ISCSI.  If my hunch is right, then the overall throughput of the database server will be higher leveraging additional storage from the other server than it could be if all of the storage was local to the server.

Although the solution is limited in scalability since there is still only 1 main SQL Server instance, it provides a topology to scale out storage to the maximum potential of the CPU capabilities of the hosting SQL Server machine. The typical bottleneck with SQL is on the I/O side rather than the CPU side. This approach helps to scale storage out such that CPU is no longer the bottleneck for a very large SQL instance that supports standard T-SQL and driver requirements so that existing applications can still connect to the database without any modifications. This could help customers who are dealing with inability to scale their current database server to support higher-throughput or lower-latency requirements from their applications with the benefit of not needing to modify the applications.

As far as where Hekaton fits, I see this as yet another component for the high-speed database to store highly-accessed tables in memory and to leverage multiple PCIE-SSD devices connected together via Microsoft’s Storage Spaces technology for the logging and the non-memory-located tables. Potentially, this type of approach could also be leveraged in a PDW implementation by the compute nodes as well. Since I am building my solution on top of standard Microsoft protocols and components, it is perfectly compatible as a design pattern to compliment Microsoft’s latest SQL Server product implementations.

As far as where my concept fits in as far as a larger BI infrastructure including predictive analytics, one significant advantage for a high-throughput/high-capacity OLTP database is the ability to perform pre-aggregations and inject intelligent data into data warehouses. This facilitates the ability to respond in near-real time based on just-in-time analytic processing as data is received, rather than as a later process.   Ultimately lower -latency predictive analytics are facilitated when OLTP databases have the capability to perform aggregative functions or execute predictive models as data is received rather rather than in later post processes.

Posted in Fusion-io, SQL Server | Tagged | Leave a comment

Write throttling and Fusion-io Cards

Posted on July 3, 2013 by Bob L

Why Fusion-IO SLC Duos may outperform MLC Duos by more than expected and some mitigations

Recently I decided to revisit the issue of write throttling that occurs on Fusion-io cards under load. I found this article http://www.hookbag.ca/media/d/b5/d987/d98720b9b537819f/original.pdf that explains the topic thoroughly, specifically for HP Server configurations. I am running 7 HP-branded Fusion-io (IO Accelerator) Duo cards presently in a DL 370 G6. Although, HP does not sell external power cable kits with the Duos and does not encourage their use, they are available through a kit as explained in the article.

Although the impact of not having external power for duos is minimal, it does occur. I ran the fio-status –fj command specified in the article. I discovered that throttling had occurred on virtually all of the duos, but the worst offenders were .the 2 MLC Duos – a 640 GB and a 1.28 TB card. The SLC Duos throttling was much lower, despite the database load processing being even distributed. One of the cards with the high throttling was actually in a PCIE X16 slot. The HP DL 370 G6 actually includes 3 x16 slots. All three of the slots support up to 75 W, although one is electrically an X8 slot with a X16 form factor.

Below is a section of output from the fio-status –fi command showing the throttling:

“write_pwr_throttling_count” : “5013”,
  “write_pwr_throttling_sec_since_last” : “58400”,
  “write_reg_power_level” : “Inactive”,
  “write_reg_thermal_level” : “Inactive”,
  “write_reg_total_level” : “Inactive”,
  “write_throttling_reason” : “No reason given.”,
  “write_throttling_state” : “None”

The default behavior of the driver is to only use 25 Watts regardless of the type of slot in which a card is located. The fil-config utility provides a method to override this default behavior and force the driver to utilize up to the max power rating of the card against the power provided by the PCIE slots. This capability must be used very carefully since trying to draw more power from a slot that does not have it can damage the motherboard. After checking, double-checking, and triple-checking twice, I verified the serial numbers of the cards in the X16 slots. I then utilized the fio-config to set override for the specific serial numbers.

After rebooting, I checked again the throttle counts. Sure enough, the throttling counts were eliminated for the cards in the X16 slots. The only card that was still showing significant throttling was the 1.2 TB card which was not included in the override because it was not in an x16 slot. What also was interesting was that the SLC cards did not experience nearly the degree of throttling as the MLC cards. Also, the fio-status utility reported very small amount of power draw beyond 25W for the overridden cards except for the slot containing the 640 GB MLC. The SLC slots that were given the power override barely used it. My next step will be to turn off the power override for one of the SLC cards in an X16 slot, switch the other MLC card to the X16 slot and then turn on the power override for the other MLC card in the server.

Below illustrates the different outputs of the cards. Note that although both exceeded 25 Watts, the max watt power usage is much lower for the SLC card than the MLC card.

Adapter: Dual Adapter

HP 320GB SLC PCIe ioDrive Duo for ProLiant Servers, Product Number:600281-B21

ioDrive Duo HL, PN:00190000107

External Power Override: ON

External Power: NOT connected

PCIe Bus voltage: avg 11.97V min 11.86V max 12.00V

PCIe Bus current: avg 0.92A max 2.13A

PCIe Bus power: avg 10.95W max 25.32W

Adapter: Dual Adapter

HP 640GB MLC PCIe ioDrive Duo for ProLiant Servers, Product Number:600282-B21

ioDrive Duo HL, PN:00190000108

External Power Override: ON

External Power: NOT connected

PCIe Bus voltage: avg 11.98V min 11.86V max 12.01V

PCIe Bus current: avg 0.96A max 2.62A

PCIe Bus power: avg 11.47W max 31.15W

More research is needed to validate if in fact the MLC adapters are more apt to be write-throttled than the SLC cards, but based on my experience it seems to be the case. This lines up with some anecdotal experience of noticing the MLC cards having delays under high write conditions prior to this tweaking. The work around without going to the difficulty of attaching auxiliary power is to deploy the MLC cards in x16 slots and enable (very carefully) power override. Since the override is linked to the actual serial number, this practice should not be done unless you are sure the cards will not somehow be switched around in the server at some point. That is a pretty big assumption to make and may not be worth the risk to get a small amount of extra write throughput. Note that this does not affect read throughput, only writing.

Posted in Fusion-io | Tagged | Leave a comment

In Transition…

Posted on March 22, 2013 by Bob L

I am just getting around to moving content from my MSDN blog over to here along with a lot of other stuff. Still learning ropes as far as how to create categories as I have diverse interests. SQL Server performance, predictive analytics, machine learning, automated problem solving, and automated financial investment systems.

My MSDN blog is focused on SQL Server. It still exists as of 3/22/2013  http://blogs.msdn.com/b/microsoftbob/ . Not sure how much longer they will keep it up. I can actually still post to it, but I don’t think since I left Microsoft I can still keep it.

I am assisting a startup company called Authentic Intelligence. We’re hoping to generate some visibility for an automated trading system product called TradingOptimizer.com that my son helped develop but still needs more testing as well as an automated generic continuously improving problem solving system. More about the trading optimizer is at http://www.tradingoptimizer.com and more about Authentic Intelligence services is at http://www.authenticintelligence.com

Thank you for your interest. You can follow me on twitter at bigdatabob.

Posted in Uncategorized | Leave a comment

Some thoughts on big data, predictive analytics and “A/I”

Posted on March 19, 2013 by Bob L

1) The problem with Artificial Intelligence is that it is artificial. What is needed is Authentic Intelligence.

2) Big Data means nothing without intelligent analytical processes. It takes the lifetime of the universe just to find the accurate solution for a 30 city TSP. Combinatorial analytics exponentially add complexity.

Posted in Uncategorized | Leave a comment

Now at 5.11 GB/s SQL backup to Null/3.12 GB/s local backup with I/O Accelerators

Posted on October 31, 2012 by Bob L

This will be my last update for a while, but I did some more shuffling of the database files among the various PCIE SSD logical drives (HP I/O Accelerators which are HP-OEM Fusion-Io cards). See earlier post for info about the drives. In the latest test, I got up to 5.11 GB/s (5228.521 MB/sec) doing the SQL Backup to NUL device. Given a 40 GbE network card and adequate destinations, that same number should be achievable for a “real” network SQL backup. This is raw throughput. As pointed out earlier, factoring in the database compression efficiency of 40% and typical storage overhead, this is an effective or logical data rate closer to 9.0 GB/s.  Also, improved the prior raw 3.05 GB/s to 3.12 GB/s (3195.491 MB/Sec) to local drives including the ioDrives – SQL showed up to 8 GB/s combined read/write throughput spikes – this is significantly above the 6.4 QPI limit, so if any individual QPI bottlenecks are in play, they are not all-encompassing. This time the database was distributed across all of the Duos and for the local backup test it was backed up using the SQL Backup command to all of the Duos along with an additional non-Duo MLC Drive, and 4 SATA SSDs.

SQL command outputs included at end of post for skeptics … Smile. If still not convinced this is possible, check my YouTube video at the 7 minute mark with demo referenced by the 3.05 GB/s post.

This is utilizing 7 Duos spread across Windows-based Raid-0 and Raid-1 logical drives for the database (The ioDrives do not support hardware-based RAID).  In theory, RAID-1 is not be much slower than RAID-0 for read, so if all of the files were distributed evenly and read in parallel, the performance should be about twice that (7 * 1500 MB/s per Duo –>10.2 GB/s). Two issues seem to be complicating optimal performance:

1) The RAID-0 implementation from Windows Server – Not sure how it actually does this, but suspect that this involves buffering each data portion from the input drives together and then buffering out – normally this would be good for typical storage, but at these speeds almost any form of buffering just adds another bottleneck, particularly if it is saturating a QPI link. Based on that, better performance will probably be realized by distributing the files across non-Raid volumes, even the RAID-0. The database has dozens of files, but adding a lower level of granularity makes even file distribution more difficult. Depending on how low in the stack the RAID-0 is occurring, it could also be disadvantaged by the PCIE cards from different IOHs connected to different CPUs – can’t figure out which PCIE slots go to which IOHs – figure it is probably every other card or the first half of cards to one IOH and the other set to the other IOH.  Each logical read would need to bridge together the I/O from each device which would also involve a non-direct transfer from storage to CPU.

2) SQL Server backup internals – lack of knowledge is hurting me here. Not sure of all details of parallelization, but notice a balancing issue in that if one device has more data to read than another, it slows things down, but not to the degree as on the output balancing.  SQL also seems to perform the backup of the various database files in a manner not totally parallel – seemed to see some sequencing around portioned structures but not positive. It also does a final pass on the log, but that is not an issue here since there is noting in the transaction log at this point.

Trying to work through these issues will be time-consuming. Other things are more pressing, so will move onto other things and revisit later unless I stumble upon something in the interim. Thanks for the interest.

 

RESULTS (Local Backup)

/*————————
BACKUP DATABASE [tp_v5_dev] TO 
DISK = ‘j:\sqlbackup\tp_v5_dev_2012_10_28_j1.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k2.bak’,
DISK=  ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k3.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k4.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h5.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6b.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_7.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_8.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_9.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_10.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_11.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_12.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_13.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_14.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_15.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_16.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_17.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_18.bak’,
DISK = ‘i:\sqlbackup\tp_v5_dev_2012_10_28_j1_b.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k2_b.bak’,
DISK=  ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k3_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_k4_b.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_h5_b.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6_b.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6b_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_7_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_8_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_9_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_10_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_11_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_12_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_13_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_14_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_15_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_16_b.bak’,
DISK = ‘L:\sqlbackup\tp_v5_dev_2012_10_28_l_17_b.bak’,
DISK = ‘L:\sqlbackup\tp_v5_dev_2012_10_28_l_18_b.bak’,
DISK=  ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k3_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_k4_c.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_h5_c.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6b_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_7_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_8_c.bak’,
DISK = ‘L:\sqlbackup\tp_v5_dev_2012_10_28_l_9_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_10_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_11_c.bak’,
DISK = ‘j:\sqlbackup\tp_v5_dev_2012_10_28_l_12_c.bak’,
DISK = ‘g:\sqlbackup\tp_v5_dev_2012_10_28_l_13_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_14_c.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_l_15_c.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_l_16_c.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_17_c.bak’,
DISK=  ‘J:\sqlbackup\tp_v5_dev_2012_10_28_k3_d.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_k4_d.bak’,
DISK = ‘F:\sqlbackup\tp_v5_dev_2012_10_28_l_8_d.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_10_d.bak’,
DISK = ‘H:\sqlbackup\tp_v5_dev_2012_10_28_l_11_d.bak’,
DISK = ‘H:\sqlbackup\tp_v5_dev_2012_10_28_l_12_d.bak’,
DISK = ‘K:\sqlbackup\tp_v5_dev_2012_10_28_l_14_d.bak’

— ‘NUL:’ — N’E:\SqlBackup\tp_v5_dev_20120708010002.BAK’ WITH NOFORMAT, NOINIT, 
— NAME = N’tp_v5_dev-Full Database Backup’,
— SKIP, NOREWIND, NOUNLOAD, 
–disk = ‘NUL:’
with STATS = 10, NOINIT, SKIP, — COPY_ONLY,
BUFFERCOUNT=1536, MAXTRANSFERSIZE=1048576, BLOCKSIZE=65536, NO_COMPRESSION
GO
————————*/
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Processed 25288 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG01_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG02_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG03_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG04_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG05_PageFile01’ on file 1.
Processed 17584 pages for database ‘tp_v5_dev’, file ‘History09a’ on file 1.
Processed 1680 pages for database ‘tp_v5_dev’, file ‘History09b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History01_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History01_02’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History02a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History02b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History03a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History03b’ on file 1.
Processed 2736 pages for database ‘tp_v5_dev’, file ‘History04a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History04b’ on file 1.
Processed 3400 pages for database ‘tp_v5_dev’, file ‘History05a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History05b’ on file 1.
Processed 5032 pages for database ‘tp_v5_dev’, file ‘History06a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History06b’ on file 1.
Processed 6936 pages for database ‘tp_v5_dev’, file ‘History07a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History07b’ on file 1.
Processed 10904 pages for database ‘tp_v5_dev’, file ‘History08a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History08b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG06_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG07_PageFile01’ on file 1.
Processed 1814280 pages for database ‘tp_v5_dev’, file ‘HistoryData01’ on file 1.
Processed 1674784 pages for database ‘tp_v5_dev’, file ‘HistoryData03’ on file 1.
Processed 1657248 pages for database ‘tp_v5_dev’, file ‘HistoryData05’ on file 1.
Processed 1182680 pages for database ‘tp_v5_dev’, file ‘LoadData02’ on file 1.
Processed 1150464 pages for database ‘tp_v5_dev’, file ‘LoadData04’ on file 1.
Processed 1385080 pages for database ‘tp_v5_dev’, file ‘LoadData01’ on file 1.
Processed 1230520 pages for database ‘tp_v5_dev’, file ‘LoadData03’ on file 1.
Processed 357776 pages for database ‘tp_v5_dev’, file ‘MiscData2’ on file 1.
Processed 324864 pages for database ‘tp_v5_dev’, file ‘MiscData1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG08_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG09_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG10_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG11_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG12_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG13_PageFile01’ on file 1.
Processed 5112 pages for database ‘tp_v5_dev’, file ‘History10_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History10_02’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00a’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00b’ on file 1.
Processed 32608 pages for database ‘tp_v5_dev’, file ‘Loadfg01a’ on file 1.
Processed 42000 pages for database ‘tp_v5_dev’, file ‘Loadfg01b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG14_PageFile01’ on file 1.
Processed 5168 pages for database ‘tp_v5_dev’, file ‘History09b1’ on file 1.
Processed 464 pages for database ‘tp_v5_dev’, file ‘History09b2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09c1’ on file 1.
Processed 5688 pages for database ‘tp_v5_dev’, file ‘History09c2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09d1’ on file 1.
Processed 5760 pages for database ‘tp_v5_dev’, file ‘History09d2’ on file 1.
Processed 6488 pages for database ‘tp_v5_dev’, file ‘History10a1’ on file 1.
Processed 432 pages for database ‘tp_v5_dev’, file ‘History10a2’ on file 1.
Processed 8784 pages for database ‘tp_v5_dev’, file ‘History10b1’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History10b2’ on file 1.
Processed 20240 pages for database ‘tp_v5_dev’, file ‘History10c2’ on file 1.
Processed 55416 pages for database ‘tp_v5_dev’, file ‘History10d2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive02’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘Archive03’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Loadfg02a’ on file 1.
Processed 41488 pages for database ‘tp_v5_dev’, file ‘Loadfg02b’ on file 1.
Processed 43032 pages for database ‘tp_v5_dev’, file ‘Loadfg03a’ on file 1.
Processed 43448 pages for database ‘tp_v5_dev’, file ‘Loadfg03b’ on file 1.
Processed 40976 pages for database ‘tp_v5_dev’, file ‘Loadfg04a’ on file 1.
Processed 41248 pages for database ‘tp_v5_dev’, file ‘Loadfg04b’ on file 1.
Processed 34376 pages for database ‘tp_v5_dev’, file ‘Loadfg05a’ on file 1.
Processed 47120 pages for database ‘tp_v5_dev’, file ‘Loadfg05b’ on file 1.
Processed 44816 pages for database ‘tp_v5_dev’, file ‘Loadfg06a’ on file 1.
Processed 45072 pages for database ‘tp_v5_dev’, file ‘Loadfg06b’ on file 1.
Processed 44056 pages for database ‘tp_v5_dev’, file ‘Loadfg07a’ on file 1.
Processed 44344 pages for database ‘tp_v5_dev’, file ‘Loadfg07b’ on file 1.
Processed 41976 pages for database ‘tp_v5_dev’, file ‘Loadfg08a’ on file 1.
Processed 48648 pages for database ‘tp_v5_dev’, file ‘Loadfg08b’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09a’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09b’ on file 1.
Processed 51208 pages for database ‘tp_v5_dev’, file ‘Loadfg10a’ on file 1.
Processed 55432 pages for database ‘tp_v5_dev’, file ‘Loadfg10b’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg11d’ on file 1.
Processed 46096 pages for database ‘tp_v5_dev’, file ‘Loadfg11a’ on file 1.
Processed 49672 pages for database ‘tp_v5_dev’, file ‘Loadfg11b’ on file 1.
Processed 46864 pages for database ‘tp_v5_dev’, file ‘Loadfg12a’ on file 1.
Processed 60424 pages for database ‘tp_v5_dev’, file ‘Loadfg12b’ on file 1.
Processed 41496 pages for database ‘tp_v5_dev’, file ‘Loadfg13a’ on file 1.
Processed 50808 pages for database ‘tp_v5_dev’, file ‘Loadfg13b’ on file 1.
Processed 35872 pages for database ‘tp_v5_dev’, file ‘Loadfg14a’ on file 1.
Processed 45192 pages for database ‘tp_v5_dev’, file ‘Loadfg14b’ on file 1.
Processed 45080 pages for database ‘tp_v5_dev’, file ‘Loadfg15a’ on file 1.
Processed 54352 pages for database ‘tp_v5_dev’, file ‘Loadfg15b’ on file 1.
Processed 39664 pages for database ‘tp_v5_dev’, file ‘Loadfg16a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg16b’ on file 1.
Processed 39624 pages for database ‘tp_v5_dev’, file ‘Loadfg17a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg17b’ on file 1.
Processed 41328 pages for database ‘tp_v5_dev’, file ‘Loadfg18a’ on file 1.
Processed 54784 pages for database ‘tp_v5_dev’, file ‘Loadfg18b’ on file 1.
Processed 116240 pages for database ‘tp_v5_dev’, file ‘Loadfg19a’ on file 1.
Processed 119688 pages for database ‘tp_v5_dev’, file ‘Loadfg19b’ on file 1.
Processed 131088 pages for database ‘tp_v5_dev’, file ‘Loadfg20a’ on file 1.
Processed 91656 pages for database ‘tp_v5_dev’, file ‘Loadfg20b’ on file 1.
Processed 71296 pages for database ‘tp_v5_dev’, file ‘Loadfg21a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg21b’ on file 1.
Processed 74768 pages for database ‘tp_v5_dev’, file ‘Loadfg22a’ on file 1.
Processed 96832 pages for database ‘tp_v5_dev’, file ‘Loadfg22b’ on file 1.
Processed 71224 pages for database ‘tp_v5_dev’, file ‘Loadfg23a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg23b’ on file 1.
Processed 76200 pages for database ‘tp_v5_dev’, file ‘Loadfg24a’ on file 1.
Processed 98312 pages for database ‘tp_v5_dev’, file ‘Loadfg24b’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘SimIndex01’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex02’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex04’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex05’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Sim42’ on file 1.
Processed 65472 pages for database ‘tp_v5_dev’, file ‘History11a1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11a2’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday03’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday04’ on file 1.
Processed 64744 pages for database ‘tp_v5_dev’, file ‘History11b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11b2’ on file 1.
Processed 73344 pages for database ‘tp_v5_dev’, file ‘History11c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History11d1’ on file 1.
Processed 34704 pages for database ‘tp_v5_dev’, file ‘History11d2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12a1’ on file 1.
Processed 144 pages for database ‘tp_v5_dev’, file ‘History12a2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12b2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12c1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12d1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12d2’ on file 1.
Processed 94912 pages for database ‘tp_v5_dev’, file ‘loadfg25a’ on file 1.
Processed 105168 pages for database ‘tp_v5_dev’, file ‘loadfg25b’ on file 1.
Processed 112320 pages for database ‘tp_v5_dev’, file ‘loadfg26a’ on file 1.
Processed 114832 pages for database ‘tp_v5_dev’, file ‘loadfg26b’ on file 1.
Processed 129792 pages for database ‘tp_v5_dev’, file ‘loadfg27a’ on file 1.
Processed 145840 pages for database ‘tp_v5_dev’, file ‘loadfg27b’ on file 1.
Processed 114000 pages for database ‘tp_v5_dev’, file ‘loadfg28a’ on file 1.
Processed 115704 pages for database ‘tp_v5_dev’, file ‘loadfg28b’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg29a’ on file 1.
Processed 116640 pages for database ‘tp_v5_dev’, file ‘loadfg29b’ on file 1.
Processed 127136 pages for database ‘tp_v5_dev’, file ‘loadfg30a’ on file 1.
Processed 137128 pages for database ‘tp_v5_dev’, file ‘loadfg30b’ on file 1.
Processed 114208 pages for database ‘tp_v5_dev’, file ‘loadfg31a’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg31b’ on file 1.
Processed 130200 pages for database ‘tp_v5_dev’, file ‘loadfg32a’ on file 1.
Processed 139536 pages for database ‘tp_v5_dev’, file ‘loadfg32b’ on file 1.
Processed 114648 pages for database ‘tp_v5_dev’, file ‘loadfg33a’ on file 1.
Processed 126072 pages for database ‘tp_v5_dev’, file ‘loadfg33b’ on file 1.
Processed 113184 pages for database ‘tp_v5_dev’, file ‘loadfg34a’ on file 1.
Processed 122184 pages for database ‘tp_v5_dev’, file ‘loadfg34b’ on file 1.
Processed 105432 pages for database ‘tp_v5_dev’, file ‘loadfg35a’ on file 1.
Processed 126624 pages for database ‘tp_v5_dev’, file ‘loadfg35b’ on file 1.
Processed 111752 pages for database ‘tp_v5_dev’, file ‘loadfg36a’ on file 1.
Processed 121128 pages for database ‘tp_v5_dev’, file ‘loadfg36b’ on file 1.
Processed 150920 pages for database ‘tp_v5_dev’, file ‘Loadfg37a’ on file 1.
Processed 64000 pages for database ‘tp_v5_dev’, file ‘Loadfg37b’ on file 1.
Processed 113976 pages for database ‘tp_v5_dev’, file ‘load38_01’ on file 1.
Processed 102400 pages for database ‘tp_v5_dev’, file ‘load38_02’ on file 1.
Processed 121368 pages for database ‘tp_v5_dev’, file ‘load39_01’ on file 1.
Processed 115200 pages for database ‘tp_v5_dev’, file ‘load39_02’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG15_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG16_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG17_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG18_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG19_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG20_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG21_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG22_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG23_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG24_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG25_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG26_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG27_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG28_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG29_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG30_PageFile01’ on file 1.
Processed 44448 pages for database ‘tp_v5_dev’, file ‘Interval_01’ on file 1.
Processed 60544 pages for database ‘tp_v5_dev’, file ‘Interval_fg01a’ on file 1.
Processed 65752 pages for database ‘tp_v5_dev’, file ‘Interval_fg01b’ on file 1.
Processed 71600 pages for database ‘tp_v5_dev’, file ‘Interval_fg01c’ on file 1.
Processed 32168 pages for database ‘tp_v5_dev’, file ‘Interval_02’ on file 1.
Processed 58416 pages for database ‘tp_v5_dev’, file ‘Interval_fg02a’ on file 1.
Processed 58336 pages for database ‘tp_v5_dev’, file ‘Interval_fg02b’ on file 1.
Processed 75624 pages for database ‘tp_v5_dev’, file ‘Interval_fg02c’ on file 1.
Processed 35632 pages for database ‘tp_v5_dev’, file ‘Interval_03’ on file 1.
Processed 64488 pages for database ‘tp_v5_dev’, file ‘Interval_fg03a’ on file 1.
Processed 73336 pages for database ‘tp_v5_dev’, file ‘Interval_fg03b’ on file 1.
Processed 73776 pages for database ‘tp_v5_dev’, file ‘Interval_fg03c’ on file 1.
Processed 11456 pages for database ‘tp_v5_dev’, file ‘Interval_04’ on file 1.
Processed 30584 pages for database ‘tp_v5_dev’, file ‘Interval_fg04a’ on file 1.
Processed 30392 pages for database ‘tp_v5_dev’, file ‘Interval_fg04b’ on file 1.
Processed 31688 pages for database ‘tp_v5_dev’, file ‘Interval_fg04c’ on file 1.
Processed 38992 pages for database ‘tp_v5_dev’, file ‘Interval_fg05a’ on file 1.
Processed 38896 pages for database ‘tp_v5_dev’, file ‘Interval_fg05b’ on file 1.
Processed 39304 pages for database ‘tp_v5_dev’, file ‘Interval_fg05c’ on file 1.
Processed 22016 pages for database ‘tp_v5_dev’, file ‘Interval_06’ on file 1.
Processed 38704 pages for database ‘tp_v5_dev’, file ‘Interval_fg06a’ on file 1.
Processed 35408 pages for database ‘tp_v5_dev’, file ‘Interval_fg06b’ on file 1.
Processed 34840 pages for database ‘tp_v5_dev’, file ‘Interval_fg06c’ on file 1.
Processed 45920 pages for database ‘tp_v5_dev’, file ‘Interval_fg07a’ on file 1.
Processed 47080 pages for database ‘tp_v5_dev’, file ‘Interval_fg07b’ on file 1.
Processed 52416 pages for database ‘tp_v5_dev’, file ‘Interval_fg07c’ on file 1.
Processed 55120 pages for database ‘tp_v5_dev’, file ‘Interval_fg08a’ on file 1.
Processed 60064 pages for database ‘tp_v5_dev’, file ‘Interval_fg08b’ on file 1.
Processed 61808 pages for database ‘tp_v5_dev’, file ‘Interval_fg08c’ on file 1.
Processed 32392 pages for database ‘tp_v5_dev’, file ‘Interval_09’ on file 1.
Processed 64872 pages for database ‘tp_v5_dev’, file ‘Interval_fg09a’ on file 1.
Processed 63080 pages for database ‘tp_v5_dev’, file ‘Interval_fg09b’ on file 1.
Processed 60840 pages for database ‘tp_v5_dev’, file ‘Interval_fg09c’ on file 1.
Processed 13992 pages for database ‘tp_v5_dev’, file ‘Interval_10’ on file 1.
Processed 16272 pages for database ‘tp_v5_dev’, file ‘Interval_fg10a’ on file 1.
Processed 13352 pages for database ‘tp_v5_dev’, file ‘Interval_fg10b’ on file 1.
Processed 27160 pages for database ‘tp_v5_dev’, file ‘Interval_fg10c’ on file 1.
Processed 14720 pages for database ‘tp_v5_dev’, file ‘Interval_11’ on file 1.
Processed 16680 pages for database ‘tp_v5_dev’, file ‘Interval_fg11a’ on file 1.
Processed 28184 pages for database ‘tp_v5_dev’, file ‘Interval_fg11b’ on file 1.
Processed 13784 pages for database ‘tp_v5_dev’, file ‘Interval_fg11c’ on file 1.
Processed 15744 pages for database ‘tp_v5_dev’, file ‘Interval_12’ on file 1.
Processed 15040 pages for database ‘tp_v5_dev’, file ‘Interval_fg12a’ on file 1.
Processed 13936 pages for database ‘tp_v5_dev’, file ‘Interval_fg12b’ on file 1.
Processed 29944 pages for database ‘tp_v5_dev’, file ‘Interval_fg12c’ on file 1.
Processed 13200 pages for database ‘tp_v5_dev’, file ‘Interval_13’ on file 1.
Processed 23584 pages for database ‘tp_v5_dev’, file ‘Interval_fg13a’ on file 1.
Processed 12904 pages for database ‘tp_v5_dev’, file ‘Interval_fg13b’ on file 1.
Processed 26776 pages for database ‘tp_v5_dev’, file ‘Interval_fg13c’ on file 1.
Processed 15296 pages for database ‘tp_v5_dev’, file ‘Interval_14’ on file 1.
Processed 17840 pages for database ‘tp_v5_dev’, file ‘Interval_fg14a’ on file 1.
Processed 12320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14b’ on file 1.
Processed 28320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14c’ on file 1.
Processed 18400 pages for database ‘tp_v5_dev’, file ‘Interval_fg15a’ on file 1.
Processed 28928 pages for database ‘tp_v5_dev’, file ‘Interval_fg15b’ on file 1.
Processed 30744 pages for database ‘tp_v5_dev’, file ‘Interval_fg15c’ on file 1.
Processed 30088 pages for database ‘tp_v5_dev’, file ‘Interval_fg16a’ on file 1.
Processed 16184 pages for database ‘tp_v5_dev’, file ‘Interval_fg16b’ on file 1.
Processed 36504 pages for database ‘tp_v5_dev’, file ‘Interval_fg16c’ on file 1.
Processed 18968 pages for database ‘tp_v5_dev’, file ‘Interval_17’ on file 1.
Processed 14592 pages for database ‘tp_v5_dev’, file ‘Interval_fg17a’ on file 1.
Processed 30032 pages for database ‘tp_v5_dev’, file ‘Interval_fg17b’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Interval_fg17c’ on file 1.
Processed 22392 pages for database ‘tp_v5_dev’, file ‘Interval_fg18a’ on file 1.
Processed 30136 pages for database ‘tp_v5_dev’, file ‘Interval_fg18b’ on file 1.
Processed 37224 pages for database ‘tp_v5_dev’, file ‘Interval_fg18c’ on file 1.
Processed 33616 pages for database ‘tp_v5_dev’, file ‘Interval_fg19a’ on file 1.
Processed 30024 pages for database ‘tp_v5_dev’, file ‘Interval_fg19b’ on file 1.
Processed 29864 pages for database ‘tp_v5_dev’, file ‘Interval_fg19c’ on file 1.
Processed 36248 pages for database ‘tp_v5_dev’, file ‘Interval_20a’ on file 1.
Processed 27616 pages for database ‘tp_v5_dev’, file ‘Interval_20b’ on file 1.
Processed 27376 pages for database ‘tp_v5_dev’, file ‘Interval_20c’ on file 1.
Processed 12632 pages for database ‘tp_v5_dev’, file ‘Interval_21’ on file 1.
Processed 13080 pages for database ‘tp_v5_dev’, file ‘Interval_fg21a’ on file 1.
Processed 24608 pages for database ‘tp_v5_dev’, file ‘Interval_fg21b’ on file 1.
Processed 24288 pages for database ‘tp_v5_dev’, file ‘Interval_fg21c’ on file 1.
Processed 736 pages for database ‘tp_v5_dev’, file ‘Interval_22b’ on file 1.
Processed 992 pages for database ‘tp_v5_dev’, file ‘Interval_fg22a’ on file 1.
Processed 1032 pages for database ‘tp_v5_dev’, file ‘Interval_fg22b’ on file 1.
Processed 1088 pages for database ‘tp_v5_dev’, file ‘Interval_fg22c’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg01_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg02_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg03_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg04_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg05_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg06_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg07_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg08_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg09_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg10_File01’ on file 1.
Processed 768 pages for database ‘tp_v5_dev’, file ‘Interval_fg23a’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23b’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23c’ on file 1.
Processed 838952 pages for database ‘tp_v5_dev’, file ‘Interval_fg24a’ on file 1.
Processed 732784 pages for database ‘tp_v5_dev’, file ‘Interval_fg24b’ on file 1.
Processed 804256 pages for database ‘tp_v5_dev’, file ‘Interval_fg24c’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25a’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25b’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25c’ on file 1.
Processed 219528 pages for database ‘tp_v5_dev’, file ‘Load40_01’ on file 1.
Processed 156968 pages for database ‘tp_v5_dev’, file ‘Load41_01’ on file 1.
Processed 169880 pages for database ‘tp_v5_dev’, file ‘Load42_01’ on file 1.
Processed 860640 pages for database ‘tp_v5_dev’, file ‘Load43_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load44_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load45_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load46_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load47_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load48_01’ on file 1.
100 percent processed.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2_log’ on file 1.
Processed 2 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog2’ on file 1.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog3’ on file 1.
BACKUP DATABASE successfully processed 23884890 pages in 58.395 seconds (3195.491 MB/sec).

RESUTS (Backup TO NUL – forgot to include the query in the output)

10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Processed 25288 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG01_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG02_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG03_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG04_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG05_PageFile01’ on file 1.
Processed 17584 pages for database ‘tp_v5_dev’, file ‘History09a’ on file 1.
Processed 1680 pages for database ‘tp_v5_dev’, file ‘History09b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History01_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History01_02’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History02a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History02b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History03a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History03b’ on file 1.
Processed 2736 pages for database ‘tp_v5_dev’, file ‘History04a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History04b’ on file 1.
Processed 3400 pages for database ‘tp_v5_dev’, file ‘History05a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History05b’ on file 1.
Processed 5032 pages for database ‘tp_v5_dev’, file ‘History06a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History06b’ on file 1.
Processed 6936 pages for database ‘tp_v5_dev’, file ‘History07a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History07b’ on file 1.
Processed 10904 pages for database ‘tp_v5_dev’, file ‘History08a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History08b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG06_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG07_PageFile01’ on file 1.
Processed 1814280 pages for database ‘tp_v5_dev’, file ‘HistoryData01’ on file 1.
Processed 1674784 pages for database ‘tp_v5_dev’, file ‘HistoryData03’ on file 1.
Processed 1657248 pages for database ‘tp_v5_dev’, file ‘HistoryData05’ on file 1.
Processed 1182680 pages for database ‘tp_v5_dev’, file ‘LoadData02’ on file 1.
Processed 1150464 pages for database ‘tp_v5_dev’, file ‘LoadData04’ on file 1.
Processed 1385080 pages for database ‘tp_v5_dev’, file ‘LoadData01’ on file 1.
Processed 1230520 pages for database ‘tp_v5_dev’, file ‘LoadData03’ on file 1.
Processed 357776 pages for database ‘tp_v5_dev’, file ‘MiscData2’ on file 1.
Processed 324864 pages for database ‘tp_v5_dev’, file ‘MiscData1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG08_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG09_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG10_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG11_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG12_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG13_PageFile01’ on file 1.
Processed 5112 pages for database ‘tp_v5_dev’, file ‘History10_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History10_02’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00a’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00b’ on file 1.
Processed 32608 pages for database ‘tp_v5_dev’, file ‘Loadfg01a’ on file 1.
Processed 42000 pages for database ‘tp_v5_dev’, file ‘Loadfg01b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG14_PageFile01’ on file 1.
Processed 5168 pages for database ‘tp_v5_dev’, file ‘History09b1’ on file 1.
Processed 464 pages for database ‘tp_v5_dev’, file ‘History09b2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09c1’ on file 1.
Processed 5688 pages for database ‘tp_v5_dev’, file ‘History09c2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09d1’ on file 1.
Processed 5760 pages for database ‘tp_v5_dev’, file ‘History09d2’ on file 1.
Processed 6488 pages for database ‘tp_v5_dev’, file ‘History10a1’ on file 1.
Processed 432 pages for database ‘tp_v5_dev’, file ‘History10a2’ on file 1.
Processed 8784 pages for database ‘tp_v5_dev’, file ‘History10b1’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History10b2’ on file 1.
Processed 20240 pages for database ‘tp_v5_dev’, file ‘History10c2’ on file 1.
Processed 55416 pages for database ‘tp_v5_dev’, file ‘History10d2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive02’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘Archive03’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Loadfg02a’ on file 1.
Processed 41488 pages for database ‘tp_v5_dev’, file ‘Loadfg02b’ on file 1.
Processed 43032 pages for database ‘tp_v5_dev’, file ‘Loadfg03a’ on file 1.
Processed 43448 pages for database ‘tp_v5_dev’, file ‘Loadfg03b’ on file 1.
Processed 40976 pages for database ‘tp_v5_dev’, file ‘Loadfg04a’ on file 1.
Processed 41248 pages for database ‘tp_v5_dev’, file ‘Loadfg04b’ on file 1.
Processed 34376 pages for database ‘tp_v5_dev’, file ‘Loadfg05a’ on file 1.
Processed 47120 pages for database ‘tp_v5_dev’, file ‘Loadfg05b’ on file 1.
Processed 44816 pages for database ‘tp_v5_dev’, file ‘Loadfg06a’ on file 1.
Processed 45072 pages for database ‘tp_v5_dev’, file ‘Loadfg06b’ on file 1.
Processed 44056 pages for database ‘tp_v5_dev’, file ‘Loadfg07a’ on file 1.
Processed 44344 pages for database ‘tp_v5_dev’, file ‘Loadfg07b’ on file 1.
Processed 41976 pages for database ‘tp_v5_dev’, file ‘Loadfg08a’ on file 1.
Processed 48648 pages for database ‘tp_v5_dev’, file ‘Loadfg08b’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09a’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09b’ on file 1.
Processed 51208 pages for database ‘tp_v5_dev’, file ‘Loadfg10a’ on file 1.
Processed 55432 pages for database ‘tp_v5_dev’, file ‘Loadfg10b’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg11d’ on file 1.
Processed 46096 pages for database ‘tp_v5_dev’, file ‘Loadfg11a’ on file 1.
Processed 49672 pages for database ‘tp_v5_dev’, file ‘Loadfg11b’ on file 1.
Processed 46864 pages for database ‘tp_v5_dev’, file ‘Loadfg12a’ on file 1.
Processed 60424 pages for database ‘tp_v5_dev’, file ‘Loadfg12b’ on file 1.
Processed 41496 pages for database ‘tp_v5_dev’, file ‘Loadfg13a’ on file 1.
Processed 50808 pages for database ‘tp_v5_dev’, file ‘Loadfg13b’ on file 1.
Processed 35872 pages for database ‘tp_v5_dev’, file ‘Loadfg14a’ on file 1.
Processed 45192 pages for database ‘tp_v5_dev’, file ‘Loadfg14b’ on file 1.
Processed 45080 pages for database ‘tp_v5_dev’, file ‘Loadfg15a’ on file 1.
Processed 54352 pages for database ‘tp_v5_dev’, file ‘Loadfg15b’ on file 1.
Processed 39664 pages for database ‘tp_v5_dev’, file ‘Loadfg16a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg16b’ on file 1.
Processed 39624 pages for database ‘tp_v5_dev’, file ‘Loadfg17a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg17b’ on file 1.
Processed 41328 pages for database ‘tp_v5_dev’, file ‘Loadfg18a’ on file 1.
Processed 54784 pages for database ‘tp_v5_dev’, file ‘Loadfg18b’ on file 1.
Processed 116240 pages for database ‘tp_v5_dev’, file ‘Loadfg19a’ on file 1.
Processed 119688 pages for database ‘tp_v5_dev’, file ‘Loadfg19b’ on file 1.
Processed 131088 pages for database ‘tp_v5_dev’, file ‘Loadfg20a’ on file 1.
Processed 91656 pages for database ‘tp_v5_dev’, file ‘Loadfg20b’ on file 1.
Processed 71296 pages for database ‘tp_v5_dev’, file ‘Loadfg21a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg21b’ on file 1.
Processed 74768 pages for database ‘tp_v5_dev’, file ‘Loadfg22a’ on file 1.
Processed 96832 pages for database ‘tp_v5_dev’, file ‘Loadfg22b’ on file 1.
Processed 71224 pages for database ‘tp_v5_dev’, file ‘Loadfg23a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg23b’ on file 1.
Processed 76200 pages for database ‘tp_v5_dev’, file ‘Loadfg24a’ on file 1.
Processed 98312 pages for database ‘tp_v5_dev’, file ‘Loadfg24b’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘SimIndex01’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex02’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex04’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex05’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Sim42’ on file 1.
Processed 65472 pages for database ‘tp_v5_dev’, file ‘History11a1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11a2’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday03’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday04’ on file 1.
Processed 64744 pages for database ‘tp_v5_dev’, file ‘History11b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11b2’ on file 1.
Processed 73344 pages for database ‘tp_v5_dev’, file ‘History11c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History11d1’ on file 1.
Processed 34704 pages for database ‘tp_v5_dev’, file ‘History11d2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12a1’ on file 1.
Processed 144 pages for database ‘tp_v5_dev’, file ‘History12a2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12b2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12c1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12d1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12d2’ on file 1.
Processed 94912 pages for database ‘tp_v5_dev’, file ‘loadfg25a’ on file 1.
Processed 105168 pages for database ‘tp_v5_dev’, file ‘loadfg25b’ on file 1.
Processed 112320 pages for database ‘tp_v5_dev’, file ‘loadfg26a’ on file 1.
Processed 114832 pages for database ‘tp_v5_dev’, file ‘loadfg26b’ on file 1.
Processed 129792 pages for database ‘tp_v5_dev’, file ‘loadfg27a’ on file 1.
Processed 145840 pages for database ‘tp_v5_dev’, file ‘loadfg27b’ on file 1.
Processed 114000 pages for database ‘tp_v5_dev’, file ‘loadfg28a’ on file 1.
Processed 115704 pages for database ‘tp_v5_dev’, file ‘loadfg28b’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg29a’ on file 1.
Processed 116640 pages for database ‘tp_v5_dev’, file ‘loadfg29b’ on file 1.
Processed 127136 pages for database ‘tp_v5_dev’, file ‘loadfg30a’ on file 1.
Processed 137128 pages for database ‘tp_v5_dev’, file ‘loadfg30b’ on file 1.
Processed 114208 pages for database ‘tp_v5_dev’, file ‘loadfg31a’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg31b’ on file 1.
Processed 130200 pages for database ‘tp_v5_dev’, file ‘loadfg32a’ on file 1.
Processed 139536 pages for database ‘tp_v5_dev’, file ‘loadfg32b’ on file 1.
Processed 114648 pages for database ‘tp_v5_dev’, file ‘loadfg33a’ on file 1.
Processed 126072 pages for database ‘tp_v5_dev’, file ‘loadfg33b’ on file 1.
Processed 113184 pages for database ‘tp_v5_dev’, file ‘loadfg34a’ on file 1.
Processed 122184 pages for database ‘tp_v5_dev’, file ‘loadfg34b’ on file 1.
Processed 105432 pages for database ‘tp_v5_dev’, file ‘loadfg35a’ on file 1.
Processed 126624 pages for database ‘tp_v5_dev’, file ‘loadfg35b’ on file 1.
Processed 111752 pages for database ‘tp_v5_dev’, file ‘loadfg36a’ on file 1.
Processed 121128 pages for database ‘tp_v5_dev’, file ‘loadfg36b’ on file 1.
Processed 150920 pages for database ‘tp_v5_dev’, file ‘Loadfg37a’ on file 1.
Processed 64000 pages for database ‘tp_v5_dev’, file ‘Loadfg37b’ on file 1.
Processed 113976 pages for database ‘tp_v5_dev’, file ‘load38_01’ on file 1.
Processed 102400 pages for database ‘tp_v5_dev’, file ‘load38_02’ on file 1.
Processed 121368 pages for database ‘tp_v5_dev’, file ‘load39_01’ on file 1.
Processed 115200 pages for database ‘tp_v5_dev’, file ‘load39_02’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG15_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG16_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG17_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG18_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG19_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG20_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG21_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG22_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG23_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG24_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG25_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG26_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG27_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG28_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG29_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG30_PageFile01’ on file 1.
Processed 44448 pages for database ‘tp_v5_dev’, file ‘Interval_01’ on file 1.
Processed 60544 pages for database ‘tp_v5_dev’, file ‘Interval_fg01a’ on file 1.
Processed 65752 pages for database ‘tp_v5_dev’, file ‘Interval_fg01b’ on file 1.
Processed 71600 pages for database ‘tp_v5_dev’, file ‘Interval_fg01c’ on file 1.
Processed 32168 pages for database ‘tp_v5_dev’, file ‘Interval_02’ on file 1.
Processed 58416 pages for database ‘tp_v5_dev’, file ‘Interval_fg02a’ on file 1.
Processed 58336 pages for database ‘tp_v5_dev’, file ‘Interval_fg02b’ on file 1.
Processed 75624 pages for database ‘tp_v5_dev’, file ‘Interval_fg02c’ on file 1.
Processed 35632 pages for database ‘tp_v5_dev’, file ‘Interval_03’ on file 1.
Processed 64488 pages for database ‘tp_v5_dev’, file ‘Interval_fg03a’ on file 1.
Processed 73336 pages for database ‘tp_v5_dev’, file ‘Interval_fg03b’ on file 1.
Processed 73776 pages for database ‘tp_v5_dev’, file ‘Interval_fg03c’ on file 1.
Processed 11456 pages for database ‘tp_v5_dev’, file ‘Interval_04’ on file 1.
Processed 30584 pages for database ‘tp_v5_dev’, file ‘Interval_fg04a’ on file 1.
Processed 30392 pages for database ‘tp_v5_dev’, file ‘Interval_fg04b’ on file 1.
Processed 31688 pages for database ‘tp_v5_dev’, file ‘Interval_fg04c’ on file 1.
Processed 38992 pages for database ‘tp_v5_dev’, file ‘Interval_fg05a’ on file 1.
Processed 38896 pages for database ‘tp_v5_dev’, file ‘Interval_fg05b’ on file 1.
Processed 39304 pages for database ‘tp_v5_dev’, file ‘Interval_fg05c’ on file 1.
Processed 22016 pages for database ‘tp_v5_dev’, file ‘Interval_06’ on file 1.
Processed 38704 pages for database ‘tp_v5_dev’, file ‘Interval_fg06a’ on file 1.
Processed 35408 pages for database ‘tp_v5_dev’, file ‘Interval_fg06b’ on file 1.
Processed 34840 pages for database ‘tp_v5_dev’, file ‘Interval_fg06c’ on file 1.
Processed 45920 pages for database ‘tp_v5_dev’, file ‘Interval_fg07a’ on file 1.
Processed 47080 pages for database ‘tp_v5_dev’, file ‘Interval_fg07b’ on file 1.
Processed 52416 pages for database ‘tp_v5_dev’, file ‘Interval_fg07c’ on file 1.
Processed 55120 pages for database ‘tp_v5_dev’, file ‘Interval_fg08a’ on file 1.
Processed 60064 pages for database ‘tp_v5_dev’, file ‘Interval_fg08b’ on file 1.
Processed 61808 pages for database ‘tp_v5_dev’, file ‘Interval_fg08c’ on file 1.
Processed 32392 pages for database ‘tp_v5_dev’, file ‘Interval_09’ on file 1.
Processed 64872 pages for database ‘tp_v5_dev’, file ‘Interval_fg09a’ on file 1.
Processed 63080 pages for database ‘tp_v5_dev’, file ‘Interval_fg09b’ on file 1.
Processed 60840 pages for database ‘tp_v5_dev’, file ‘Interval_fg09c’ on file 1.
Processed 13992 pages for database ‘tp_v5_dev’, file ‘Interval_10’ on file 1.
Processed 16272 pages for database ‘tp_v5_dev’, file ‘Interval_fg10a’ on file 1.
Processed 13352 pages for database ‘tp_v5_dev’, file ‘Interval_fg10b’ on file 1.
Processed 27160 pages for database ‘tp_v5_dev’, file ‘Interval_fg10c’ on file 1.
Processed 14720 pages for database ‘tp_v5_dev’, file ‘Interval_11’ on file 1.
Processed 16680 pages for database ‘tp_v5_dev’, file ‘Interval_fg11a’ on file 1.
Processed 28184 pages for database ‘tp_v5_dev’, file ‘Interval_fg11b’ on file 1.
Processed 13784 pages for database ‘tp_v5_dev’, file ‘Interval_fg11c’ on file 1.
Processed 15744 pages for database ‘tp_v5_dev’, file ‘Interval_12’ on file 1.
Processed 15040 pages for database ‘tp_v5_dev’, file ‘Interval_fg12a’ on file 1.
Processed 13936 pages for database ‘tp_v5_dev’, file ‘Interval_fg12b’ on file 1.
Processed 29944 pages for database ‘tp_v5_dev’, file ‘Interval_fg12c’ on file 1.
Processed 13200 pages for database ‘tp_v5_dev’, file ‘Interval_13’ on file 1.
Processed 23584 pages for database ‘tp_v5_dev’, file ‘Interval_fg13a’ on file 1.
Processed 12904 pages for database ‘tp_v5_dev’, file ‘Interval_fg13b’ on file 1.
Processed 26776 pages for database ‘tp_v5_dev’, file ‘Interval_fg13c’ on file 1.
Processed 15296 pages for database ‘tp_v5_dev’, file ‘Interval_14’ on file 1.
Processed 17840 pages for database ‘tp_v5_dev’, file ‘Interval_fg14a’ on file 1.
Processed 12320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14b’ on file 1.
Processed 28320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14c’ on file 1.
Processed 18400 pages for database ‘tp_v5_dev’, file ‘Interval_fg15a’ on file 1.
Processed 28928 pages for database ‘tp_v5_dev’, file ‘Interval_fg15b’ on file 1.
Processed 30744 pages for database ‘tp_v5_dev’, file ‘Interval_fg15c’ on file 1.
Processed 30088 pages for database ‘tp_v5_dev’, file ‘Interval_fg16a’ on file 1.
Processed 16184 pages for database ‘tp_v5_dev’, file ‘Interval_fg16b’ on file 1.
Processed 36504 pages for database ‘tp_v5_dev’, file ‘Interval_fg16c’ on file 1.
Processed 18968 pages for database ‘tp_v5_dev’, file ‘Interval_17’ on file 1.
Processed 14592 pages for database ‘tp_v5_dev’, file ‘Interval_fg17a’ on file 1.
Processed 30032 pages for database ‘tp_v5_dev’, file ‘Interval_fg17b’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Interval_fg17c’ on file 1.
Processed 22392 pages for database ‘tp_v5_dev’, file ‘Interval_fg18a’ on file 1.
Processed 30136 pages for database ‘tp_v5_dev’, file ‘Interval_fg18b’ on file 1.
Processed 37224 pages for database ‘tp_v5_dev’, file ‘Interval_fg18c’ on file 1.
Processed 33616 pages for database ‘tp_v5_dev’, file ‘Interval_fg19a’ on file 1.
Processed 30024 pages for database ‘tp_v5_dev’, file ‘Interval_fg19b’ on file 1.
Processed 29864 pages for database ‘tp_v5_dev’, file ‘Interval_fg19c’ on file 1.
Processed 36248 pages for database ‘tp_v5_dev’, file ‘Interval_20a’ on file 1.
Processed 27616 pages for database ‘tp_v5_dev’, file ‘Interval_20b’ on file 1.
Processed 27376 pages for database ‘tp_v5_dev’, file ‘Interval_20c’ on file 1.
Processed 12632 pages for database ‘tp_v5_dev’, file ‘Interval_21’ on file 1.
Processed 13080 pages for database ‘tp_v5_dev’, file ‘Interval_fg21a’ on file 1.
Processed 24608 pages for database ‘tp_v5_dev’, file ‘Interval_fg21b’ on file 1.
Processed 24288 pages for database ‘tp_v5_dev’, file ‘Interval_fg21c’ on file 1.
Processed 736 pages for database ‘tp_v5_dev’, file ‘Interval_22b’ on file 1.
Processed 992 pages for database ‘tp_v5_dev’, file ‘Interval_fg22a’ on file 1.
Processed 1032 pages for database ‘tp_v5_dev’, file ‘Interval_fg22b’ on file 1.
Processed 1088 pages for database ‘tp_v5_dev’, file ‘Interval_fg22c’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg01_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg02_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg03_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg04_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg05_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg06_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg07_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg08_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg09_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg10_File01’ on file 1.
Processed 768 pages for database ‘tp_v5_dev’, file ‘Interval_fg23a’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23b’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23c’ on file 1.
Processed 838952 pages for database ‘tp_v5_dev’, file ‘Interval_fg24a’ on file 1.
Processed 732784 pages for database ‘tp_v5_dev’, file ‘Interval_fg24b’ on file 1.
Processed 804256 pages for database ‘tp_v5_dev’, file ‘Interval_fg24c’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25a’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25b’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25c’ on file 1.
Processed 219528 pages for database ‘tp_v5_dev’, file ‘Load40_01’ on file 1.
Processed 156968 pages for database ‘tp_v5_dev’, file ‘Load41_01’ on file 1.
Processed 169880 pages for database ‘tp_v5_dev’, file ‘Load42_01’ on file 1.
Processed 860640 pages for database ‘tp_v5_dev’, file ‘Load43_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load44_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load45_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load46_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load47_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load48_01’ on file 1.
100 percent processed.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2_log’ on file 1.
Processed 2 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog2’ on file 1.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog3’ on file 1.
BACKUP DATABASE successfully processed 23884890 pages in 35.689 seconds (5228.521 MB/sec).

Posted in Uncategorized | Leave a comment

Now at 5.11 GB/s SQL backup to Null/3.12 GB/s local backup with I/O Accelerators

Posted on October 30, 2012 by Bob L

This will be my last update for a while, but I did some more shuffling of the database files among the various PCIE SSD logical drives (HP I/O Accelerators which are HP-OEM Fusion-Io cards). See earlier post for info about the drives. In the latest test, I got up to 5.11 GB/s (5228.521 MB/sec) doing the SQL Backup to NUL device. Given a 40 GbE network card and adequate destinations, that same number should be achievable for a “real” network SQL backup. This is raw throughput. As pointed out earlier, factoring in the database compression efficiency of 40% and typical storage overhead, this is an effective or logical data rate closer to 9.0 GB/s.  Also, improved the prior raw 3.05 GB/s to 3.12 GB/s (3195.491 MB/Sec) to local drives including the ioDrives – SQL showed up to 8 GB/s combined read/write throughput spikes – this is significantly above the 6.4 QPI limit, so if any individual QPI bottlenecks are in play, they are not all-encompassing. This time the database was distributed across all of the Duos and for the local backup test it was backed up using the SQL Backup command to all of the Duos along with an additional non-Duo MLC Drive, and 4 SATA SSDs.

SQL command outputs included at end of post for skeptics … Smile. If still not convinced this is possible, check my YouTube video at the 7 minute mark with demo referenced by the 3.05 GB/s post. 

This is utilizing 7 Duos spread across Windows-based Raid-0 and Raid-1 logical drives for the database (The ioDrives do not support hardware-based RAID).  In theory, RAID-1 is not be much slower than RAID-0 for read, so if all of the files were distributed evenly and read in parallel, the performance should be about twice that (7 * 1500 MB/s per Duo –>10.2 GB/s). Two issues seem to be complicating optimal performance:

1) The RAID-0 implementation from Windows Server – Not sure how it actually does this, but suspect that this involves buffering each data portion from the input drives together and then buffering out – normally this would be good for typical storage, but at these speeds almost any form of buffering just adds another bottleneck, particularly if it is saturating a QPI link. Based on that, better performance will probably be realized by distributing the files across non-Raid volumes, even the RAID-0. The database has dozens of files, but adding a lower level of granularity makes even file distribution more difficult. Depending on how low in the stack the RAID-0 is occurring, it could also be disadvantaged by the PCIE cards from different IOHs connected to different CPUs – can’t figure out which PCIE slots go to which IOHs – figure it is probably every other card or the first half of cards to one IOH and the other set to the other IOH.  Each logical read would need to bridge together the I/O from each device which would also involve a non-direct transfer from storage to CPU.

2) SQL Server backup internals – lack of knowledge is hurting me here. Not sure of all details of parallelization, but notice a balancing issue in that if one device has more data to read than another, it slows things down, but not to the degree as on the output balancing.  SQL also seems to perform the backup of the various database files in a manner not totally parallel – seemed to see some sequencing around portioned structures but not positive. It also does a final pass on the log, but that is not an issue here since there is noting in the transaction log at this point.

Trying to work through these issues will be time-consuming. Other things are more pressing, so will move onto other things and revisit later unless I stumble upon something in the interim. Thanks for the interest.

 

RESULTS (Local Backup)

/*————————
BACKUP DATABASE [tp_v5_dev] TO 
DISK = ‘j:\sqlbackup\tp_v5_dev_2012_10_28_j1.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k2.bak’,
DISK=  ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k3.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k4.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h5.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6b.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_7.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_8.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_9.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_10.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_11.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_12.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_13.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_14.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_15.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_16.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_17.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_18.bak’,
DISK = ‘i:\sqlbackup\tp_v5_dev_2012_10_28_j1_b.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k2_b.bak’,
DISK=  ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k3_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_k4_b.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_h5_b.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6_b.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6b_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_7_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_8_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_9_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_10_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_11_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_12_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_13_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_14_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_15_b.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_16_b.bak’,
DISK = ‘L:\sqlbackup\tp_v5_dev_2012_10_28_l_17_b.bak’,
DISK = ‘L:\sqlbackup\tp_v5_dev_2012_10_28_l_18_b.bak’,
DISK=  ‘k:\sqlbackup\tp_v5_dev_2012_10_28_k3_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_k4_c.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_h5_c.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_h6b_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_7_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_8_c.bak’,
DISK = ‘L:\sqlbackup\tp_v5_dev_2012_10_28_l_9_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_10_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_11_c.bak’,
DISK = ‘j:\sqlbackup\tp_v5_dev_2012_10_28_l_12_c.bak’,
DISK = ‘g:\sqlbackup\tp_v5_dev_2012_10_28_l_13_c.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_14_c.bak’,
DISK = ‘h:\sqlbackup\tp_v5_dev_2012_10_28_l_15_c.bak’,
DISK = ‘k:\sqlbackup\tp_v5_dev_2012_10_28_l_16_c.bak’,
DISK = ‘f:\sqlbackup\tp_v5_dev_2012_10_28_l_17_c.bak’,
DISK=  ‘J:\sqlbackup\tp_v5_dev_2012_10_28_k3_d.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_k4_d.bak’,
DISK = ‘F:\sqlbackup\tp_v5_dev_2012_10_28_l_8_d.bak’,
DISK = ‘l:\sqlbackup\tp_v5_dev_2012_10_28_l_10_d.bak’,
DISK = ‘H:\sqlbackup\tp_v5_dev_2012_10_28_l_11_d.bak’,
DISK = ‘H:\sqlbackup\tp_v5_dev_2012_10_28_l_12_d.bak’,
DISK = ‘K:\sqlbackup\tp_v5_dev_2012_10_28_l_14_d.bak’

— ‘NUL:’ — N’E:\SqlBackup\tp_v5_dev_20120708010002.BAK’ WITH NOFORMAT, NOINIT, 
— NAME = N’tp_v5_dev-Full Database Backup’,
— SKIP, NOREWIND, NOUNLOAD, 
–disk = ‘NUL:’
with STATS = 10, NOINIT, SKIP, — COPY_ONLY,
BUFFERCOUNT=1536, MAXTRANSFERSIZE=1048576, BLOCKSIZE=65536, NO_COMPRESSION
GO
————————*/
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Processed 25288 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG01_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG02_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG03_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG04_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG05_PageFile01’ on file 1.
Processed 17584 pages for database ‘tp_v5_dev’, file ‘History09a’ on file 1.
Processed 1680 pages for database ‘tp_v5_dev’, file ‘History09b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History01_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History01_02’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History02a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History02b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History03a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History03b’ on file 1.
Processed 2736 pages for database ‘tp_v5_dev’, file ‘History04a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History04b’ on file 1.
Processed 3400 pages for database ‘tp_v5_dev’, file ‘History05a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History05b’ on file 1.
Processed 5032 pages for database ‘tp_v5_dev’, file ‘History06a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History06b’ on file 1.
Processed 6936 pages for database ‘tp_v5_dev’, file ‘History07a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History07b’ on file 1.
Processed 10904 pages for database ‘tp_v5_dev’, file ‘History08a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History08b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG06_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG07_PageFile01’ on file 1.
Processed 1814280 pages for database ‘tp_v5_dev’, file ‘HistoryData01’ on file 1.
Processed 1674784 pages for database ‘tp_v5_dev’, file ‘HistoryData03’ on file 1.
Processed 1657248 pages for database ‘tp_v5_dev’, file ‘HistoryData05’ on file 1.
Processed 1182680 pages for database ‘tp_v5_dev’, file ‘LoadData02’ on file 1.
Processed 1150464 pages for database ‘tp_v5_dev’, file ‘LoadData04’ on file 1.
Processed 1385080 pages for database ‘tp_v5_dev’, file ‘LoadData01’ on file 1.
Processed 1230520 pages for database ‘tp_v5_dev’, file ‘LoadData03’ on file 1.
Processed 357776 pages for database ‘tp_v5_dev’, file ‘MiscData2’ on file 1.
Processed 324864 pages for database ‘tp_v5_dev’, file ‘MiscData1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG08_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG09_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG10_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG11_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG12_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG13_PageFile01’ on file 1.
Processed 5112 pages for database ‘tp_v5_dev’, file ‘History10_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History10_02’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00a’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00b’ on file 1.
Processed 32608 pages for database ‘tp_v5_dev’, file ‘Loadfg01a’ on file 1.
Processed 42000 pages for database ‘tp_v5_dev’, file ‘Loadfg01b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG14_PageFile01’ on file 1.
Processed 5168 pages for database ‘tp_v5_dev’, file ‘History09b1’ on file 1.
Processed 464 pages for database ‘tp_v5_dev’, file ‘History09b2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09c1’ on file 1.
Processed 5688 pages for database ‘tp_v5_dev’, file ‘History09c2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09d1’ on file 1.
Processed 5760 pages for database ‘tp_v5_dev’, file ‘History09d2’ on file 1.
Processed 6488 pages for database ‘tp_v5_dev’, file ‘History10a1’ on file 1.
Processed 432 pages for database ‘tp_v5_dev’, file ‘History10a2’ on file 1.
Processed 8784 pages for database ‘tp_v5_dev’, file ‘History10b1’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History10b2’ on file 1.
Processed 20240 pages for database ‘tp_v5_dev’, file ‘History10c2’ on file 1.
Processed 55416 pages for database ‘tp_v5_dev’, file ‘History10d2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive02’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘Archive03’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Loadfg02a’ on file 1.
Processed 41488 pages for database ‘tp_v5_dev’, file ‘Loadfg02b’ on file 1.
Processed 43032 pages for database ‘tp_v5_dev’, file ‘Loadfg03a’ on file 1.
Processed 43448 pages for database ‘tp_v5_dev’, file ‘Loadfg03b’ on file 1.
Processed 40976 pages for database ‘tp_v5_dev’, file ‘Loadfg04a’ on file 1.
Processed 41248 pages for database ‘tp_v5_dev’, file ‘Loadfg04b’ on file 1.
Processed 34376 pages for database ‘tp_v5_dev’, file ‘Loadfg05a’ on file 1.
Processed 47120 pages for database ‘tp_v5_dev’, file ‘Loadfg05b’ on file 1.
Processed 44816 pages for database ‘tp_v5_dev’, file ‘Loadfg06a’ on file 1.
Processed 45072 pages for database ‘tp_v5_dev’, file ‘Loadfg06b’ on file 1.
Processed 44056 pages for database ‘tp_v5_dev’, file ‘Loadfg07a’ on file 1.
Processed 44344 pages for database ‘tp_v5_dev’, file ‘Loadfg07b’ on file 1.
Processed 41976 pages for database ‘tp_v5_dev’, file ‘Loadfg08a’ on file 1.
Processed 48648 pages for database ‘tp_v5_dev’, file ‘Loadfg08b’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09a’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09b’ on file 1.
Processed 51208 pages for database ‘tp_v5_dev’, file ‘Loadfg10a’ on file 1.
Processed 55432 pages for database ‘tp_v5_dev’, file ‘Loadfg10b’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg11d’ on file 1.
Processed 46096 pages for database ‘tp_v5_dev’, file ‘Loadfg11a’ on file 1.
Processed 49672 pages for database ‘tp_v5_dev’, file ‘Loadfg11b’ on file 1.
Processed 46864 pages for database ‘tp_v5_dev’, file ‘Loadfg12a’ on file 1.
Processed 60424 pages for database ‘tp_v5_dev’, file ‘Loadfg12b’ on file 1.
Processed 41496 pages for database ‘tp_v5_dev’, file ‘Loadfg13a’ on file 1.
Processed 50808 pages for database ‘tp_v5_dev’, file ‘Loadfg13b’ on file 1.
Processed 35872 pages for database ‘tp_v5_dev’, file ‘Loadfg14a’ on file 1.
Processed 45192 pages for database ‘tp_v5_dev’, file ‘Loadfg14b’ on file 1.
Processed 45080 pages for database ‘tp_v5_dev’, file ‘Loadfg15a’ on file 1.
Processed 54352 pages for database ‘tp_v5_dev’, file ‘Loadfg15b’ on file 1.
Processed 39664 pages for database ‘tp_v5_dev’, file ‘Loadfg16a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg16b’ on file 1.
Processed 39624 pages for database ‘tp_v5_dev’, file ‘Loadfg17a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg17b’ on file 1.
Processed 41328 pages for database ‘tp_v5_dev’, file ‘Loadfg18a’ on file 1.
Processed 54784 pages for database ‘tp_v5_dev’, file ‘Loadfg18b’ on file 1.
Processed 116240 pages for database ‘tp_v5_dev’, file ‘Loadfg19a’ on file 1.
Processed 119688 pages for database ‘tp_v5_dev’, file ‘Loadfg19b’ on file 1.
Processed 131088 pages for database ‘tp_v5_dev’, file ‘Loadfg20a’ on file 1.
Processed 91656 pages for database ‘tp_v5_dev’, file ‘Loadfg20b’ on file 1.
Processed 71296 pages for database ‘tp_v5_dev’, file ‘Loadfg21a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg21b’ on file 1.
Processed 74768 pages for database ‘tp_v5_dev’, file ‘Loadfg22a’ on file 1.
Processed 96832 pages for database ‘tp_v5_dev’, file ‘Loadfg22b’ on file 1.
Processed 71224 pages for database ‘tp_v5_dev’, file ‘Loadfg23a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg23b’ on file 1.
Processed 76200 pages for database ‘tp_v5_dev’, file ‘Loadfg24a’ on file 1.
Processed 98312 pages for database ‘tp_v5_dev’, file ‘Loadfg24b’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘SimIndex01’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex02’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex04’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex05’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Sim42’ on file 1.
Processed 65472 pages for database ‘tp_v5_dev’, file ‘History11a1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11a2’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday03’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday04’ on file 1.
Processed 64744 pages for database ‘tp_v5_dev’, file ‘History11b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11b2’ on file 1.
Processed 73344 pages for database ‘tp_v5_dev’, file ‘History11c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History11d1’ on file 1.
Processed 34704 pages for database ‘tp_v5_dev’, file ‘History11d2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12a1’ on file 1.
Processed 144 pages for database ‘tp_v5_dev’, file ‘History12a2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12b2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12c1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12d1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12d2’ on file 1.
Processed 94912 pages for database ‘tp_v5_dev’, file ‘loadfg25a’ on file 1.
Processed 105168 pages for database ‘tp_v5_dev’, file ‘loadfg25b’ on file 1.
Processed 112320 pages for database ‘tp_v5_dev’, file ‘loadfg26a’ on file 1.
Processed 114832 pages for database ‘tp_v5_dev’, file ‘loadfg26b’ on file 1.
Processed 129792 pages for database ‘tp_v5_dev’, file ‘loadfg27a’ on file 1.
Processed 145840 pages for database ‘tp_v5_dev’, file ‘loadfg27b’ on file 1.
Processed 114000 pages for database ‘tp_v5_dev’, file ‘loadfg28a’ on file 1.
Processed 115704 pages for database ‘tp_v5_dev’, file ‘loadfg28b’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg29a’ on file 1.
Processed 116640 pages for database ‘tp_v5_dev’, file ‘loadfg29b’ on file 1.
Processed 127136 pages for database ‘tp_v5_dev’, file ‘loadfg30a’ on file 1.
Processed 137128 pages for database ‘tp_v5_dev’, file ‘loadfg30b’ on file 1.
Processed 114208 pages for database ‘tp_v5_dev’, file ‘loadfg31a’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg31b’ on file 1.
Processed 130200 pages for database ‘tp_v5_dev’, file ‘loadfg32a’ on file 1.
Processed 139536 pages for database ‘tp_v5_dev’, file ‘loadfg32b’ on file 1.
Processed 114648 pages for database ‘tp_v5_dev’, file ‘loadfg33a’ on file 1.
Processed 126072 pages for database ‘tp_v5_dev’, file ‘loadfg33b’ on file 1.
Processed 113184 pages for database ‘tp_v5_dev’, file ‘loadfg34a’ on file 1.
Processed 122184 pages for database ‘tp_v5_dev’, file ‘loadfg34b’ on file 1.
Processed 105432 pages for database ‘tp_v5_dev’, file ‘loadfg35a’ on file 1.
Processed 126624 pages for database ‘tp_v5_dev’, file ‘loadfg35b’ on file 1.
Processed 111752 pages for database ‘tp_v5_dev’, file ‘loadfg36a’ on file 1.
Processed 121128 pages for database ‘tp_v5_dev’, file ‘loadfg36b’ on file 1.
Processed 150920 pages for database ‘tp_v5_dev’, file ‘Loadfg37a’ on file 1.
Processed 64000 pages for database ‘tp_v5_dev’, file ‘Loadfg37b’ on file 1.
Processed 113976 pages for database ‘tp_v5_dev’, file ‘load38_01’ on file 1.
Processed 102400 pages for database ‘tp_v5_dev’, file ‘load38_02’ on file 1.
Processed 121368 pages for database ‘tp_v5_dev’, file ‘load39_01’ on file 1.
Processed 115200 pages for database ‘tp_v5_dev’, file ‘load39_02’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG15_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG16_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG17_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG18_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG19_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG20_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG21_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG22_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG23_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG24_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG25_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG26_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG27_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG28_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG29_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG30_PageFile01’ on file 1.
Processed 44448 pages for database ‘tp_v5_dev’, file ‘Interval_01’ on file 1.
Processed 60544 pages for database ‘tp_v5_dev’, file ‘Interval_fg01a’ on file 1.
Processed 65752 pages for database ‘tp_v5_dev’, file ‘Interval_fg01b’ on file 1.
Processed 71600 pages for database ‘tp_v5_dev’, file ‘Interval_fg01c’ on file 1.
Processed 32168 pages for database ‘tp_v5_dev’, file ‘Interval_02’ on file 1.
Processed 58416 pages for database ‘tp_v5_dev’, file ‘Interval_fg02a’ on file 1.
Processed 58336 pages for database ‘tp_v5_dev’, file ‘Interval_fg02b’ on file 1.
Processed 75624 pages for database ‘tp_v5_dev’, file ‘Interval_fg02c’ on file 1.
Processed 35632 pages for database ‘tp_v5_dev’, file ‘Interval_03’ on file 1.
Processed 64488 pages for database ‘tp_v5_dev’, file ‘Interval_fg03a’ on file 1.
Processed 73336 pages for database ‘tp_v5_dev’, file ‘Interval_fg03b’ on file 1.
Processed 73776 pages for database ‘tp_v5_dev’, file ‘Interval_fg03c’ on file 1.
Processed 11456 pages for database ‘tp_v5_dev’, file ‘Interval_04’ on file 1.
Processed 30584 pages for database ‘tp_v5_dev’, file ‘Interval_fg04a’ on file 1.
Processed 30392 pages for database ‘tp_v5_dev’, file ‘Interval_fg04b’ on file 1.
Processed 31688 pages for database ‘tp_v5_dev’, file ‘Interval_fg04c’ on file 1.
Processed 38992 pages for database ‘tp_v5_dev’, file ‘Interval_fg05a’ on file 1.
Processed 38896 pages for database ‘tp_v5_dev’, file ‘Interval_fg05b’ on file 1.
Processed 39304 pages for database ‘tp_v5_dev’, file ‘Interval_fg05c’ on file 1.
Processed 22016 pages for database ‘tp_v5_dev’, file ‘Interval_06’ on file 1.
Processed 38704 pages for database ‘tp_v5_dev’, file ‘Interval_fg06a’ on file 1.
Processed 35408 pages for database ‘tp_v5_dev’, file ‘Interval_fg06b’ on file 1.
Processed 34840 pages for database ‘tp_v5_dev’, file ‘Interval_fg06c’ on file 1.
Processed 45920 pages for database ‘tp_v5_dev’, file ‘Interval_fg07a’ on file 1.
Processed 47080 pages for database ‘tp_v5_dev’, file ‘Interval_fg07b’ on file 1.
Processed 52416 pages for database ‘tp_v5_dev’, file ‘Interval_fg07c’ on file 1.
Processed 55120 pages for database ‘tp_v5_dev’, file ‘Interval_fg08a’ on file 1.
Processed 60064 pages for database ‘tp_v5_dev’, file ‘Interval_fg08b’ on file 1.
Processed 61808 pages for database ‘tp_v5_dev’, file ‘Interval_fg08c’ on file 1.
Processed 32392 pages for database ‘tp_v5_dev’, file ‘Interval_09’ on file 1.
Processed 64872 pages for database ‘tp_v5_dev’, file ‘Interval_fg09a’ on file 1.
Processed 63080 pages for database ‘tp_v5_dev’, file ‘Interval_fg09b’ on file 1.
Processed 60840 pages for database ‘tp_v5_dev’, file ‘Interval_fg09c’ on file 1.
Processed 13992 pages for database ‘tp_v5_dev’, file ‘Interval_10’ on file 1.
Processed 16272 pages for database ‘tp_v5_dev’, file ‘Interval_fg10a’ on file 1.
Processed 13352 pages for database ‘tp_v5_dev’, file ‘Interval_fg10b’ on file 1.
Processed 27160 pages for database ‘tp_v5_dev’, file ‘Interval_fg10c’ on file 1.
Processed 14720 pages for database ‘tp_v5_dev’, file ‘Interval_11’ on file 1.
Processed 16680 pages for database ‘tp_v5_dev’, file ‘Interval_fg11a’ on file 1.
Processed 28184 pages for database ‘tp_v5_dev’, file ‘Interval_fg11b’ on file 1.
Processed 13784 pages for database ‘tp_v5_dev’, file ‘Interval_fg11c’ on file 1.
Processed 15744 pages for database ‘tp_v5_dev’, file ‘Interval_12’ on file 1.
Processed 15040 pages for database ‘tp_v5_dev’, file ‘Interval_fg12a’ on file 1.
Processed 13936 pages for database ‘tp_v5_dev’, file ‘Interval_fg12b’ on file 1.
Processed 29944 pages for database ‘tp_v5_dev’, file ‘Interval_fg12c’ on file 1.
Processed 13200 pages for database ‘tp_v5_dev’, file ‘Interval_13’ on file 1.
Processed 23584 pages for database ‘tp_v5_dev’, file ‘Interval_fg13a’ on file 1.
Processed 12904 pages for database ‘tp_v5_dev’, file ‘Interval_fg13b’ on file 1.
Processed 26776 pages for database ‘tp_v5_dev’, file ‘Interval_fg13c’ on file 1.
Processed 15296 pages for database ‘tp_v5_dev’, file ‘Interval_14’ on file 1.
Processed 17840 pages for database ‘tp_v5_dev’, file ‘Interval_fg14a’ on file 1.
Processed 12320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14b’ on file 1.
Processed 28320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14c’ on file 1.
Processed 18400 pages for database ‘tp_v5_dev’, file ‘Interval_fg15a’ on file 1.
Processed 28928 pages for database ‘tp_v5_dev’, file ‘Interval_fg15b’ on file 1.
Processed 30744 pages for database ‘tp_v5_dev’, file ‘Interval_fg15c’ on file 1.
Processed 30088 pages for database ‘tp_v5_dev’, file ‘Interval_fg16a’ on file 1.
Processed 16184 pages for database ‘tp_v5_dev’, file ‘Interval_fg16b’ on file 1.
Processed 36504 pages for database ‘tp_v5_dev’, file ‘Interval_fg16c’ on file 1.
Processed 18968 pages for database ‘tp_v5_dev’, file ‘Interval_17’ on file 1.
Processed 14592 pages for database ‘tp_v5_dev’, file ‘Interval_fg17a’ on file 1.
Processed 30032 pages for database ‘tp_v5_dev’, file ‘Interval_fg17b’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Interval_fg17c’ on file 1.
Processed 22392 pages for database ‘tp_v5_dev’, file ‘Interval_fg18a’ on file 1.
Processed 30136 pages for database ‘tp_v5_dev’, file ‘Interval_fg18b’ on file 1.
Processed 37224 pages for database ‘tp_v5_dev’, file ‘Interval_fg18c’ on file 1.
Processed 33616 pages for database ‘tp_v5_dev’, file ‘Interval_fg19a’ on file 1.
Processed 30024 pages for database ‘tp_v5_dev’, file ‘Interval_fg19b’ on file 1.
Processed 29864 pages for database ‘tp_v5_dev’, file ‘Interval_fg19c’ on file 1.
Processed 36248 pages for database ‘tp_v5_dev’, file ‘Interval_20a’ on file 1.
Processed 27616 pages for database ‘tp_v5_dev’, file ‘Interval_20b’ on file 1.
Processed 27376 pages for database ‘tp_v5_dev’, file ‘Interval_20c’ on file 1.
Processed 12632 pages for database ‘tp_v5_dev’, file ‘Interval_21’ on file 1.
Processed 13080 pages for database ‘tp_v5_dev’, file ‘Interval_fg21a’ on file 1.
Processed 24608 pages for database ‘tp_v5_dev’, file ‘Interval_fg21b’ on file 1.
Processed 24288 pages for database ‘tp_v5_dev’, file ‘Interval_fg21c’ on file 1.
Processed 736 pages for database ‘tp_v5_dev’, file ‘Interval_22b’ on file 1.
Processed 992 pages for database ‘tp_v5_dev’, file ‘Interval_fg22a’ on file 1.
Processed 1032 pages for database ‘tp_v5_dev’, file ‘Interval_fg22b’ on file 1.
Processed 1088 pages for database ‘tp_v5_dev’, file ‘Interval_fg22c’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg01_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg02_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg03_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg04_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg05_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg06_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg07_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg08_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg09_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg10_File01’ on file 1.
Processed 768 pages for database ‘tp_v5_dev’, file ‘Interval_fg23a’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23b’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23c’ on file 1.
Processed 838952 pages for database ‘tp_v5_dev’, file ‘Interval_fg24a’ on file 1.
Processed 732784 pages for database ‘tp_v5_dev’, file ‘Interval_fg24b’ on file 1.
Processed 804256 pages for database ‘tp_v5_dev’, file ‘Interval_fg24c’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25a’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25b’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25c’ on file 1.
Processed 219528 pages for database ‘tp_v5_dev’, file ‘Load40_01’ on file 1.
Processed 156968 pages for database ‘tp_v5_dev’, file ‘Load41_01’ on file 1.
Processed 169880 pages for database ‘tp_v5_dev’, file ‘Load42_01’ on file 1.
Processed 860640 pages for database ‘tp_v5_dev’, file ‘Load43_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load44_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load45_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load46_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load47_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load48_01’ on file 1.
100 percent processed.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2_log’ on file 1.
Processed 2 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog2’ on file 1.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog3’ on file 1.
BACKUP DATABASE successfully processed 23884890 pages in 58.395 seconds (3195.491 MB/sec).

RESUTS (Backup TO NUL – forgot to include the query in the output)

10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Processed 25288 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG01_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG02_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG03_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG04_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG05_PageFile01’ on file 1.
Processed 17584 pages for database ‘tp_v5_dev’, file ‘History09a’ on file 1.
Processed 1680 pages for database ‘tp_v5_dev’, file ‘History09b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History01_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History01_02’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History02a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History02b’ on file 1.
Processed 24 pages for database ‘tp_v5_dev’, file ‘History03a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History03b’ on file 1.
Processed 2736 pages for database ‘tp_v5_dev’, file ‘History04a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History04b’ on file 1.
Processed 3400 pages for database ‘tp_v5_dev’, file ‘History05a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History05b’ on file 1.
Processed 5032 pages for database ‘tp_v5_dev’, file ‘History06a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History06b’ on file 1.
Processed 6936 pages for database ‘tp_v5_dev’, file ‘History07a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History07b’ on file 1.
Processed 10904 pages for database ‘tp_v5_dev’, file ‘History08a’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History08b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG06_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG07_PageFile01’ on file 1.
Processed 1814280 pages for database ‘tp_v5_dev’, file ‘HistoryData01’ on file 1.
Processed 1674784 pages for database ‘tp_v5_dev’, file ‘HistoryData03’ on file 1.
Processed 1657248 pages for database ‘tp_v5_dev’, file ‘HistoryData05’ on file 1.
Processed 1182680 pages for database ‘tp_v5_dev’, file ‘LoadData02’ on file 1.
Processed 1150464 pages for database ‘tp_v5_dev’, file ‘LoadData04’ on file 1.
Processed 1385080 pages for database ‘tp_v5_dev’, file ‘LoadData01’ on file 1.
Processed 1230520 pages for database ‘tp_v5_dev’, file ‘LoadData03’ on file 1.
Processed 357776 pages for database ‘tp_v5_dev’, file ‘MiscData2’ on file 1.
Processed 324864 pages for database ‘tp_v5_dev’, file ‘MiscData1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG08_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG09_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG10_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG11_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG12_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG13_PageFile01’ on file 1.
Processed 5112 pages for database ‘tp_v5_dev’, file ‘History10_01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History10_02’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00a’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg00b’ on file 1.
Processed 32608 pages for database ‘tp_v5_dev’, file ‘Loadfg01a’ on file 1.
Processed 42000 pages for database ‘tp_v5_dev’, file ‘Loadfg01b’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG14_PageFile01’ on file 1.
Processed 5168 pages for database ‘tp_v5_dev’, file ‘History09b1’ on file 1.
Processed 464 pages for database ‘tp_v5_dev’, file ‘History09b2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09c1’ on file 1.
Processed 5688 pages for database ‘tp_v5_dev’, file ‘History09c2’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘History09d1’ on file 1.
Processed 5760 pages for database ‘tp_v5_dev’, file ‘History09d2’ on file 1.
Processed 6488 pages for database ‘tp_v5_dev’, file ‘History10a1’ on file 1.
Processed 432 pages for database ‘tp_v5_dev’, file ‘History10a2’ on file 1.
Processed 8784 pages for database ‘tp_v5_dev’, file ‘History10b1’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History10b2’ on file 1.
Processed 20240 pages for database ‘tp_v5_dev’, file ‘History10c2’ on file 1.
Processed 55416 pages for database ‘tp_v5_dev’, file ‘History10d2’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘Archive02’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘Archive03’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Loadfg02a’ on file 1.
Processed 41488 pages for database ‘tp_v5_dev’, file ‘Loadfg02b’ on file 1.
Processed 43032 pages for database ‘tp_v5_dev’, file ‘Loadfg03a’ on file 1.
Processed 43448 pages for database ‘tp_v5_dev’, file ‘Loadfg03b’ on file 1.
Processed 40976 pages for database ‘tp_v5_dev’, file ‘Loadfg04a’ on file 1.
Processed 41248 pages for database ‘tp_v5_dev’, file ‘Loadfg04b’ on file 1.
Processed 34376 pages for database ‘tp_v5_dev’, file ‘Loadfg05a’ on file 1.
Processed 47120 pages for database ‘tp_v5_dev’, file ‘Loadfg05b’ on file 1.
Processed 44816 pages for database ‘tp_v5_dev’, file ‘Loadfg06a’ on file 1.
Processed 45072 pages for database ‘tp_v5_dev’, file ‘Loadfg06b’ on file 1.
Processed 44056 pages for database ‘tp_v5_dev’, file ‘Loadfg07a’ on file 1.
Processed 44344 pages for database ‘tp_v5_dev’, file ‘Loadfg07b’ on file 1.
Processed 41976 pages for database ‘tp_v5_dev’, file ‘Loadfg08a’ on file 1.
Processed 48648 pages for database ‘tp_v5_dev’, file ‘Loadfg08b’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09a’ on file 1.
Processed 50696 pages for database ‘tp_v5_dev’, file ‘Loadfg09b’ on file 1.
Processed 51208 pages for database ‘tp_v5_dev’, file ‘Loadfg10a’ on file 1.
Processed 55432 pages for database ‘tp_v5_dev’, file ‘Loadfg10b’ on file 1.
Processed 56 pages for database ‘tp_v5_dev’, file ‘Loadfg11d’ on file 1.
Processed 46096 pages for database ‘tp_v5_dev’, file ‘Loadfg11a’ on file 1.
Processed 49672 pages for database ‘tp_v5_dev’, file ‘Loadfg11b’ on file 1.
Processed 46864 pages for database ‘tp_v5_dev’, file ‘Loadfg12a’ on file 1.
Processed 60424 pages for database ‘tp_v5_dev’, file ‘Loadfg12b’ on file 1.
Processed 41496 pages for database ‘tp_v5_dev’, file ‘Loadfg13a’ on file 1.
Processed 50808 pages for database ‘tp_v5_dev’, file ‘Loadfg13b’ on file 1.
Processed 35872 pages for database ‘tp_v5_dev’, file ‘Loadfg14a’ on file 1.
Processed 45192 pages for database ‘tp_v5_dev’, file ‘Loadfg14b’ on file 1.
Processed 45080 pages for database ‘tp_v5_dev’, file ‘Loadfg15a’ on file 1.
Processed 54352 pages for database ‘tp_v5_dev’, file ‘Loadfg15b’ on file 1.
Processed 39664 pages for database ‘tp_v5_dev’, file ‘Loadfg16a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg16b’ on file 1.
Processed 39624 pages for database ‘tp_v5_dev’, file ‘Loadfg17a’ on file 1.
Processed 53256 pages for database ‘tp_v5_dev’, file ‘Loadfg17b’ on file 1.
Processed 41328 pages for database ‘tp_v5_dev’, file ‘Loadfg18a’ on file 1.
Processed 54784 pages for database ‘tp_v5_dev’, file ‘Loadfg18b’ on file 1.
Processed 116240 pages for database ‘tp_v5_dev’, file ‘Loadfg19a’ on file 1.
Processed 119688 pages for database ‘tp_v5_dev’, file ‘Loadfg19b’ on file 1.
Processed 131088 pages for database ‘tp_v5_dev’, file ‘Loadfg20a’ on file 1.
Processed 91656 pages for database ‘tp_v5_dev’, file ‘Loadfg20b’ on file 1.
Processed 71296 pages for database ‘tp_v5_dev’, file ‘Loadfg21a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg21b’ on file 1.
Processed 74768 pages for database ‘tp_v5_dev’, file ‘Loadfg22a’ on file 1.
Processed 96832 pages for database ‘tp_v5_dev’, file ‘Loadfg22b’ on file 1.
Processed 71224 pages for database ‘tp_v5_dev’, file ‘Loadfg23a’ on file 1.
Processed 93704 pages for database ‘tp_v5_dev’, file ‘Loadfg23b’ on file 1.
Processed 76200 pages for database ‘tp_v5_dev’, file ‘Loadfg24a’ on file 1.
Processed 98312 pages for database ‘tp_v5_dev’, file ‘Loadfg24b’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘SimIndex01’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex02’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex04’ on file 1.
Processed 48 pages for database ‘tp_v5_dev’, file ‘SimIndex05’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Sim42’ on file 1.
Processed 65472 pages for database ‘tp_v5_dev’, file ‘History11a1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11a2’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday03’ on file 1.
Processed 64 pages for database ‘tp_v5_dev’, file ‘Intraday04’ on file 1.
Processed 64744 pages for database ‘tp_v5_dev’, file ‘History11b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History11b2’ on file 1.
Processed 73344 pages for database ‘tp_v5_dev’, file ‘History11c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History11d1’ on file 1.
Processed 34704 pages for database ‘tp_v5_dev’, file ‘History11d2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12a1’ on file 1.
Processed 144 pages for database ‘tp_v5_dev’, file ‘History12a2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12b1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12b2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12c1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12c2’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘History12d1’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘History12d2’ on file 1.
Processed 94912 pages for database ‘tp_v5_dev’, file ‘loadfg25a’ on file 1.
Processed 105168 pages for database ‘tp_v5_dev’, file ‘loadfg25b’ on file 1.
Processed 112320 pages for database ‘tp_v5_dev’, file ‘loadfg26a’ on file 1.
Processed 114832 pages for database ‘tp_v5_dev’, file ‘loadfg26b’ on file 1.
Processed 129792 pages for database ‘tp_v5_dev’, file ‘loadfg27a’ on file 1.
Processed 145840 pages for database ‘tp_v5_dev’, file ‘loadfg27b’ on file 1.
Processed 114000 pages for database ‘tp_v5_dev’, file ‘loadfg28a’ on file 1.
Processed 115704 pages for database ‘tp_v5_dev’, file ‘loadfg28b’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg29a’ on file 1.
Processed 116640 pages for database ‘tp_v5_dev’, file ‘loadfg29b’ on file 1.
Processed 127136 pages for database ‘tp_v5_dev’, file ‘loadfg30a’ on file 1.
Processed 137128 pages for database ‘tp_v5_dev’, file ‘loadfg30b’ on file 1.
Processed 114208 pages for database ‘tp_v5_dev’, file ‘loadfg31a’ on file 1.
Processed 114888 pages for database ‘tp_v5_dev’, file ‘loadfg31b’ on file 1.
Processed 130200 pages for database ‘tp_v5_dev’, file ‘loadfg32a’ on file 1.
Processed 139536 pages for database ‘tp_v5_dev’, file ‘loadfg32b’ on file 1.
Processed 114648 pages for database ‘tp_v5_dev’, file ‘loadfg33a’ on file 1.
Processed 126072 pages for database ‘tp_v5_dev’, file ‘loadfg33b’ on file 1.
Processed 113184 pages for database ‘tp_v5_dev’, file ‘loadfg34a’ on file 1.
Processed 122184 pages for database ‘tp_v5_dev’, file ‘loadfg34b’ on file 1.
Processed 105432 pages for database ‘tp_v5_dev’, file ‘loadfg35a’ on file 1.
Processed 126624 pages for database ‘tp_v5_dev’, file ‘loadfg35b’ on file 1.
Processed 111752 pages for database ‘tp_v5_dev’, file ‘loadfg36a’ on file 1.
Processed 121128 pages for database ‘tp_v5_dev’, file ‘loadfg36b’ on file 1.
Processed 150920 pages for database ‘tp_v5_dev’, file ‘Loadfg37a’ on file 1.
Processed 64000 pages for database ‘tp_v5_dev’, file ‘Loadfg37b’ on file 1.
Processed 113976 pages for database ‘tp_v5_dev’, file ‘load38_01’ on file 1.
Processed 102400 pages for database ‘tp_v5_dev’, file ‘load38_02’ on file 1.
Processed 121368 pages for database ‘tp_v5_dev’, file ‘load39_01’ on file 1.
Processed 115200 pages for database ‘tp_v5_dev’, file ‘load39_02’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG15_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG16_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG17_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG18_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG19_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG20_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG21_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG22_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG23_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG24_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG25_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG26_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG27_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG28_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG29_PageFile01’ on file 1.
Processed 32 pages for database ‘tp_v5_dev’, file ‘PageField_FG30_PageFile01’ on file 1.
Processed 44448 pages for database ‘tp_v5_dev’, file ‘Interval_01’ on file 1.
Processed 60544 pages for database ‘tp_v5_dev’, file ‘Interval_fg01a’ on file 1.
Processed 65752 pages for database ‘tp_v5_dev’, file ‘Interval_fg01b’ on file 1.
Processed 71600 pages for database ‘tp_v5_dev’, file ‘Interval_fg01c’ on file 1.
Processed 32168 pages for database ‘tp_v5_dev’, file ‘Interval_02’ on file 1.
Processed 58416 pages for database ‘tp_v5_dev’, file ‘Interval_fg02a’ on file 1.
Processed 58336 pages for database ‘tp_v5_dev’, file ‘Interval_fg02b’ on file 1.
Processed 75624 pages for database ‘tp_v5_dev’, file ‘Interval_fg02c’ on file 1.
Processed 35632 pages for database ‘tp_v5_dev’, file ‘Interval_03’ on file 1.
Processed 64488 pages for database ‘tp_v5_dev’, file ‘Interval_fg03a’ on file 1.
Processed 73336 pages for database ‘tp_v5_dev’, file ‘Interval_fg03b’ on file 1.
Processed 73776 pages for database ‘tp_v5_dev’, file ‘Interval_fg03c’ on file 1.
Processed 11456 pages for database ‘tp_v5_dev’, file ‘Interval_04’ on file 1.
Processed 30584 pages for database ‘tp_v5_dev’, file ‘Interval_fg04a’ on file 1.
Processed 30392 pages for database ‘tp_v5_dev’, file ‘Interval_fg04b’ on file 1.
Processed 31688 pages for database ‘tp_v5_dev’, file ‘Interval_fg04c’ on file 1.
Processed 38992 pages for database ‘tp_v5_dev’, file ‘Interval_fg05a’ on file 1.
Processed 38896 pages for database ‘tp_v5_dev’, file ‘Interval_fg05b’ on file 1.
Processed 39304 pages for database ‘tp_v5_dev’, file ‘Interval_fg05c’ on file 1.
Processed 22016 pages for database ‘tp_v5_dev’, file ‘Interval_06’ on file 1.
Processed 38704 pages for database ‘tp_v5_dev’, file ‘Interval_fg06a’ on file 1.
Processed 35408 pages for database ‘tp_v5_dev’, file ‘Interval_fg06b’ on file 1.
Processed 34840 pages for database ‘tp_v5_dev’, file ‘Interval_fg06c’ on file 1.
Processed 45920 pages for database ‘tp_v5_dev’, file ‘Interval_fg07a’ on file 1.
Processed 47080 pages for database ‘tp_v5_dev’, file ‘Interval_fg07b’ on file 1.
Processed 52416 pages for database ‘tp_v5_dev’, file ‘Interval_fg07c’ on file 1.
Processed 55120 pages for database ‘tp_v5_dev’, file ‘Interval_fg08a’ on file 1.
Processed 60064 pages for database ‘tp_v5_dev’, file ‘Interval_fg08b’ on file 1.
Processed 61808 pages for database ‘tp_v5_dev’, file ‘Interval_fg08c’ on file 1.
Processed 32392 pages for database ‘tp_v5_dev’, file ‘Interval_09’ on file 1.
Processed 64872 pages for database ‘tp_v5_dev’, file ‘Interval_fg09a’ on file 1.
Processed 63080 pages for database ‘tp_v5_dev’, file ‘Interval_fg09b’ on file 1.
Processed 60840 pages for database ‘tp_v5_dev’, file ‘Interval_fg09c’ on file 1.
Processed 13992 pages for database ‘tp_v5_dev’, file ‘Interval_10’ on file 1.
Processed 16272 pages for database ‘tp_v5_dev’, file ‘Interval_fg10a’ on file 1.
Processed 13352 pages for database ‘tp_v5_dev’, file ‘Interval_fg10b’ on file 1.
Processed 27160 pages for database ‘tp_v5_dev’, file ‘Interval_fg10c’ on file 1.
Processed 14720 pages for database ‘tp_v5_dev’, file ‘Interval_11’ on file 1.
Processed 16680 pages for database ‘tp_v5_dev’, file ‘Interval_fg11a’ on file 1.
Processed 28184 pages for database ‘tp_v5_dev’, file ‘Interval_fg11b’ on file 1.
Processed 13784 pages for database ‘tp_v5_dev’, file ‘Interval_fg11c’ on file 1.
Processed 15744 pages for database ‘tp_v5_dev’, file ‘Interval_12’ on file 1.
Processed 15040 pages for database ‘tp_v5_dev’, file ‘Interval_fg12a’ on file 1.
Processed 13936 pages for database ‘tp_v5_dev’, file ‘Interval_fg12b’ on file 1.
Processed 29944 pages for database ‘tp_v5_dev’, file ‘Interval_fg12c’ on file 1.
Processed 13200 pages for database ‘tp_v5_dev’, file ‘Interval_13’ on file 1.
Processed 23584 pages for database ‘tp_v5_dev’, file ‘Interval_fg13a’ on file 1.
Processed 12904 pages for database ‘tp_v5_dev’, file ‘Interval_fg13b’ on file 1.
Processed 26776 pages for database ‘tp_v5_dev’, file ‘Interval_fg13c’ on file 1.
Processed 15296 pages for database ‘tp_v5_dev’, file ‘Interval_14’ on file 1.
Processed 17840 pages for database ‘tp_v5_dev’, file ‘Interval_fg14a’ on file 1.
Processed 12320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14b’ on file 1.
Processed 28320 pages for database ‘tp_v5_dev’, file ‘Interval_fg14c’ on file 1.
Processed 18400 pages for database ‘tp_v5_dev’, file ‘Interval_fg15a’ on file 1.
Processed 28928 pages for database ‘tp_v5_dev’, file ‘Interval_fg15b’ on file 1.
Processed 30744 pages for database ‘tp_v5_dev’, file ‘Interval_fg15c’ on file 1.
Processed 30088 pages for database ‘tp_v5_dev’, file ‘Interval_fg16a’ on file 1.
Processed 16184 pages for database ‘tp_v5_dev’, file ‘Interval_fg16b’ on file 1.
Processed 36504 pages for database ‘tp_v5_dev’, file ‘Interval_fg16c’ on file 1.
Processed 18968 pages for database ‘tp_v5_dev’, file ‘Interval_17’ on file 1.
Processed 14592 pages for database ‘tp_v5_dev’, file ‘Interval_fg17a’ on file 1.
Processed 30032 pages for database ‘tp_v5_dev’, file ‘Interval_fg17b’ on file 1.
Processed 31888 pages for database ‘tp_v5_dev’, file ‘Interval_fg17c’ on file 1.
Processed 22392 pages for database ‘tp_v5_dev’, file ‘Interval_fg18a’ on file 1.
Processed 30136 pages for database ‘tp_v5_dev’, file ‘Interval_fg18b’ on file 1.
Processed 37224 pages for database ‘tp_v5_dev’, file ‘Interval_fg18c’ on file 1.
Processed 33616 pages for database ‘tp_v5_dev’, file ‘Interval_fg19a’ on file 1.
Processed 30024 pages for database ‘tp_v5_dev’, file ‘Interval_fg19b’ on file 1.
Processed 29864 pages for database ‘tp_v5_dev’, file ‘Interval_fg19c’ on file 1.
Processed 36248 pages for database ‘tp_v5_dev’, file ‘Interval_20a’ on file 1.
Processed 27616 pages for database ‘tp_v5_dev’, file ‘Interval_20b’ on file 1.
Processed 27376 pages for database ‘tp_v5_dev’, file ‘Interval_20c’ on file 1.
Processed 12632 pages for database ‘tp_v5_dev’, file ‘Interval_21’ on file 1.
Processed 13080 pages for database ‘tp_v5_dev’, file ‘Interval_fg21a’ on file 1.
Processed 24608 pages for database ‘tp_v5_dev’, file ‘Interval_fg21b’ on file 1.
Processed 24288 pages for database ‘tp_v5_dev’, file ‘Interval_fg21c’ on file 1.
Processed 736 pages for database ‘tp_v5_dev’, file ‘Interval_22b’ on file 1.
Processed 992 pages for database ‘tp_v5_dev’, file ‘Interval_fg22a’ on file 1.
Processed 1032 pages for database ‘tp_v5_dev’, file ‘Interval_fg22b’ on file 1.
Processed 1088 pages for database ‘tp_v5_dev’, file ‘Interval_fg22c’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg01_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg02_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg03_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg04_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg05_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg06_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg07_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg08_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg09_File01’ on file 1.
Processed 40 pages for database ‘tp_v5_dev’, file ‘MatchType_Fg10_File01’ on file 1.
Processed 768 pages for database ‘tp_v5_dev’, file ‘Interval_fg23a’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23b’ on file 1.
Processed 784 pages for database ‘tp_v5_dev’, file ‘Interval_fg23c’ on file 1.
Processed 838952 pages for database ‘tp_v5_dev’, file ‘Interval_fg24a’ on file 1.
Processed 732784 pages for database ‘tp_v5_dev’, file ‘Interval_fg24b’ on file 1.
Processed 804256 pages for database ‘tp_v5_dev’, file ‘Interval_fg24c’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25a’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25b’ on file 1.
Processed 520 pages for database ‘tp_v5_dev’, file ‘Interval_fg25c’ on file 1.
Processed 219528 pages for database ‘tp_v5_dev’, file ‘Load40_01’ on file 1.
Processed 156968 pages for database ‘tp_v5_dev’, file ‘Load41_01’ on file 1.
Processed 169880 pages for database ‘tp_v5_dev’, file ‘Load42_01’ on file 1.
Processed 860640 pages for database ‘tp_v5_dev’, file ‘Load43_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load44_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load45_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load46_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load47_01’ on file 1.
Processed 16 pages for database ‘tp_v5_dev’, file ‘Load48_01’ on file 1.
100 percent processed.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizer_v2_log’ on file 1.
Processed 2 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog2’ on file 1.
Processed 0 pages for database ‘tp_v5_dev’, file ‘TradingOptimizerLog3’ on file 1.
BACKUP DATABASE successfully processed 23884890 pages in 35.689 seconds (5228.521 MB/sec).

Note: this was originally posted on http://blogs.msdn.com/b/microsoftbob/archive/2012/10/31/now-at-5-11-gb-s-sql-backup-to-null-3-12-gb-s-local-backup-with-i-o-accelerators.aspx

Posted in Fusion-io, SQL Server | Tagged | 1 Comment

More clarifications on 3.05 GB/s SQL backup potential for much higher throughput

Posted on October 29, 2012 by Bob L

A couple of clarifications – including potential for much greater backup throughput beyond 3 GB/s up to 9 GB/s for this hardware:

1) Contrary to the video, 10 GbE is not the fastest practical Ethernet for server-to-server communications. 40 GbE network cards and switches are available and affordable. It is feasible to achieve 5GB/s using a PCIE Gen 2 40 GbE card as well as via a 4 port 10 GbE adapter configured suitably. Mellanox produces a Gen 2 PCIE card supporting 40 Gb/s Ethernet and 32 Gb/s (actual) QDR InfiniBand as well as a Gen 3 version with FDR InfiniBand throughput of 56 Gb/s (54.54 Gb/s actual) providing close to 7 GB/s bandwidth. See http://www.mellanox.com/content/pages.php?pg=infiniband_cards_overview&menu_section=41. 

However, Just three x8 Duo2s which can be hosted in many servers as small as 2U generates up to 9 GB/s throughput saturating 56 Gb/s InfiniBand, the fastest network interface card having practical availability. PCIE SSD adoption means the network is now the bottleneck rather than storage I/O in the area of server-to-server data transfer.

2) Although backup compression is not used in the testing due to CPU limitations, database row/page compression is used achieving about 40% space reduction. This makes “real-world” effective backup throughput closer to 5 GB/s. Extrapolating that metric pushes logical throughput into the 15 GB/s range for the tested configuration if the current bottleneck (next item) is resolved.

3) CPUs are averaging under 50% utilization in my testing so that does not seem to be the bottleneck. I suspect a QPI (Quick Path Interconnect) configuration issue. See http://www.qdpma.com/systemarchitecture/systemarchitecture_qpi.html. The aggregate total bandwidth in a 2-way Nehalem architecture is 25.6 GB/s accommodated through 4 x 6.4 GB/s QPI links. The QPI links comprise:

a. One between the two I/O hubs (IOH) (each of which connects directly to half of the PCIE cards)

b. One each (total of two) between each IOH and a processor socket (i.e. NUMA node),

c. One between the sockets themselves.

As I understand, If data transfer is monopolizing the IOH-to-IOH or CPU-to-CPU links rather than affinitized between each processor and the processor’s directly-connected IOH this limits throughput to the individual QPI speed of 6.4 GB/s. If PCIE/NUMA configuration causing QPI link saturation is the bottleneck, then resolving should enable a SQL backup of a database stored on 6 Duos (1.5 GB/s read rate) to achieve 9 GB/s distributed among collectively-adequate destination targets using a pair of 40 GbE network cards. Using the SQL Backup to NULL operation can help verify. I realize there are other possible culprits – i.e. inefficient cache use, SQL Server specific NUMA configuration – Open to suggestions. The article http://www.micron.com/~/media/Documents/Products/White%20Paper/pcie_ssd_performance_hi.pdf provides recommendations for optimizing PCIE configuration for throughput.

Note: Due to an unexpected health crisis in our family, I need to re-prioritize and will be slow for next several days reviewing responses to the blog and associated video.

Thank you.

Posted in Uncategorized | Leave a comment

A couple of corrections on video

Posted on October 29, 2012 by Bob L
  1. I should have said that 40 Gbe and 100 Gbe are not widely implemented rather than not available  – they are available. But, even 100 GbE is only adequate for 12 GBPS – and with Gen 3 PCIE SSD reading at 3.0 GBps +, that will easily be overrun by newer servers that can utilize 5 or more of those cards. Ultimately the solution to the network bottleneck issue probably involves utilizing enough parallel multiple network interface cards/links together to match the PCIE speeds or extending PCIE as a network transfer itself. See http://www.networkworld.com/news/tech/2012/030112-pci-express-256848.html
  2. The effective transfer rate is actually better than the 4GBps proposed when factoring in the effectiveness of database page/row compression. As pointed out in the blog entry, my sample database is storing closer to 1/2 TB of logical data when considering the compression ratios achieved. SQL Backup reads compressed data natively and backs it up as is without decompressing, thus increasing effective read throughput by the effectiveness of the database compression with no adverse impact on the backup performance. It is important to understand the difference between backup compression and database compression – backup compression does occur while the database is being backed up and reduces the amount of storage needed for the target destination at the cost of CPU – however data in a database already compressed using page/row database compression is simply backed up natively.
  3. The title should probably end with “using HP IO Accelerators” rather than Fusion-IO cards since I am using the HP-branded cards, but my feeling is that those new to the technology may not realize that the HP cards are actually just OEM versions of Fusion-IO cards.

There are probably a few other misstatements, feel free to let me know any others.

Thanks.

Posted in Fusion-io, SQL Server | Leave a comment

A couple of corrections on video

Posted on October 29, 2012 by Bob L
  1. I should have said that 40 Gbe and 100 Gbe are not widely implemented rather than not available  – they are available. But, even 100 GbE is only adequate for 12 GBPS – and with Gen 3 PCIE SSD reading at 3.0 GBps +, that will easily be overrun by newer servers that can utilize 5 or more of those cards. Ultimately the solution to the network bottleneck issue probably involves utilizing enough parallel multiple network interface cards/links together to match the PCIE speeds or extending PCIE as a network transfer itself. See http://www.networkworld.com/news/tech/2012/030112-pci-express-256848.html
  2. The effective transfer rate is actually better than the 4GBps proposed when factoring in the effectiveness of database page/row compression. As pointed out in the blog entry, my sample database is storing closer to 1/2 TB of logical data when considering the compression ratios achieved. SQL Backup reads compressed data natively and backs it up as is without decompressing, thus increasing effective read throughput by the effectiveness of the database compression with no adverse impact on the backup performance. It is important to understand the difference between backup compression and database compression – backup compression does occur while the database is being backed up and reduces the amount of storage needed for the target destination at the cost of CPU – however data in a database already compressed using page/row database compression is simply backed up natively.
  3. The title should probably end with “using HP IO Accelerators” rather than Fusion-IO cards since I am using the HP-branded cards, but my feeling is that those new to the technology may not realize that the HP cards are actually just OEM versions of Fusion-IO cards.

There are probably a few other misstatements, feel free to let me know any others.

Thanks.

Posted in Uncategorized | Leave a comment