text:
Intel has released an interesting micro-ATX motherboard that has magnitude of nice features and retails for under $100. The Intel DZ75ML-45K motherboard uses the Intel Z75 Express chipset and the board highlights are; DDR3 2400MHz+ OC memory support (four slots, 32 GB max capacity), one PCI Express 3.0 x16 slot, one PCI Express 2.0 x 16 connector (x4 Electrical), Two PCI Express 2.0 x 1 slots, 8-channel audio (5.1+2), four USB 3.0 ports, 10 USB 2.0 ports, two SATA 6.0 Gbps connectors and four SATA 3.0 Gbps ports. It also features flexible overclocking and Lucid MVP software. The Lucid MVP GPU Virtualization feature enables use of Intel QuickSync whether your monitor cable is connected to a discrete graphics card or you are using Intel HD graphics built in to the CPU. Not bad features for an Intel board at a reasonable price point.
The latest in a series of Intel Desktop Boards designed for overclocking K-series 2nd and 3rd gen Intel Core processors, the Intel DZ75ML-45K delivers flexible overclocking and Lucid Virtu MVP at an affordable price. Additionally, Intel Desktop Boards has extended a Lucid MVP upgrade to existing Intel 7-series performance boards currently using Lucid Virtu Universal.
Comments are closed.


text:
Now this would have to be something implemented by the teams of course. I am not sure how many of you have checked out the MLB GameDay this year, but it is a new version and it charts Speed, break of the pitch and shows the delivery of the ball (when it is being used. it was not on for todays Reds game). If teams were to set up the equiptment in the minor league parks (I imagine it takes about 5 cameras from different view points, a radar gun and a computer that is connected to the cameras with a program that can take the data and put together the information). How much would it help scouting pitchers if you could look at the break on his pitches on a computer model? You could compare each curveball with the rest he has thrown. You could tell when the inconsistancies came, then go back and look at the video and maybe pick up the mechanical flaw that caused it. If its a consistant problem, you could then work with the pitcher to attempt to fix it.
Maybe I am thinking to much on this, but I think a system like this would do wonders for both the coaches and the players if it were used in the right way. Anyways, I just wanted to put that out there.

subset: commoncrawl


text:
Boat Tests
- Hampton
- Hampton Endurance 720
- 2014
- Cruiser
- 72'0"
- 18'8"
- 5'2"
- 122,500 lb. (dry)
- 2,031 gal.
- 450 gal.
Layout Diagram
Noteworthy Options: Intellian HD6 w/Dummy Dome ($12,980)
400-600 GPD watermaker ($9,000/$11,000)
12-foot tender with 40-hp outboard ($20,000)
or 14-foot tender with 60-hp outboard ($29,500)
CONDITIONS DURING BOAT TESTAir temperature: 83°F; humidity: 85%; seas: 3-4'
LOAD DURING BOAT TEST800 gal. fuel, 112 gal. water, 7 persons.
2/1,150-hp Caterpillar C18 ACERT diesels
Hung Shen 40 x 39 five-blade
The Numbers
|Hampton Endurance 720 - Final Boat Test Numbers:
|Speeds are two-way averages measured with Garmin GPS. GPH estimates taken via Caterpillar display. Range is based on 90% of advertised fuel capacity. Sound levels measured at the helm. 65 dB(A) is the level of normal conversation.
Noteworthy Options: Intellian HD6 w/Dummy Dome ($12,980)
400-600 GPD watermaker ($9,000/$11,000)
12-foot tender with 40-hp outboard ($20,000)
or 14-foot tender with 60-hp outboard ($29,500)
In For The Long Haul
Hampton Yachts offers a salty combination of comfort, elegance, and blue water capability in the Endurance 720 Long Range Cruiser.
Any boatbuilder worth his salt knows that success lies in the fundamentals of design and construction. Falter there and no amount of backfilling will save the day. But dial in all the critical points and a promising foundation can be laid. Hampton Yachts nails the fundamentals with this addition to its proven Endurance Series, the 720 EN.
To gain an appreciation for this big-shouldered cruiser, you need to go way back to the beginning, to the time when the tooling sat empty in a construction bay, fastidiously cleaned and polished, ready for that first layer of gelcoat. Then, you need to follow the building process, hallmarked as it is by a precise and intense attention to detail, start to finish. You need to understand the sumptuousness of the accommodations that are being carefully fitted into the interior, the array of redundant systems that are being installed in the engine room, and the seakindliness that's been designed into the hullform, with a running surface that will take you virtually anywhere you want to go.
A partnership launched the Endurance Series. Visionary boatbuilder Jeff Chen, the scion of a Far Eastern marine-industry family, joined forces with Capt. Forest Roberts, a long-time veteran of the marine industry and the guiding force behind Ft. Lauderdale's Anchor Yacht Sales.
There was a third person as well. Seeing the need for a yacht that would be highly efficient over a broad range of speeds while at the same time offering standout comfort and safety, Chen brought aboard renowned marine architect Howard Apollonio.
Apollonio had been evolving purpose-driven hull forms for decades, applying his ideas to everything from trawlers to superyachts. He added an immense knowledge base to the project, along with some serious expertise in hydrodynamics as well as tank testing.
What resulted was the split-chine, semidisplacement Hampton Hybrid Hull, with its ability to produce superior operating efficiencies right alongside outstanding seakindliness. A unique set of upper and lower chines accomplished this synergy, nicely combining the advantages of a planing hullform with those of a displacement hullform, and providing excellent stability.
I sea-trialed the 720 in the open Atlantic, straight offshore from Ft. Lauderdale, on a day that was rather rough and ready. But then again, the steady 20 knots of wind that was blowing, driving before it legions of 3- to 4-foot cresting waves of short duration, with an occasional "big boy" thrown in for good measure, generated a mixture of conditions that were perfect for evaluating the open-water performance of a fair-sized yacht.
The boat handled like a champ. My six fellow passengers (three of whom were prospective owners) and I noted little if any of the usual 'bucking' motion that often prevails when busting headseas, a total lack of slamming in the errant big boys, no squatting aft in following seas, and no significant roll while abeam and running, whether the seas were on the port or starboard sides. Facilitating all this, of course, were our Wesmar Three-Term Stabilizer fins and a pair of Caterpillar 1,150-horsepower C18 ACERT diesels, which generated an average fast cruise of 18 knots at 2000 rpm and a respectable 14.7 knots at 1750 rpm. With Roberts at the wheel, I was able to stroll about while underway, examining every corner of the yacht, from the skylounge to the main deck, to the accommodations area below, including the crew's quarters aft.
Sound levels were generally low. Working closely with the sound-and-vibration-attenuation experts at Soundown, Hampton's technicians had installed thick layers of noise-deadening materials beneath the floors and in the bulkheads, especially the ones on either side of the engine room. Moreover, sound-deadening tiles had been layered over the prop tunnels, thus reducing the noise and vibration associated with blade turbulence at both low and high speeds. The results were sound meter readings that went from a mere 62 dB(A) at 1000 rpm, to a gentle-on-the-ear 69 dB(A) while at WOT.
Due to the way she's constructed (see "Better Boat: Material Matters," right), the boat felt big, and as tough as they come. Bolstering this impression was the feeling of total solididity of the decks underfoot, as well the heavy-duty rails, cleats, and fairleads I could see during our test, carefully installed on the weatherdeck outside.
But for all her toughness and robustness, the 720 also offers an array of features and amenities, outside and inside, that truly put her on the radar screen of thoroughly relaxed comfort and luxury.
The straightforward, low-profile exterior design boasts a Portuguese bridge that bulwarks the pilothouse as well as wide-open anchor-handling spaces on the foredeck, with a comfortable good-weather seating area nearby. For ease in docking from outside the boat, I counted four standard, remotely-located ZF electronic engine control stations—two at the stern (port and starboard) and two at the wing stations up forward (also port and starboard). On the main deck, aft, there's a dining table with a grill and sink (a perfect spot for alfresco meals in sunset anchorages), while topside, there's an aft deck (accessed from the skylounge or via a staircase) that is large enough for one of the few options on this boat: a tender. The only other big option is a watermaker, by the way. It's amazing how complete the standards list is, quite frankly, including as it does a Garmin electronics package, Intellian HD 6 Sat-TV system, 1,800-pound HD Davit (with power turn and lift), and a ZF JMS joystick-maneuvering system.
As mentioned earlier, sumptuousness is the interior's theme. As soon as you step inside you are greeted by a top-shelf fit and finish and an obvious attention to detail. At the bottom of a wide staircase that communicates between the forward end of the saloon and the lower deck, the 720 features a four-stateroom, five-head layout. The forepeak VIP offers an island queen berth and cedar-lined closets, while an amidships guest stateroom (which shares a head with the VIP) offers side-by-side berths easily converted to a double thanks to a convenient insert. The full-beam master aft has an exceptionally decorative burl overhead, as well as a large walk-in, a cedar-lined closet, a bureau, vanity cabinets, and an ensuite head. The crew's quarters, all the way aft, have upper and lower berths and a separate shower and head compartments, as well as a full galley. Exceptional, finely crafted woodwork, fine linens, and stowage areas ample enough for extended cruising prevail throughout.
On the upper deck, the skylounge has a dining table as well as a helm station, a comfortable seating area, and a head. A beautifully crafted staircase leads down to the main deck, with its galley forward, bar to starboard, formal dining area to port, and aft, a lovely main saloon.
In the engine room, accessed via a large watertight door from the ample swim platform, or by descending the convenient staircase in the saloon's aft starboard corner, I found the kind of forethought and common-sense features that sidestep any and all knuckle busting, knee slamming, and head knocking. While doing maintenance chores in the 720's ER you'll have no trouble getting to all the critical machinery, pumps, valves, hoses, and switches.
And when it comes to safety? As I mentioned earlier, the 720 has plenty of redundant systems, including big duplex Racor fuel-water separators for each engine, a pair of 20-gallon water heaters with heat exchangers, two Kohler (28- and 15.5-kW) gensets, two Glendinning Cablemasters with 72-foot cords, a pair of Newmar 50-amp battery chargers, backup raw-water pumps for the air-conditioning system, hydraulic power-steering pumps on both engines, backup water supplies for each shaft log, and a special selector switch that temporarily combines the batteries aboard for 1,900 amps, just in case you find yourself needing a little emergency starting.
Which is just the kind of feature that tells me this long-range cruiser has your back in a pinch. In fact, after my day aboard the Endurance 720EN, I was absolutely convinced—this boat is well-suited to take care of everything else as well. And that includes your all-important peace of mind while underway and a long way from home.
Hampton Endurance 720 Photo Gallery
Click here for Hampton's contact information and index of articles ➤
Brokerage Listings Powered by BoatQuest.com
Click to see listings of Yachts currently for sale on BoatQuest.com. ➤
This article originally appeared in the February 2014 issue of Power & Motoryacht magazine.


text:
Note: This item is more than 13 years old. Please take the publication date into consideration for any date references.
Print – Plain Text – Permalink
News Release
Media Contact: TPWD News, email@example.com, 512-389-8030
Feb. 9, 2004
South Texas, Mid Coast Hunters Got the Ducks
AUSTIN, Texas Just as Panhandle waterfowlers were blessed last year with prime hunting, this year's hotspots shifted to the other end of the state, according to Texas Parks and Wildlife Department reports.
Recently completed mid-winter aerial surveys of waterfowl populations conducted by TPWD confirmed what many hunters already knew the birds flew south.
"South Texas duck numbers went through the roof this season," said TPWD waterfowl program leader Dave Morrison. "Survey estimates for the region were up more than 60 percent from last year and the Sand Plains in deep South Texas saw a 300 percent jump."
Despite a lull from Thanksgiving through most of December when moderate weather conditions slowed waterfowl migration throughout much of the Central and Mississippi Flyways, Texas actually received more birds this year, 3.8 million compared to 3.7 million last year, according to TPWD estimates.
"All in all I think the season was better than last year," Morrison offered. "The greenwings showed up this year and didn't last year. That's our bread and butter duck on the coast. Gadwalls were also an important component and saved a lot of hunts this year. That was the biggest difference this year; the coast actually got some birds."
"There was a lot of bragging on the early teal season," confirmed TPWD coastal waterfowl biologist David Lobpries. "Most of the guides were limiting out on the prairie and calling it one of the best seasons ever. The first couple of weeks into the regular season some were saying they'd killed more ducks than they had all of last year."
Areas along the middle coast, such as Peach Point and Mad Island Wildlife Management Areas, were reporting twice as many hunters as last year and they weren't coming away disappointed as strap counts averaged nearly two birds apiece.
Despite migration shifts in recent years from the Central to the Mississippi Flyway and mild winters that kept birds to the north, Lobpries also reported more geese showed up this season.
Other parts of the state were not as fortunate. In the Panhandle, biologists reported less than one percent of the playas had water. Those few spots where water was available, however, saw times of excellent hunting, according to TPWD waterfowl biologist Bill Johnson.
The lack of water was a factor in moving many Panhandle birds into the Blackland Prairies region, according to Morrison. Surveys from that area showed a jump from 595,000 birds a year ago to 815,000 birds this season.
Dry conditions also plagued the eastern half of the state for the second straight season, with East Texas and the upper coast being short-changed.
"During early November large numbers of ducks and geese moved down the Central Flyway almost en masse," said Carl Frentress, TPWD waterfowl biologist for East Texas. "Their coordinated arrival was obvious in East Texas. If these birds had found abundant water in the wetlands, they would have stayed. Duck hunters who initially were thrilled with the abundance of arriving migrants soon became disenchanted as the birds departed to more attractive habitats. This predicament characterized the East Texas season for the duration."
Frentress noted that hunting success was hit or miss for much of the season. "Great hunts would be had one weekend to be followed by a complete absence of ducks the next weekend," he said. "At the same time, nearby duck habitats would be producing opposite experiences. I have the feeling the birds were drifting about the wintering grounds seeking satisfactory habitat resources."
Even some of the traditional hotspots like the J.D. Murphree WMA were left holding an empty bag as high salinity levels along the upper coast provided little support for waterfowl.
Publication — Permission is granted to publish, in whole or in part, any news releases on this page.
Print — A print-friendly version of the news release shows only the release with font sizes set to the browser default.
Plain Text — Plain text versions of TPWD news releases are provided for copying and pasting into editing software.
To copy text into an editing software:
- Click a Plain Text link to display the plain text page in your browser.
- Select all.
- Copy.
- Paste in a document in your editing program.
Permalink — This is a direct link to the news release, omitting the navigation context from the URI.
English/Spanish — News releases posted in both English and Spanish have one of these links.
If you have any suggestions for improving these pages, send an e-mail to email@example.com and mention Plain Text Pages.
(5.4.16 i)


text:
THE SQL Server Blog Spot on the Web
A conflict in merge replication occurs when applying a replicated command to the subscriber and:
there is a constraint violation
Foreign Key Violation
Primary Key Violation
there is an error modifying data
Data domain violation
Missing dependencies (trigger firing referencing missing objects)
Security violation (the account the replication agent runs under does not have rights to apply the replicated command on the publisher/subscriber).
You are updating a row which does not exist on the other side of your replication topology
You are deleting a row which does not exist on the other side of the replication topology
You are updating the column on the same row on both sides of a replication topology and are using column level tracking
You are updating the same row on both sides of a replication topology and are using row level tracking.
SQL Server provides a rich set of resolvers to resolve the conflict. You can see the list by issuing a call to:
On a machine with no COM or Business Logic Resolvers will return the below list.
Microsoft SQL Server Additive Conflict Resolver
Microsoft SQL Server Averaging Conflict Resolver
Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver
Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver
Microsoft SQL Server Download Only Conflict Resolver
Microsoft SQL Server Maximum Conflict Resolver
Microsoft SQL Server Merge Text Columns Conflict Resolver
Microsoft SQL Server Minimum Conflict Resolver
Microsoft SQL Server Priority Column Resolver
Microsoft SQL Server Subscriber Always Wins Conflict Resolver
Microsoft SQL Server Upload Only Conflict Resolver
Microsoft SQLServer Stored Procedure Resolver
However in some cases you wish to extend the way a conflict is handled by using a stored procedure resolver. A stored procedure resolver allows you to fire a custom stored procedure when a conflict occurs. The custom stored procedure resolver can handle a conflict arising from a single article or multiple articles.
There is some overlap between what a Business Logic Resolver can do for you over a Stored Procedure Resolver. Here is a breakdown of what the differences between a Businesses Logic Resolver can handle vs a Stored Procedure Resolver.
Business Logic Resolver
Stored Procedure Resolver
Development Language
Any .Net Language
Can be modified on the fly
Yes, but will require dll recompilation
Faster than BLR.
Can Handle the following Replication Events
Conflicts, Errors, DML
Can detect which column has changed?
Somewhat complicated but allows step by step processing
Can be done by logging.
The parameters you must pass to your stored procedure resolver are:
Data Type
Name of the owner of the table for which a conflict is being resolved. This is the owner for the table in the publication database.
Name of the table for which a conflict is being resolved.
Unique identifier for the row having the conflict.
Name of the server from where a conflicting change is being propagated.
Name of the database from where conflicting change is being propagated.
@log_conflict OUTPUT
Whether the merge process should log a conflict for later resolution:
@conflict_message OUTPUT
Message Logged in Conflict Tables
The owner of the published table at the Subscriber.
Table above snagged from ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10rp_1devconc/html/76bd8524-ebc1-4d80-b5a2-4169944d6ac0.htm
Here is an example of how this works.
use MasterGOset nocount on GO--need to access cmdshell to create a directory called c:\temp--on most modern os's the program files directory is locked down--and you will be unable to create a snapshot in the default folderexec sp_configure 'show advanced options',1reconfigure with overrideexec sp_configure 'xp_cmdshell',1reconfigure with overrideexec xp_cmdshell 'md c:\temp'GOif exists(select *from sys.sysdatabases where name='StoredProcedureResolverPub')beginexec sp_replicationdboption 'StoredProcedureResolverPub','publish', falseexec sp_replicationdboption 'StoredProcedureResolverPub','merge publish', falsealter database StoredProcedureResolverPub set single_user with rollback immediate drop database StoredProcedureResolverPub endCreate Database StoredProcedureResolverPubGOexec sp_replicationdboption 'StoredProcedureResolverPub','merge publish', trueGOif exists(select *from sys.sysdatabases where name='StoredProcedureResolverSub1')beginexec sp_replicationdboption 'StoredProcedureResolverSub1','publish', falseexec sp_replicationdboption 'StoredProcedureResolverSub1','merge publish', falsealter database StoredProcedureResolverSub1 set single_user with rollback immediate drop database StoredProcedureResolverSub1endGOCreate Database StoredProcedureResolverSub1GOif exists(select *from sys.sysdatabases where name='StoredProcedureResolverSub2')beginexec sp_replicationdboption 'StoredProcedureResolverSub2','publish', falseexec sp_replicationdboption 'StoredProcedureResolverSub2','merge publish', falsealter database StoredProcedureResolverSub2 set single_user with rollback immediate drop database StoredProcedureResolverSub2endCreate database StoredProcedureResolverSub2use StoredProcedureResolverPubGOCreate Table table1(PK int IDENTITY(1,1) NOT NULL PRIMARY KEY, charcol varchar(40) NULL, originating_db varchar(40) NULL DEFAULT ('StoredProcedureResolverPub') , rowguid uniqueidentifier ROWGUIDCOL NOT NULL UNIQUE CONSTRAINT table1_rowguid_Constraint DEFAULT (newsequentialid()) ) GOdeclare @counter int=1while @counter<1000begininsert into table1( charcol) values('test')select @counter=@counter+1endGO--a log table which records when the stored procedure resolver was used.Create table LogTable(PK int identity primary key, dtstamp datetime)GO--here is our stored procedure conflict resolverCREATE PROC MyConflictResolver(@tableowner sysname, @tablename Sysname, @rowguid Uniqueidentifier, @subscriber sysname, @subscriber_db sysname, @log_conflict int OUTPUT, @conflict_message nvarchar(512) OUTPUT, @destowner Sysname)ASset nocount on
set @log_conflict =1--if set to NULL or 0 no conflicts are logged--just for kicks I am going to update a column from a row with the pk value of 11 on the publisher.--you will note that this change does not get replicated.--this causes a lack of consistency between your publisher and subscriber--this is generally not considered to be a good thing --but something to tuck away into your little gray cells--in case you ever have a req like thisupdate table1 set originating_db='from resolver' where pk=11
SELECT @conflict_message ='The same row was conflicted at both '+@@ServerName +'.'+db_name()+' and '+@subscriber+'.'+@subscriber_db+'. The resolver chose the update from '++@@ServerName +'.'+db_name()+' as the winner.'
INSERT INTO LogTable(dtstamp) VALUES(getdate())
SELECT PK, 'From Stored Procedure Conflict Resolver', originating_db, rowguid FROM table1 where rowguid=@rowguidGOexec sp_addmergepublication StoredProcedureResolver, @snapshot_in_defaultfolder=false,@alt_snapshot_folder='c:\temp', @publication_compatibility_level='100RTM', @conflict_logging =bothGOexec sp_addpublication_snapshot StoredProcedureResolverGOexec sp_addmergearticle StoredProcedureResolver, table1, @source_object=table1, @article_resolver='Microsoft SQLServer Stored Procedure Resolver', @resolver_info=MyConflictResolverGosp_addmergesubscription StoredProcedureResolver, @@Servername, 'StoredProcedureResolverSub1'GOsp_addmergesubscription StoredProcedureResolver, @@Servername, 'StoredProcedureResolverSub2'GOexec sp_startpublication_snapshot StoredProcedureResolver--waiting for 1 minute for the snapshot to be generatedWAITFOR DELAY '00:01'exec sp_startmergepushsubscription_agent StoredProcedureResolver, @@ServerName, StoredProcedureResolverSub1GOexec sp_startmergepushsubscription_agent StoredProcedureResolver, @@ServerName, StoredProcedureResolverSub2GO--waiting for 1 minute for the snapshot to be appliedWAITFOR DELAY '00:01'GOuse StoredProcedureResolverSub1GOupdate Table1 set charcol='StoredProcedureResolverSub1' where pk<10GOuse StoredProcedureResolverSub2GOupdate Table1 set charcol='StoredProcedureResolverSub2' where pk<10GOuse StoredProcedureResolverPubGO
exec sp_startmergepushsubscription_agent StoredProcedureResolver, @@ServerName, StoredProcedureResolverSub1GOexec sp_startmergepushsubscription_agent StoredProcedureResolver, @@ServerName, StoredProcedureResolverSub2GOWAITFOR DELAY '00:01'GOselect Reason_text from MSmerge_conflicts_info GOselect * from MSmerge_conflict_StoredProcedureResolver_table1GOselect * from table1GOselect * from LogtableGOHere is a conflict within the Conflict Viewer:
Now look for the row less traveled. This is the row modified by inside our conflict resolver. Notice how it does not travel
--the row less traveled! --this was the one we updated in the stored procedure conflict resolver--but it does not move to the subscribers!GOselect * from StoredProcedureResolverPub.dbo.table1 where pk=11GOselect * from StoredProcedureResolverSub2.dbo.table1 where pk=11GOselect * from StoredProcedureResolverSub1.dbo.table1 where pk=11GO
You may notice that the Publisher db has won the conflict, but the rows were both updated on the subscriber dbs. This is because the default is subscription type is Client – which means the first DML to the publisher is the one which will persist.
It is worth pointing out that the Stored Procedure Conflict Resolver not only return the results set of data to be applied on the publisher and subscriber, but can also send out alerts, write data to replicated tables (which will not be replicated), write data to replicated tables, log data, in short do anything your skill in TSQL allows you to within the context of the security context your replication agent runs under.
It can't however access Web Sync Subscribers, Heterogeneous databases, or SQLCE subscribers.
Here is an example of using a stored procedure resolver to access data on the subscriber. Note we are using dynamic SQL for this.
alter PROC MyConflictResolver ( @tableowner SYSNAME , @tablename SYSNAME , @rowguid UNIQUEIDENTIFIER , @subscriber SYSNAME , @subscriber_db SYSNAME , @log_conflict INT OUTPUT , @conflict_message NVARCHAR(512) OUTPUT , @destowner SYSNAME )AS DECLARE @str NVARCHAR(MAX) DECLARE @newstr NVARCHAR(MAX) DECLARE @params NVARCHAR(MAX)
DECLARE @originating_db varchar(40) DECLARE @PK int DECLARE @charcol varchar(40) DECLARE @table1 Table (PK int, charcol varchar(40), originating_db varchar(40),rowguid uniqueidentifier) SET @str = 'SELECT @originating_db = originating_db, @PK = PK, @charcol = charcol FROM [@subscriber].@subscriber_db.dbo.Table1 WHERE rowguid=''@rowguid''' SELECT @newstr = REPLACE(@str, '@subscriber_db', @subscriber_db) SELECT @newstr = REPLACE(@newstr, '@subscriber', @subscriber) SELECT @newstr = REPLACE(@newstr, '@rowguid', @rowguid)
SELECT @params = N'@subscriber sysname, @subscriber_db sysname, @rowguid uniqueidentifier, @originating_db varchar(40) OUTPUT, @PK int OUTPUT, @charcol varchar(40) OUTPUT'
select @newstr EXEC sp_executesql @newstr, @params, @subscriber, @subscriber_db, @rowguid, @originating_db = @originating_db OUTPUT, @PK = @PK OUTPUT, @charcol = @charcol OUTPUT insert into @table1(PK, originating_db, charcol, rowguid) select @PK, @originating_db, @charcol, @rowguid select * From @table1
Bi-Directional replication is copying data from one server to another where:
• either server can be the source or destination, and• the data being copied can be in the same tables on both sides.
For example, I want to replicate a database between Server A and Server B, so that:
• the data which originates on Server A will be replicated to Server B, and • the data which originates on Server B will be replicated to Server A.
Essentially, I want writeable copies of the data in two different databases - which might be on the same or different servers - and I want the data to be consistent ( i.e. - the same on both sides).
Most implementations on which I consult have a "real time" requirement, i.e. at any one time the data in both database is identical. Though not really achievable using bi-directional replication, this may be achieved by doing some sort of split write (open a transaction, write on server A, write on Server B, commit the transaction, and then return to the application so it can move on and do different work).
Of course, using a split write has significant application latency considerations, and the link between the two servers must be very stable. Application latency refers to how long it takes for the application to commit a transaction to the database(s). The two servers also must be very close to each other; the greater the distance between the two servers, the greater the application latency. Basically, if you go down the split write route, you do get identical point in time synchronization of the two databases, but the cost is transferred to application latency where transactions which originally took 10 ms, may now take 100 ms or more.
Normally, I have some education process where I have the client reduce the real time expectations to something of the order of several seconds or even minutes.The most common usage is for Load Balancing or Fault Tolerance/Disaster Recovery. Load balancing normally means the load is balanced between one or more servers - as one server cannot handle the load, the load spills over to servers which have a lighter load. It also can mean or may entail that clients connecting to one server will continue to connect to that server for the lifetime of their sessions – sometimes called "sticky session" or persistence. Fault Tolerance means the ability of a server to with stand a localized failure and continue to serve clients with minimal disruption of services and minimal data loss. Disaster recovery means the ability to withstand regional failures and continue business operations in another location. I should point out that bi-directional transactional replication is a poor fit for all of these cases since:
1) Replication does not offer predictable latency, so at one instant my latency can be several seconds, while a half day later it can be several minutes, and sometimes several hours. Using replication for disaster recovery means that your exposure to data loss can is unpredictable. Using replication for load balancing is also a poor choice as a client may do some work on one node, and then return seconds later and hit the other node expecting to have the data that was just entered in the first node. Due to replication latency - this data, however, has not yet made its way to the second node. 2) There is no automatic client redirection as found in mirroring or clustering. 3) There is no load balancing or workload distribution; in our case, as the workload on Server A increases, clients will not be automatically redirected to Server B - as in the case of NLB.
With the above points being noted the majority of my bi-directional transactional replication implementations have been meant to address both fault tolerance/disaster recovery and load balancing goals and they do work well.
The goal of some implementations of bi-directional transactional replication is to reduce contention on one server by scaling out the load over a multitude of servers.
This can be a good fit in some cases. For example, with read intensive workloads, you will find that the read activity can be halved by redirecting half of your clients to the second node. In other words, instead of having 100 clients banging away at Server A, you can distribute the load by having 50 of them bang away at Server B (the remaining 50 clients will bang away at Server A).
However, if you are trying to reduce write contention, the dynamics are different. If I have 1000 inserts per second on Server A coming from 100 clients, and I decide to load balance by having 50 clients work on Server A and 50 on Server B, I will still end up with 1000 inserts per second on Server A – 500 from the 50 clients on Server A, and 500 from the replication process carrying over the 500 inserts per second from the clients banging away at Server B. The end result is the same level of writes and twice the licensing/hardware and maintenance costs.
But the transactional footprint can be quite different. If the transactional context of the client operations is such that it causes contention due to the transaction length or footprint, you may find that replicating the transactions to the other node will result in far less resource consumption than the transactional footprint on the originating server.
For instance, consider a case when an insert statement which occurs on the publisher is the result of a 5 table join, as follows:Insert into tableName
Select col1, col2, col3, col4 from tableName1 Join tablename2 on TableName2.pk=TableName1.pkLeft join tablename3 on TableName3.pk=TableName2.pkLeft join tablename4 on TableName4.pk=TableName3.pkLeft join tablename5 on TableName5.pk=TableName4.pk
This will be replicated as:
Insert into tableName(col1,col2, col3, col4) values(col1, col2, col3, col4)
Of course the above would be wrapped in a replication stored procedure, I have stripped everything away except the essential insert for clarity.
This replicated insert statement will just be the final state of the row and will not have to reference the 5 table join on the subscriber. The consequence of this is a much smaller resource footprint on the subscriber, and the locks will be held for a shorter time period.
Also, consider this transaction occurring on the publisher:
Begin TranExec Proc1 -- inserts 5 rows into table1 as the result of some lengthy calculationExec Proc2 -- inserts 5 rows into table2 as the result of some lengthy calculationExec Proc3 -- inserts 5 rows into table3 as the result of some lengthy calculationExec Proc4 -- inserts 5 rows into table4 as the result of some lengthy calculation...Exec Proc20 -- inserts 5 rows into table20 as the result of some lengthy calculationCommit tran
As you can imagine, the transaction footprint on the publisher would be far more severe than the simple 100 row insert which would occur on the subscriber - even though the transaction would be held for the entire 100 row insert on both the publisher and the subscriber. On the subscriber, the transaction is merely 100 insert statements – no lookups, no 5 table joins, etc. So a transaction that takes several seconds on the publisher will
• take far less time on the subscriber, • have a minimal IO hit, • and cause significantly less blocking/deadlocking there.
One last item I wish to cover before diving into an example is to explain why bi-directional transactional replication is normally the better choice amidst the other contenders listed below.
Merge Replication
Merge replication can be used, but is generally a poor fit since the tracking triggers add considerable application latency, and the replication latency of the synchronization tends to be much higher than the alternatives. There is also the added complexity of a merge replication solution and the guid column requirement.
Peer to Peer Replication
Peer to Peer replication can be used, but it is much slower than bi-directional transactional replication and has a much smaller feature set. For example, in Peer to Peer replication I cannot use custom stored procedures, there is no row or column filtering, or automatic identity range management. The Enterprise Edition requirement normally makes Peer to Peer replication a costly choice.
Here is an illustration of just how slowly Peer to Peer replication will perform: to replicate 10,000 inserts with a CommitBatchSize of 100 and CommitBatchThreshold of 1000 (the defaults) takes an average of 6.325 s over 10 runs using bi-directional transactional replication, and an average of 12.939 s over 10 runs using peer to peer replication. Keep in mind that we are looking at an edge case and YMMV, but, in general, bi-directional transactional replication is significantly faster than Peer to Peer. On the downside, you cannot practically scale bi-directional replication to more than 2 nodes – it can be done, but performance degrades significantly the more nodes you add to your topology. Just an aside - Peer to Peer can't be scaled beyond 10 nodes easily.
Updatable Subscriptions
Updatable Subscriptions are another option - however; they are intended for topologies where the majority of the transactions originate on the publisher. Immediate updating is a split write, and performance degrades as a function of the link speed/bandwidth for subscriber side originating transactions. Should the link go down between the publisher and subscriber, the published tables will be read-only on the subscriber. Queued is an option, but again - it is tuned for the majority of the DML originating on the Publisher, not the Subscriber. Also keep in mind that Updatable Subscriptions are deprecated.
Setting up bi-directional transactional replication requires two things:1) All identity columns must be set a. to NOT FOR REPLICATION, andb. odd on one side and even on the other c. the increment should be adjusted to 2 d. and reseed to hand out an odd value on the odd side and an even on the other.2) All triggers and constraints should be set to NOT FOR REPLICATION. You don't want the trigger to fire twice as it has already done its work on the publisher (auditing may be an exception here).
This can involve considerable work. Marking identity column NOT FOR REPLICATION is easy using the proc sp_identitycolumnforreplication. Changing the current identity value to odd or even is again simple using DBCC CheckIdent. However, changing the increment involves recreating the table. Normally, I would do as follows:
• Script all triggers, constraints, indexes• Script out the tables and recreate the new ones with a _temp extension• Move the table data from the original table to the new table using bcp.• Drop the original table and rename the new table the old name, ie OriginalTable data is copied to OriginalTable_temp, OriginalTable is dropped and OriginalTable_Temp is renamed as OriginalTable• Apply the triggers, constraints and indexes.
You will likely need to figure out which are your largest tables, and then group them into batches you can do simultaneously. For databases with large numbers or tables, doing this sequentially can be very time consuming and will involve considerable downtime. You may want to group your tables by size and then run multiple bcp scripts at one time - each dedicated to different tables to minimize your downtime.
Doing this on a live production system, however, requires a different approach:• Create the first publication/subscription pair (Server A and Server B in our case). Ensure you use the no-sync subscription option.• Ensure that the distribution agent is disabled. • Backup the database and restore it on the Subscriber (Server B).
Now you have all sorts of time to get your subscriber setup as the transactions occurring on the Publisher (Server A) will pool in its distribution database.
Set all identity columns on Server B to have an island of ranges - several orders of magnitude above what is being currently assigned on the original source. For example, on Server A you may be currently assigning identity ranges in the millions. Then, set your range on the subscriber to 100 million. This gives you a lot of wiggle room before primary key collisions occur when the same identity range value is assigned on both sides. Naturally, you want some alerting job that will send out email when you are exhausting a range, or when one range is likely to collide with another.
Setting up bi-directional transactional replication is simple. Once you have prepped your tables, all you need to do is ensure that the @loopback_detection parameter of sp_addsubscription is set to "true".
Here is an end to end example:
USE masterGOIF EXISTS(SELECT * FROM sys.databases WHERE name='BIDINodeA')BEGINEXEC sp_removedbreplication 'BIDINodeA'ALTER DATABASE BIDINodeA SET SINGLE_USER WITH ROLLBACK IMMEDIATEDROP DATABASE BIDINodeAENDGOIF EXISTS(SELECT * FROM sys.databases WHERE name='BIDINodeB')BEGINEXEC sp_removedbreplication 'BIDINodeB'ALTER DATABASE BIDINodeB SET SINGLE_USER WITH ROLLBACK IMMEDIATEDROP DATABASE BIDINodeBENDCREATE DATABASE BIDINodeAGOEXEC sp_replicationdboption 'BIDINodeA', 'publish', trueGOCREATE DATABASE BIDINodeBGOEXEC sp_replicationdboption 'BIDINodeB', 'publish', trueGOUSE BIDiNodeAGOIF exists(SELECT * FROM sys.objects WHERE type='u' AND name='Table1')DROP TABLE Table1GOCREATE TABLE Table1(PK INT IDENTITY (1,2) NOT FOR REPLICATION CONSTRAINT Table1PK PRIMARY KEY, Charcol VARCHAR(20), originatingDB sysname DEFAULT db_name(), dtstamp DATETIME DEFAULT GETDATE())GOEXEC sp_addpublication 'BIDINodeA', @Status=ACTIVEGOEXEC sp_addarticle 'BIDINodeA', @article='Table1',@source_object='Table1' ,@identityrangemanagementoption='manual'GOEXEC sp_addsubscription 'BIDINodeA','ALL', @@ServerName, 'BIDINodeB', 'Replication support only', @loopback_detection='true'GOUSE BIDiNodeBGOIF exists(SELECT * FROM sys.objects WHERE type='u' AND name='Table1')DROP TABLE Table1GOCREATE TABLE Table1(PK INT IDENTITY (2,2) NOT FOR REPLICATION CONSTRAINT Table1PK PRIMARY KEY, Charcol VARCHAR(20), originatingDB sysname DEFAULT db_name(), dtstamp DATETIME DEFAULT GETDATE())GOEXEC sp_addpublication 'BIDINodeB', @Status=ACTIVEGOEXEC sp_addarticle 'BIDINodeB', @article='Table1',@source_object='Table1', @identityrangemanagementoption='manual'GOEXEC sp_addsubscription 'BIDINodeB','ALL', @@ServerName, 'BIDINodeA', 'Replication support only', @loopback_detection='true'GOUSE BIDINodeAGODECLARE @counter INTSET @counter=1WHILE @counter<=10BEGININSERT INTO BIDINodeA.dbo.Table1(Charcol) VALUES('test')SELECT @counter=@counter+1ENDGOUSE BIDINodeBGODECLARE @counter INTSET @counter=1WHILE @counter<=10BEGININSERT INTO BIDINodeB.dbo.Table1(Charcol) VALUES('test')SELECT @counter=@counter+1ENDGOSELECT *from BIDINodeA.dbo.Table1SELECT *from BIDINodeB.dbo.Table1Note, that you may need to wait a couple of seconds for the above two queries for return 20 rows. Rows originating from BIDINodeA will have a value for the OriginatingDB column of BIDINodeA, and rows originating from BIDINodeB will have a value for the OriginatingDB column of BIDINodeB.
There are some caveats with Bi-Directional Transactional Replication.
The first is that should a failure event occur, which might cause a lack of data consistency (i.e. different data on both sides), the distribution agent will fail/stop until the administrator can step in and clear the event which is causing the failure. This is normally a good thing, as it prevents your databases from losing consistency (i.e. having different data). This event will likely be a conflict – an attempt to:
• insert a primary key value on a node which causes a primary key violation; • update a row which is deleted; • delete a row which is already deleted.
Most frequently the goal in a bi-directional replication topology is to present two data sets to your clients which are within seconds of synchronization with each other.
When a data consistency error occurs and the agents shut down the two data sets will get progressively more and more out of sync; in other words they will become disconnected islands of data as each set of clients is entering/modifying data on each island. An insert occurring on Node A will stay in Node A. If the client is redirected to node B and does not see their data – chances are that they will try to re-enter their data this time on Node B – which when the synchronization process occurs, will cause a conflict.
It becomes critical to clear any data consistency errors as quickly as possible to prevent further conflicts. For some implementations this can be difficult. Some implementation it is very simple. I normally have email alerts going off to the team when these events occur. Some implementations never raise alerts and it makes me check them to make sure they are working. Others are very noisy. For example one company feels the need to replicate the ASP.NET state tables. This results in a lot of noise, all of it false positives – well so far - all of it false positives.
Another factor to consider is there is apparently a bug in bi-directional transactional replication which will raise "row not found" error messages. I have only heard about is anecdotally.
Quite often it is more important to keep the agents running, and then run a validation to determine where the error is, as opposed to let the agents stop, investigate and clear the error. The reason why it is more important to keep the agents running is that the longer the agents are not running for, the greater the chances of future conflicts occurring is.
The best way is to skip the error(s) using the Continue On Data Consistency Error Profile. However, this means that if errors are skipped there is a chance your database will get progressively more and more out of sync or different.
It then becomes critical to run publication validations to find out what tables are different.
I normally schedule validations at least daily and run the validation twice to see if the validation error occurs on the same tables for both validation runs. My reasoning is the first time a validation error occurs, it could be due to in-flight data. If the table shows up with a validation error twice in a row, it likely is a true out of sync condition as opposed to inflight data.
Non-Convergence and swapping
Another factor to consider is that if I update the same column on the same row on both sides of a bi-directional replication topology, my values will swap.
Consider this update.
Update TableName1 set Col1='NodeA' where PK =1 -- on NodeAUpdate TableName1 set Col1='NodeB where PK =1 -- on NodeB
Before my synchronization the state of the row will look like this:
Select * from TableName1 where PK=1 -- on NodeA1, NodeASelect * from TableName1 where PK=1 -- on Nodeb1, NodeB
After synchronization it will look like this:
Select * from TableName1 where PK=1 -- on NodeA1, NodeBSelect * from TableName1 where PK=1 -- on Nodeb1, NodeA
The values have swapped. Granted the chances of such an update happening are slim, but it can happen. Ideally with your data perfectly partitioned only one client will be active on one node at one time and will only work with data he/she owns so the chances of swapping are slim.
DML Changes
Bi-Directional Transactional Replication can replicate DML changes. However there is a caveat. A change made on Node A will be replicated to Node B and the replication stored procedures Node A uses to apply commands to Node B will be updated for the schema change on Node B. But the replication stored procedures that Node B uses to replicate changes occurring on Node B to Node A will not reflect this change.
It becomes necessary to regenerate these stored procedures. Either through a database trigger or a SQL Server job than runs at periodic intervals. I use • sp_scriptinsproc• sp_scriptupdproc
For this. I don't need to worry about the delete procs as they only need to account for the PK.
Here is an example of such a job.
--UpdateProcs looks like this:CREATE PROCEDURE [dbo].[UPDATEPROCS] ( @table SYSNAME ) AS DECLARE @articleNumber INT DECLARE @insertType INT DECLARE @updateType INT DECLARE @rowcount INT DECLARE @Statement VARCHAR(MAX) DECLARE @end VARCHAR(MAX) DECLARE @top VARCHAR(MAX) DECLARE @middle VARCHAR(MAX) CREATE TABLE #table1 ( pk INT IDENTITY , varcharcol VARCHAR(MAX) ) SELECT @articleNumber = artid , @insertType = CASE WHEN ins_cmd LIKE 'C%' THEN 1 ELSE 0 END , @updateType = CASE WHEN upd_cmd LIKE 'C%' THEN 1 ELSE 0 END FROM sysarticles WHERE dest_table = @table IF @insertType = 1 BEGIN SET @statement = ' ' SET @end = ' ' TRUNCATE TABLE #table1 INSERT INTO #table1 EXEC sp_scriptinsproc @articleNumber SELECT @rowcount = MAX(pk) FROM #table1 SELECT @top = varcharcol FROM #table1 WHERE pk = 1 SELECT @middle = varcharcol FROM #table1 WHERE pk = 3 SELECT @statement = @statement + ' ' + varcharcol FROM #table1 WHERE pk > 4 AND pk < @rowcount - 2 SELECT @end = @end + ' ' + varcharcol FROM #table1 WHERE pk >= @rowcount - 1 EXEC(@top) EXEC(@middle) EXEC(@statement) EXEC(@end) END ELSE BEGIN SET @statement = ' ' SET @statement = ' ' SET @end = ' ' TRUNCATE TABLE #table1 INSERT INTO #table1 EXEC sp_scriptsinsproc @articleNumber SELECT @rowcount = MAX(pk) FROM #table1 SELECT @top = varcharcol FROM #table1 WHERE pk = 1 SELECT @middle = varcharcol FROM #table1 WHERE pk = 3 SELECT @statement = @statement + ' ' + varcharcol FROM #table1 WHERE pk > 4 AND pk < @rowcount - 2 SELECT @end = @end + ' ' + varcharcol FROM #table1 WHERE pk >= @rowcount - 1 EXEC(@top) EXEC(@middle) EXEC(@statement) EXEC(@end) END--this is the update statement IF @UpdateType = 1 BEGIN SET @statement = ' ' SET @end = ' ' TRUNCATE TABLE #table1 SET @statement = '' INSERT INTO #table1 EXEC sp_scriptupdproc @articleNumber SELECT @rowcount = MAX(pk) FROM #table1 SELECT @top = varcharcol FROM #table1 WHERE pk = 1 SELECT @middle = varcharcol FROM #table1 WHERE pk = 3 SELECT @statement = @statement + ' ' + varcharcol FROM #table1 WHERE pk > 4 AND pk < @rowcount - 2 SELECT @end = @end + ' ' + varcharcol FROM #table1 WHERE pk >= @rowcount - 1 EXEC(@top) EXEC(@middle) EXEC(@statement) EXEC(@end) END ELSE BEGIN SET @statement = ' ' SET @end = ' ' TRUNCATE TABLE #table1 SET @statement = '' INSERT INTO #table1 EXEC sp_scriptsupdproc @articleNumber SELECT @rowcount = MAX(pk) FROM #table1 SELECT @top = varcharcol FROM #table1 WHERE pk = 1 SELECT @middle = varcharcol FROM #table1 WHERE pk = 3 SELECT @statement = @statement + ' ' + varcharcol FROM #table1 WHERE pk > 4 AND pk < @rowcount - 2 SELECT @end = @end + ' ' + varcharcol FROM #table1 WHERE pk >= @rowcount - 1 EXEC(@top) EXEC(@middle) EXEC(@statement) EXEC(@end) ENDAs you can see bi-directional transactional replication can be a good fit for some scenarios.Before you implement a bi-directional. Ensure you test with a representative workload before deploying into production.
On the newsgropes recently I have encountered some posters who are perplexed by the results of their full-text searches.
The first poster was puzzled as to why searches on f.b.i. would not find F.B.I. in his content. SQL FTS and Microsoft Search products index uppercased tokens with periods in them differently than other lower or upper cased tokens. During indexing most language word breakers will index upper cased tokens with periods in them as the token, and then the token with all the periods stripped out. So F.B.I. is indexed as F.B.I. and FBI. All tokens are stored upper cased in the index with the exception of path names (for cosmetic reasons - e.g. in Indexing services a path like c:\TeMp is stored as c:\temp as lowercase was considered to look better than uppercase).
There is no length cut off as far as I am aware. For example, C.R.E.E.P. (Committee to Re-Elect the President - the unfortunately and what we can only hope was unintentional acronym for President Richard Nixon's second election campaign) is indexed as CREEP and C.R.E.E.P. I've tried up to 10 letter combinations.
Here is an example:
Note that this works for most languages but does NOT work for the neutral, Chinese (both types), Japanese, and Thai word breakers. They will index F.B.I. as F, B, and I - in other words as three separate letters. Korean will index F.B.I. as F.B.I
The next post covers some of the unusual behaviors while searching on C#, C+, C++, and F#, etc
A friend of mine called me up last night. He had a problem replicating 300,000,000 transactions per day, or was it per hour. Can't recall, it was a late night.
Anyhowze, with volumes like this replication might not be the best tool. His problem was that the distribution agent to two of his subscribers was hanging on initializing. From experience I know this is caused by depleted buffers on the publisher and the only solution I know of is a reboot. Naturally this was not an option for him.
His has his max distribution retention setting to 72 hours and was under the impression that this would decrease the amount of time required to purse distributed transactions. I told him that min distribution retention setting controlled this, and that his problem with expired subscribers was likely caused by this low max distribution retention setting or the history setting. Subscribers are expired based on the lesser of these two settings.
Anyhowze on with my story - so he asks me what he can do to improve performance and I recommended he use sp_scriptdynamicupdproc to create a more efficient update proc (as his app did heavy updating), or its SQL 2005 analogue sp_scriptsupdproc.
I expect another midnight call from him soon as he continues in his losing battle.
There seems to be some confusion out there in the internet about how to implement transaction marks. Or perhaps I was merely very confused about how to implement them.
Transaction marks allow you to restore two or more database to a consistent point in time. For example if you have two database and your app writes to both databases, how do you restore them to a consistent point in time without kicking all your users off the databases? This is complicated by many things, for example backup speed.
I googled looking for a working example but could not find one, so here is a script I wrote to demonstrate it.
create database MarkedTransactionGOcreate database MarkedTransaction1GOuse MarkedTransactiongocreate table test1(pk int)GOuse MarkedTransaction1GOcreate table test1(pk int)GObackup database MarkedTransaction to disk='c:\MarkedTransaction.bak' with initGObackup database MarkedTransaction1 to disk='c:\MarkedTransaction1.bak'with initGObegin transactioninsert into MarkedTransaction.dbo.test1(pk) values(1)insert into MarkedTransaction1.dbo.test1(pk) values(1)commit tranGObegin transaction mark6 with mark 'marked transaction'insert into MarkedTransaction.dbo.test1(pk) values(2)insert into MarkedTransaction1.dbo.test1(pk) values(2)commit transaction mark6GObegin transaction mark7 with mark 'marked transaction - 1'insert into MarkedTransaction.dbo.test1(pk) values(3)insert into MarkedTransaction1.dbo.test1(pk) values(3)commit tran mark7GObackup log MarkedTransaction to disk='c:\MarkedTransactionlog.bak' with initbackup log MarkedTransaction1 to disk='c:\MarkedTransactionlog1.bak' with initGOuse masterGO--backing up the tailbackup log MarkedTransaction to disk='c:\MarkedTransactionlogTail.bak' with init, norecoverybackup log MarkedTransaction1 to disk='c:\MarkedTransactionlog1Tail.bak' with init, norecoveryGO--restoring the databaserestore database markedtransaction from disk='c:\markedtransaction.bak' with norecovery restore database markedtransaction1 from disk='c:\markedtransaction1.bak' with norecoveryGO--restoring the log RESTORE LOG MarkedTransaction FROM DISK = 'c:\MarkedTransactionlog.bak'WITH STOPATMARK = 'mark6', recoveryGORESTORE LOG MarkedTransaction1 FROM DISK = 'c:\MarkedTransactionlog1.bak' WITH STOPATMARK = 'mark6', recovery GOselect * from MarkedTransaction.dbo.test1select * from MarkedTransaction1.dbo.test1--both 1, 2 are there, 3 is not--repeating, but this time we will stop beforebackup database MarkedTransaction to disk='c:\MarkedTransaction.bak' with initGObackup database MarkedTransaction1 to disk='c:\MarkedTransaction1.bak'with initGObegin transactioninsert into MarkedTransaction.dbo.test1(pk) values(6)insert into MarkedTransaction1.dbo.test1(pk) values(6)commit transactionGObegin transaction mark8 with mark 'marked transaction -2'insert into MarkedTransaction.dbo.test1(pk) values(7)insert into MarkedTransaction1.dbo.test1(pk) values(7)commit transaction mark8GObegin transaction insert into MarkedTransaction.dbo.test1(pk) values(8)insert into MarkedTransaction1.dbo.test1(pk) values(8)commit transaction GObackup log MarkedTransaction to disk='c:\MarkedTransactionlog.bak' with initbackup log MarkedTransaction1 to disk='c:\MarkedTransactionlog1.bak' with initGOuse masterGObackup log MarkedTransaction to disk='c:\MarkedTransactionlogTail.bak' with init, norecoverybackup log MarkedTransaction1 to disk='c:\MarkedTransactionlog1Tail.bak' with init, norecoveryGORESTORE Database MarkedTransaction from disk='c:\markedtransaction.bak' with norecoveryRESTORE Database MarkedTransaction1 from disk='c:\markedtransaction1.bak' with norecoveryGORESTORE LOG MarkedTransaction FROM DISK = N'c:\MarkedTransactionlog.bak' WITH STOPBEFOREMARK = N'mark8' , recoveryGORESTORE LOG MarkedTransaction1 FROM DISK = N'c:\MarkedTransactionlog1.bak' WITH STOPBEFOREMARK = N'mark8' , recoveryGOselect * from MarkedTransaction.dbo.test1select * from MarkedTransaction1.dbo.test1--both 1, 2, and 6 are there, 7 is not


text:
Here's how Xavier Su'a-Filo is bulking up: three to four cups of whey protein dissolved in a shake, three times a day.
"I just continue to put down that protein like it's nobody's business," he said. "It's hard. You ever try to eat that much protein?"
The junior, a first-team, All-Pac-12 selection last year, will enter the fall as arguably the conference's top lineman. Capable of playing both guard and tackle, head coach Jim Mora called him "a rare football player."
He's accomplished this despite not being at peak strength as a sophomore, having spent two years on a Mormon mission in Alabama and Florida.
The Pleasant Grove, Utah, native said although he hasn't gained much weight - up from 307 pounds to 310 - he feels significantly better after a winter workout program with strength coach Sal Alosi.
As a result, he's caught less flak from his teammates, too.
"There's a lot of strong guys on our offensive line," Su'a-Filo said. "They've noticed I've gotten stronger in the weight room so they don't give me so much of a hard time.
"(Last year), they just didn't understand how I could play and move out here, but in the weight room, they're like `C'mon, man.' "
Practice scuffles
Mora has made note of how great the team's energy has been in the past two practices, but the side effect has been some extra contact after plays.
Three players were ejected about two-thirds of the way through Saturday's practice: junior Alexandru Ceachir and redshirt sophomore Kevin McReynolds - both offensive linemen - and redshirt freshman linebacker Nate Iese.
"I've been doing this long enough to know that there's going to be some scuffles, some dust-ups," Mora said. "But when you get in the open field and you throw a haymaker like that, you're hurting your football team."
Pitt transfer at practice
Former five-star running back Rushel Shell attended UCLA's practice Saturday and stood on the sideline wearing a white Bruins football sweater.
Shell is exploring options after deciding to transfer from Pitt, where he was second on the team with 641 yards as a freshman. He rushed for four touchdowns last season, as well as a 157-yard game against Virginia Tech.
Shell requested clearance to transfer to UCLA, Cal, Arizona State or Arizona, but Pitt blocked the latter two options.


text:
Brother William Webster, nLC
I never imagined that my priestly formation would present some
of the obstacles that have been quite common over the
past three weeks, namely snails and mold. I am of
course referring to my work in some strawberry fields during
a period of formation entitled Month of Work, which is
an integral part of a Legionary´s training. The month
of work in the Novitiate has proven to be one
of the most effective tests of my will as well
as the intensity of my spiritual life. Picking strawberries
does not sound like difficult work, but it is indeed
monotonous. The effort lays a wonderful groundwork for my formation.
Since September of last year, when I began my
second year in the novitiate here in Germany, I have
been working on increasing my love for our Lord, who
is present in each of my neighbors. This is of
course the practical sign, for myself and every Christian, of
love for Christ: that one recognizes Christ in the least
of his neighbors, and treats him with the same love
as if he were Christ Himself. This love has
been put to test by the schedule with which we
live during the month of work, and the long hours
of monotonous work under the beating sun. This brings me
to another practical level of formation during the month of
work: union with the working world. As a future
priest, one must in a way be "Everyman" for all
Christians, too. All workers experience this tiredness and difficulty
in love towards their neighbor at some point in the
day. Daily agricultural work unites me with those thousands
of men and women who give their lives for the
nourishment of the world, and with those thousands who must
earn their daily bread through such strenuous work. I
have begun to appreciate more deeply the sacrifices of so
many men and women who "break their backs" for the
benefit of others- an essential aspect of Christian love.
On the field I can then unite myself interiorly to
Christ, ever-present in my soul and in the souls of
all Christians, in order to pray for these heroic, often
forgotten, men and women. Yes, truly the month of
work is a time in my priestly formation when I
have learned how to say, "Offer it up!" (August
13, 2003)
13, 2003)


text:
LAKEPORT -- The winner of the Business of the Quarter award will be announced at the Lakeport Main Street Association mixer Feb. 7 at 5:30 p.m. at Pieces Boutique.
Complimentary appetizers and water will be provided. There will be a no-host wine and beer bar.
Pieces Boutique is located at 155 N. Main St. in Lakeport. For more information, call Carol Hays at 263-8843.


text:
Moderators: Timko, Fritz, Solty, Booter, Blake_T, Frank Delicious
NOHalffastpull wrote:Hit my first for the year yesterday.
City Park, New Orleans, LA
Hole 11 with a new z Buzzzz
This was the first time all three of my children have been on the course, throwing with their old dad.
Nice early Father's Day present
inthedrift wrote:...That's a sweet tee sign...
Frank Delicious wrote:I hope you're in the 51 club so you're making some extra dough on these aces you're hitting all the time. That is assuming you're not playing alone.
Users browsing this forum: No registered users and 1 guest


text:
No. 8
The Texas Constitution defines marriage as between one man and one woman, but how will the state define "man" and "woman"?
Transgender marriage cases in Dallas and Houston could force the Texas Supreme Court — or even the U.S. Supreme Court — to ultimately decide the thorny issue.
In Houston, transgender widow Nikki Araguz has appealed a district judge's ruling denying her death benefits from her late husband, Thomas Araguz III, a volunteer firefighter who was killed in the line of duty in 2010.
The judge, Randy Clapp, granted summary judgment to Thomas Araguz's family, which filed a lawsuit alleging the couple's 2008 marriage is void because Nikki Araguz was born male, and Texas law prohibits same-sex marriage.
The Araguz family's argument relies heavily on a San Antonio appeals court's 1999 ruling in Littleton v. Prange, which found that gender is determined at birth and cannot be changed.
However, LGBT advocates say the Littleton ruling is unconstitutional, goes against medical science and isn't binding in other parts of the state, where it has not always been followed.
In Dallas, a district judge apparently reached the opposite conclusion from Clapp this November — denying a similar motion for summary judgment.
James Allan Scott, a transgender man, is seeking a divorce settlement from his wife of 13 years, Rebecca Louise Robertson. However, Robertson wants to have the marriage declared void because Scott was born a biological female.
District Judge Lori Chrisman denied Robertson's motion for summary judgment, which leaned heavily on Littleton. The judge provided no explanation for her ruling allowing the matter to proceed as a divorce, at least for now.
It's unclear whether Texas Attorney General Greg Abbott plans to intervene in the Dallas case. Abbott has intervened in same-sex divorce cases in Austin and Dallas, seeking to block them. But thus far he has stayed above the fray on transgender marriage, even though it presents overlapping issues.
After a transgender woman and a cisgender woman applied for a marriage license in 2010, the El Paso County clerk requested a ruling from Abbott about whether to grant it. But Abbott opted not to weigh in, with his office saying it would instead wait for court rulings in the Araguz case. The El Paso couple was later able to marry in San Antonio, where the county clerk went by Littleton v. Prange.
In response to the Araguz case, a bill was introduced in the Texas Legislature this year to ban transgender marriage. The bill would have removed proof of a sex change from the list of documents that can be used to obtain marriage licenses. Strongly opposed by LGBT advocates, it cleared a Senate committee but never made it to the floor.
Trans advocates said the bill also would have effectively prohibited the state from recognizing their transitioned status — or, who they are — for any purpose.
The problem for socially conservative lawmakers is, they can't have it both ways. Marriage is a fundamental right that courts have said can't be taken away from a person completely. So no matter what, Texas will be forced to allow a version of same-sex marriage.
Which is why some believe the cases could help undo the marriage amendment.
— John Wright
This article appeared in the Dallas Voice print edition December 30, 2011.


text:
Are Pacers Working Out Draft Prospects?
Thursday, June 23, 2005
Conrad Brunner
Q. I saw that the others teams in the NBA are already hosting players for pre-draft workouts. Are the Pacers doing this too? If so, who are they hosting? (From Alex in Montreal)
A. The Pacers are nearly done with their pre-draft workouts involving roughly 17 prospects, but they have chosen to keep those names private. Team President Larry Bird revealed Wednesday that shooting guards Francisco Garcia (Louisville), Luther Head (Illinois) and Rashad McCants (North Carolina) were among the players the Pacers have worked out, but no other names have been made public by the team.
There are two very different schools of thought when it comes to dissemination about pre-draft information. Some teams used the pre-draft workouts as a chance to generate fan interest and publicity and release not only the names of the players they bring in, but make them available for interviews with the local media. The teams with the top eight picks all have publicized their workouts. Of course, because they weren't in the playoffs, their primary opportunity to generate some local hype during the offseason is the draft.
Sitting in the middle range of the first round, the Pacers prefer not to offer any public indications of their intentions. As Bird said Wednesday, "We don't like a lot of our information out there." It's the way they've done business for years and, given their success despite disadvantageous position in the draft, isn't likely to change.
At hoopshype they have a list of who has worked out. By my count Isiah has had 68 players in for workouts in New York. Seems to me he's trying to work out everyone available.


text:
A search warrant served on the 800 block of Madrone Street in Eureka on Thursday turned up a small indoor marijuana grow operation, according to the Humboldt County Drug Task Force.
Lt. Wayne Hanson said about 40 marijuana plants, ranging from three to four feet, were discovered growing in an unattached garage next to the residence. A half pound of processed marijuana was also found inside the residence.
Hanson said resident Erica Fike, 24, was arrested on suspicion of marijuana cultivation and possession for sales and booked into the Humboldt County jail. Fike was not in possession of a medical marijuana card, Hanson said. The case remains under investigation.


text:
Hotel Tryp Valencia Feria
- Terms and facilities
- Useful information
- Location
- Opinions
Wake up, pay TV, AlterServices, WiFi, Pillow menu, and so on. Valencian cuisine at our restaurant achieves its highest expression. You can taste the most delicious rice and other specialties of Mediterranean cuisine. Our chef and his team bring you a restaurant menu with different gastronomic proposals for all palates, attending always the demands customer. Nice and modern, the restaurant turns into a warm place where you can enjoy the most varied cuisine, accompanied by excellent service. N/I Nice and modern Lobby area. N/I N/I N/I
Choose your room
Share it
Score based on 43 reviews
Average price per night for this hotel for the following weeks
|9/18/17 - 9/24/17
|9/25/17 - 10/1/17
|10/2/17 - 10/8/17
|10/9/17 - 10/15/17
Services and terms: Hotel Tryp Valencia Feria
Accommodation facilities
- Lift
- Bar/Café
- Business Centre
- Meetings Room
- Internet Centre
- Garden/Terrace
- Laundry
- People with reduced mobility access
- Non-smoker Rooms
- Parking
- Restaurant
- 24 hr Room Service
- Shops
Leisure facilities
- Gym
- Swimming Pool
Standard Room Services
- Satellite TV
- Hairdryer
- Telephone
- Television
Useful information: Hotel Tryp Valencia Feria
Other names for Hotel Tryp Valencia Feria:
Vora Fira
Vora Fira Valencia
Location: Hotel Tryp Valencia Feria
The hotel is located next to the exhibition centre Feria Valencia, at only 10 minutes by car/taxi away from the airport of Valencia. There is an excellent connection to the city centre by public transport and the metro station Benimàmet can be found at a walking distance of the hotel. 4 kms to city centre 4 kms to the nearest airport (valencia airport) 3 minute walk to the nearest metro station (benimamet / fira) Close to the station (benimamet / fira) 2 minute walk to the nearest bus stop 1 km to the nearest fair site (valencia) 8 km to the nearest beach


text:
By Jatin Thakkar and Soham Sarkhel
In a series that went up and down, Australia's continuous dominance over India (and despite periodic caginess against Sri Lanka) earned them their first ODI Tri-Series win in Australia after a gap of six years since it became rechristened as the CB Series. Australia's win can be heralded as their answer to the growing allusions of their fading supremacy in world cricket. Their perfect mix of youth and experience brought in boldness and composure in equal measure, and helped them vanquish the two World Cup finalists.
Here is a review of the series through the prism of Impact Index.
Shane Watson is the 20th-highest impact player in ODI history. There are just 3 players in ODI cricket today who have had a higher impact than him - Brett Lee, Jacques Kallis and MS Dhoni. True to this billing, Watson was the highest impact player of the series with his Series IMPACT of 4.75 (with an all-round IMPACT of over 1 in both batting and bowling). His inclusion in the latter stages of the tournament (after being injury-free) proved to be a turning point for the Aussies as suggested by his performances in the 1st and 3rd final which earned him Series Defining status. It should also not be forgotten that Watson captained Australia for two matches in the absence of Michael Clarke and led them to victories in both of them and eventually garnered a captaincy impact greater than that of Clarke's.
Michael Clarke was the second-highest impact player in the series for Australia and was incidentally also the highest impact batsman. Although his century in the 2nd final came in a lost cause, he ensured that he chipped in throughout the tournament to provide crucial support in the middle order. His failure rate of 17% was also the lowest amongst all the players in the entire tournament. To complement the experience he brought to the middle-order was his ability to absorb pressure – he faced pressure 5 times in the series when he came out to bat, and successfully absorbed it 4 times. Despite having played just 5 and 6 matches respectively, both Watson and Clarke ensured that the Australian campaign never went off-the-rails in the series.
For David Hussey, this series showcased his mettle as a masterful ODI player for the first time in the international circuit – as he fulfilled a great deal of the promise he had shown in the Australian domestic league. He played a crucial role in all the 11 matches for Australia to rank as the third-highest impact player in the tournament with an all-round impact in the tournament. His bowling performance in the 1st final also earned him a Series Defining bonus. Hussey also had the highest Strike Rate IMPACT in the tournament (though conventionally, there were four others ahead of him when it came to strike rate) and absorbed pressure 4 times for Australia while batting.
On a Series Impact scale Clint McKay was the highest impact bowler on the table. His series tally of 15 wickets was the highest for any bowler and his haul of 5-28 in the third final also earned him a Series Defining bonus and Australia their tournament victory.
Brett Lee was the 5th highest-impact bowler in the tournament and was amongst the three highest impact Pressure Building bowlers in the series behind Watson and Hilfenhaus.
Overall, Australia was well-served by the seniors as well as youngsters like McKay, Warner (2nd highest impact batsman in the tournament) and Wade, who delivered crucial performances. It is also to be noted that David Warner was the only batsman to have a Series Defining performance in the tournament due to his back-to-back centuries in the 1st and 2nd final, a feat auguring well for Australia's future.
For Sri Lanka, Kumar Sangakkara had the highest Series Impact of 2.83. In almost all the innings he played in, he played second fiddle to Dilshan, Jayawardene and Chandimal and was instrumental in the middle overs for the Lankans. His Partnership Building IMPACT was the third-highest amongst his Lankan teammates, a quality that lends to Sri Lankan cricket its current stature of fighters.
Tillakaratne Dilshan's
first series after he stepped down as the captain also proved to be a huge success for him as he emerged as his team's highest impact batsman. His knock of 106 runs in the 2nd final also got it a Big Match stature and stretched the tournament into the third final. His starts with Mahela Jayawardene continuously throughout the series at the top proved to be very beneficial for Sri Lanka's strong batting in the later part of the tournament. His Partnership Building Impact was the third-best in the entire tournament, underlining that contribution. He got the Man-of-the-Series award – a somewhat bizarre choice however, given how many players had a higher impact than him (12, if minimum matches are 4!).
One of Sri Lanka's biggest finds of the tournament was no-longer rookie Dinesh Chandimal. He was the 8th highest impact batsman in the tournament and the 2nd highest for Sri Lanka. Chandimal had an impact in all the batting parameters; he particularly excelled in absorbing pressure without letting it affect his pace of scoring (Strike Rate IMPACT). His partnership building ability as well as his ability to chase suggested a player who has confidently found his feet and looks set to go to the next level.
Mahela Jayawardene's decision to put himself up the order was a bold and rewarding move. His natural attacking game, previously inhibited by the responsibility of holding the middle-order together, was freed up and it brought in good results. His first three matches as a middle order batsman fetched him a Batting Impact of 1.32 whereas his last eight matches as an opener was a considerably superior 2.13. In fact, his performance as an opener was a huge improvement from his Career Batting IMPACT of 1.65, and it does make one wonder if his going up the order could have the same impact Tendulkar's elevation to the same spot did in 1994 for India.
Together, these seniors, alongside young Chandimal, strengthened Sri Lanka's batting as the tournament progressed into its latter stages.
Surprisingly for Sri Lanka, their highest impact bowler was the unassuming Farveez Maharoof. His Bowling Impact of 2.40 in the 7 matches that he played was the highest for any Lankan bowler. His ability to break partnerships was identified by his Partnership Breaking IMPACT which was the highest amongst all the bowlers in this tournament. His failure rate of 28% also shows his consistency and was the lowest for any Sri Lankan bowler in this entire tournament.
Malinga was off-colour in the tournament – especially in light of his status as Sri Lanka's second-highest impact bowler in ODI history (after Muralitharan, of course, but ahead of Vaas). Malinga registered the worst Economy IMPACT (ability to bowl tight) in the tournament. His performance against the Kohli-led Indian chase in the 11th match of the series being his worst. His failure rate as a bowler in the tournament was 45% (against his career failure rate of 37%).
Rangana Herath
(9 matches) had the highest Economy IMPACT in the tournament only behind Watson (5 matches) but had a very low impact when it came to taking wickets, a case similar to that of Doherty's (3rd highest Economy IMPACT in the tournament in his 11 matches). While containing runs has become a tougher job since T20 cricket began affecting the 50-overs version too, the highest impact bowlers in ODI cricket have always been the wicket-takers.
Angelo Mathews continued his brilliant show as an all-rounder (both his Batting and Bowling Impact was over 1 in the tournament) and held Sri Lanka together in the matches he played in. David Hussey, Watson, Pathan and Mathews were the four pivotal players for their respective teams as they were the only four genuine all-round IMPACT players in the tournament.
India's story in the tournament meanwhile revolved around the successes of Virat Kohli and Gautam Gambhir. Unsurprisingly both were India's highest-impact batsmen in the tournament. Both of them delivered very high Chasing IMPACT numbers in the series with Kohli leading the way with his spellbinding chase against the Lankans at Hobart.
Irfan Pathan's return in the Indian squad could not have been better as he was India's highest-impact player in the tournament. In a series in which the Indian team management at every step tried to drill in their rotation theory, it is odd that Pathan was handed out only 4 matches in the tournament. He was also the only Indian player to have an all-round Impact (both Batting and Bowling Impact over 1) in the series. Pathan's stature as India's 8th highest impact player in the ODI history coupled with his failure rate of just 23% as an all-rounder is well magnified by his performance in the recently concluded series and just goes on to show the crucial role he could play, if given ample opportunities.
MS Dhoni's stature as India's highest impact ODI player in history was bolstered yet again through his match-winning, and tying, performances against both Australia and Sri Lanka. Interestingly though, contrary to Dhoni's explosive reputation in ODI cricket, he actually had the second-lowest Strike Rate IMPACT amongst Indian batsmen in the series – after Tendulkar.
Umesh Yadav was the biggest disappointment in the bowling department considering the amount of promise he showed during the test series. In the 6 matches in which he played his overall Bowling Impact was less than 1 and was the worst seamer in the entire tournament. Ravindra Jadeja however gave him close competition and managed to go past him on the Series Impact charts only due to his otherwise dismal Batting Impact of 0.61. Jadeja's all-round credentials also suffered a huge blow as he failed to cross an IMPACT of 1 in both batting and bowling in the entire series. His failure rate of 72% (the highest amongst the bowlers in the series) suggests an inadequacy on foreign pitches.
The biggest disappointment in the entire Indian batting line up had to be the consistent failures of Sachin Tendulkar and his opening partner Virender Sehwag. Tendulkar's Batting Impact of 1.03 was the second-worst only to that of Sehwag's 0.63. Their failures put enormous pressure on the Indian middle order. Tendulkar's failure was especially shocking as he was India's mainstay the last time India won the CB series in 2008 - his Batting Impact in the 2008 CB Series was a whopping 2.91 as compared to this time's 1.03, a drop of 65%.
Of all the performances that had an IMPACT of above 5 in the series, Australia had the maximum with 9 such performances, Sri Lanka 6 and India 3. Australia's best individual performance was Warner's in the 1st Final (Batting IMPACT 6.44), Sri Lanka's best came from Maharoof (Bowling IMPACT 5.33) in the 6th match against Australia when the latter were all-out for 158 and he in turn was closely followed by Chandimal (Batting 5.17) in the last league match where Sri Lanka were in a must-win situation against Australia. India's best performance came from Kohli (Batting IMPACT 6.96) in India's last league match under similar pressure. From the above instances it can be said that the youngsters have truly come into their own in all the three teams.
Overall, Australia delivered a Team Tournament IMPACT of 2.17 as compared to Sri Lanka's 2.02 and India's 1.78. Australia's seniors topped the IMPACT chart and ensured that the youngsters in the team got enough support to win the trophy for their team.
For more information, please go to www.impactindexcricket.com
By Jatin Thakkar and Soham Sarkhel


text:
The Pittsburgh Penguins have some defensive depth. And they're going to need it.
Paul Martin, who has rebounded dramatically from a brutal 2011-12 and reestablished himself as a vital component of Pittsburgh's blue line, will miss six weeks with a broken bone in his "upper body," according to coach Dan Bylsma. A shot hit him in the hand/wrist on Thursday against the Winnipeg Jets.
That puts him out for the duration of the regular season and the first round of the postseason. Pittsburgh is on a 14-game win streak, 27-8-0 overall and leads the Eastern Conference by seven points.
Ironically, Martin's injury was lost in the shuffle on Saturday morning amid news that star winger Jarome Iginla, acquired earlier this week from the Calgary Flames, would play later in the day against the New York Islanders.
Martin plays tougher even-strength minutes than any other Pittsburgh defenseman, comprises half of a shutdown pairing with Brooks Orpik and is second on the team in ice time, trailing only Norris Trophy candidate Kris Letang. He also kills penalties and leads the second power-play unit.
Letang, coincidentally, is currently out with a broken toe, leaving Pittsburgh with a top six of Orpik, Matt Niskanen, Simon Despres, Mark Eaton, Douglas Murray and Robert Bortuzzo. Once Letang returns, he's "a good option" to play with Orpik, Bylsma said. Niskanen could also see more responsibility on the power play, particularly while Letang recovers.
Despres, a rookie, is most likely to see his role increase—his skillset is similar to Martin's, and he has improved throughout the season. As the only Pittsburgh defenseman who doesn't have to clear waivers, Despres was briefly demoted to the AHL last week to create space for Murray, a physical, slow-footed defenseman best suited for third-pairing minutes.


text:
The U.S. Energy Information Administration (EIA) released the early release version of its 2013 Annual Energy Outlook (AEO2013), which includes projections for U.S. energy markets through 2040 under reference case assumptions. Projections under the reference case include only current laws and policies. The full AEO, which includes side cases, will be available in spring 2013.
The AEO2013 projects strong growth in natural gas production, led by continued development of shale resources. Despite growth in natural gas consumption, AEO2013 projects that the United States will become a net exporter of natural gas by the year 2020—two years earlier and with greater volumes of U.S. natural gas exports than was projected in the Annual Energy Outlook 2012.
Domestic natural gas consumption grows by about 21 percent from 2011 to 2040. Consumption grows most in the electric power and industrial sectors, which are better positioned to benefit from relatively low natural gas prices. Increased use of liquefied natural gas (LNG) for heavy-duty vehicles contributes to growth of natural gas use in the transportation sector, which represents 6 percent of natural gas consumption in 2040, compared with 3 percent in 2011.
The Henry Hub day-ahead price registered an overall decrease for the week, dropping 32 cents per MMBtu through Tuesday before regaining some ground yesterday to close the week at $3.41 per MMBtu, down 7.8 percent. Generally higher-than-average temperatures in many locations helped to lower prices early in the report week, with prices finishing the week higher in some locations ahead of forecasts of colder weather.
At the NYMEX, the January 2013 contract ended the week lower, dropping from $3.801 per MMBtu last Wednesday to $3.700 per MMBtu yesterday, a decrease of 10.1 cents per MMBtu. Prices fell for much of the report week before regaining more than 16 cents per MMBtu yesterday, finishing the week down 2.7 percent. The 12-Month Strip (average of January 2013 to December 2013 contracts) closed yesterday at $3.823 per MMBtu, down 3.2 cents per MMBtu (0.8 percent) for the week.
Certain locations in the Northeast saw prices initially trending significantly lower as very warm weather late in the report week followed seasonally colder temperatures. Prices rebounded toward the end of the week ahead of a return to colder weather. For example, at the Algonquin Citygate trading point (for delivery into Boston), spot prices started the report week at $9.78 per MMBtu and rose 20 cents per MMBtu on Thursday, but dropped to $4.76 per MMBtu on Monday (as temperatures approached 60 degrees) before rebounding sharply on Tuesday and again yesterday, closing at $9.43 per MMBtu (down 3.6 percent for the week). Similarly, prices at the Transcontinental Pipeline's Zone 6 trading point (serving New York City markets), which began the week at $5.40 per MMBtu, fell nearly $1.00 per MMBtu on Thursday, and continued a steady decline through Tuesday before regaining ground yesterday, finishing the report week at $4.34 per MMBtu (down 19.6 percent).
Total consumption for the report week registered an overall decrease, reflecting lower demand across all sectors. According to estimates from BENTEK Energy LLC (Bentek), domestic natural gas consumption fell by 11.9 percent from last week, driven by a decrease of 23.5 percent in residential/commercial sector consumption. Industrial sector consumption finished the week down 2.1 percent, while power sector consumption dipped modestly (down 0.2 percent). Residential/commercial sector consumption trailed levels for the same week last year by a considerable margin (24.7 percent).
Total supply was unchanged for the week, largely reflecting essentially flat dry natural gas production. According to Bentek estimates, domestic weekly dry natural gas production declined 0.6 percent from the previous week's volumes (while remaining 0.5 percent higher than the same period last year). Imports from Canada rose by 7.4 percent, with all regions showing increased shipments, particularly the Midwest, up 25.1 percent. For the week, imports from Canada stand moderately below year-ago volumes (down 5.2 percent). While liquefied natural gas (LNG) sendout rose 25.3 percent over last week, sendout volumes remain well below (62.6 percent) year-ago levels.
Working natural gas in storage decreased to 3,804 Bcf as of Friday, November 30, according to EIA's WNGSR. This represents an implied net withdrawal of 73 Bcf from the previous week, the third and largest withdrawal for this heating season. This week's net withdrawal was 22 Bcf below the 5-year (2007-2011) average net withdrawal of 51 Bcf, and 59 Bcf below last year's injection of 14 Bcf. Inventories are currently 33 Bcf (0.9 percent) less than last year at this time and 168 Bcf (4.6 percent) greater than the 5-year average.
All three storage regions posted decreases this week. Inventories in the East, West, and Producing regions decreased by 56 Bcf (the 5-year average net withdrawal is 35 Bcf), 3 Bcf (the 5-year average net withdrawal is 7 Bcf), and 14 Bcf (the 5-year average net withdrawal is 9 Bcf), respectively. In the Producing region, working natural gas inventories increased 1 Bcf (0.3 percent) in salt cavern facilities and decreased 13 Bcf (1.3 percent) in nonsalt cavern facilities.
Temperatures during the storage report week were 0.4 degree cooler than the 30-year normal temperature and 5.9 degrees cooler than the same period last year. Temperatures in the Lower 48 states averaged 41.7 degrees, compared to 47.6 last year and the 30-year normal of 42.1 degrees. While slightly below normal overall, temperatures varied somewhat across Census divisions. In the South, the South Atlantic and East South Central Census divisions were relatively cool, averaging 4.3 and 3.9 degrees, respectively, cooler than the 30-year normal. In the West, the Mountain and Pacific Census divisions were particularly warm, averaging 6.9 and 4.1 degrees warmer than the 30-year normal. Heating degree-days nationwide were 1.2 percent above normal and 32.3 percent above last year.


text:
Drakes Bay Oyster Co., provider of one-third of California's oysters, shut down its retail operations Thursday in a goodbye ceremony attended by hundreds who raised the salty delicacies in a final toast on the sand spit by the water.
The Inverness company's 40-year lease at the Point Reyes National Seashore has expired. Owners Kevin and Nancy Lunny fought for 19 months to stay open, but held the closing event on Thursday after a series of legal appeals failed.
"Today would have been one of the most difficult days of our lives, but you made it brighter," Kevin Lunny told the crowd of about 250 gathered behind the oyster shack on Sir Francis Drake Boulevard. The morning had been overcast and chilly, but just before he spoke, the sun came out.
While the retail operations have shut down, the company will be able to keep harvesting oysters for at least another 30 days in the wake of an agreement reached with the National Park Service last week. A group of restaurants and other businesses that purchase the oysters is pursuing a lawsuit, and forged the temporary agreement.
That group's request for an injunction will likely be heard Sept. 9. The lawsuit by the Bay Area businesses that depend on the continued operation of the company contends that the Interior Department didn't follow the law when it made its decision to close the oyster farm
"Our chances with the case are slim," acknowledged Jeff Creque of the Alliance for Local Sustainable Agriculture, speaking on behalf of the group behind the lawsuit. Nevertheless, a stream of well-wishers encouraged the Lunnys with handshakes, hugs and back pats after the event's formal conclusion, urging, "Keep fighting."
Asked if the battle was over, Kevin Lunny said, "We're still evaluating that with our legal team. We're hoping, but not so sure. It's an emotional roller coaster."
Amy Trainer, executive director of Environmental Action Committee of West Marin, which opposes the oyster farm, said, "I think the lawsuit has absolutely no merit. The plaintiffs have no standing. I think this will readily be dismissed when it is finally heard. I do not believe it will delay the inevitable and impending closure of Drakes Bay.
"I think from their perspective it's appropriate to have a final celebration," the environmentalist said of Thursday's event. "The company has been in operation now 20 months past its lease expiration and they fought hard and weren't successful."
Drakes Bay produced as many as 100,000 oysters a day during busy times, according to Lunny.
About 20 employees standing behind the speakers at the event sported blue sweatshirts with the Drakes Bay logo. The retail shop and cannery facilities shut down Thursday, eliminating the jobs of about half the company's 30 employees. The rest are involved in the harvesting, processing and delivery operations.
"I'd like to propose a toast," Kevin Lunny said after employees circulated through the crowd handing out fresh oysters.
Taking his place before the group, Jorge Mata, the company's production manager and a 30-year employee, raised an oyster and the group tipped their oysters into their mouths.
"This is the only oyster cannery in California. Other states are clamoring to set their estuaries up, but the National Park Service says (to Drakes Bay), 'Get out of there,'" said Phyllis Faber, co-founder of the Marin Agricultural Land Trust, who blasted the Park Service for its action.
The oyster farm is in an area of Point Reyes National Seashore designated as a marine wilderness, free of commercial activity, by Congress in 1976. The U.S. Department of the Interior said in 2005 that it would not renew Drakes Bay's 40-year lease because it wants to include the 1,100-acre property in the marine wilderness area.
Drakes Bay has existed, though not under that name, for some 100 years. Lunny took over the lease in 2004 and, according to then-U.S. Interior Secretary Ken Salazar, was informed "no new permit would be issued" after the lease expired.
Last month, the U.S. Supreme Court declined to review an appeal from Drakes Bay, eliminating its legal options to keep the oyster farm open while litigation continues.
"I have bought oysters from this farm for 45 years," said Anne Sands of Dogtown. "This is a tragedy.
"It isn't over. We're going to keep fighting this," Sands said. "Environmentalists need to work with ranchers to make the area sustainable. I am an environmentalist. I was a freshwater systems environmental consultant for years. This is a perfect example of how agriculture and open space can work together."
"This is a disaster," said Dawn Wagner, who drove to the event with husband Jason Regan and son Luca, 10. "We are living off nature here. I doubt (President) Roosevelt would have allowed this to happen. It should be reversed.
"The three of us can eat three dozen oysters in one sitting," Wagner said. "We loved coming here and buying a dozen oysters for $12 instead of the $25 it would cost in a restaurant, and sitting down outside at the picnic tables and eating them right in front of the water."


text:
Outdoor Concepts, Inc. or commonly known as OCI was formed in 1997. They formed the company with the high-end consumer in mind. They developed a line of entertainment islands that were well suited to meet the needs of their grilling aficionado customer base. In 1999 they moved into their current 20,000 square foot corporate headquarters in Westminster, California. Their products are sold over a wide network of distributors and dealers throughout North America. Available at AppliancesConnection
Imagine how pleased your guests will be when you serve meals prepared on OCI commercial grade grills. Made in the USA from the highest quality materials, OCI helps make your outdoor gatherings the best ever.
Their OCI Elite Series Grills are designed and manufactured to meet the standards of today's grilling chefs. They want to make sure that at your next gathering you spend more time with your guests and less time worrying about how your rib eye steak is going to turn out.
Specfications Material:
Stainless Steel Cooking Area:
927 Sq. In. Stainless Steel Burners:
2 x 28,000 BTU Sear Zone Ceramic Burner:
1 x 23,000 BTU Ceramic Infra-Red Rotisserie Burner:
1 x 15,000 BTU Stainless Steel Smoker Burner:
1 x 5,000 BTU Stainless Steel Radiants:
Yes Stainless Steel Tubes:
Yes Ignition:
9-Volt Battery Grill Grates:
Heavy Duty 3/8" Stainless Steel Warming Rack:
Removable Rotis Motor:
Yes with 50 Watt Halogen Light Stainless Steel Drip Pan:
Yes Insulated Grill Lid:
Yes Metal Knobs:
Yes Dimensions and Weights Width:
36" Height:
21 3/4" Depth:
27 1/2" Shipping Weight:
250 Lbs
Be the first to ask a questionAsk A Question
Be the first to review this productWrite A Review
- Brand:OCI
- Stock Id:142534
- Product Number:OCIE36BQRN
- Width:36"
- Height:21 3/4"
- Depth:27 1/2"
- Casters:No
- Electronic Ignition:Yes
- Smoking Tray:No
- Cooking Grates Material:Stainless Steel
- Set 1 QTY:2
- Set 1 Output:28000
- Set 2 QTY:1
- Set 2 Output:23000
- Set 3 QTY:1
- Set 3 Output:15000
- Set 4 QTY:1
- Set 4 Output:5000
- Weight:250.00 lbs


text:
For a great selection of action figures and collectibles, check out BigBadToyStore.com, BriansToys.com, ToyWiz.com, SmallJoes.com, PastGenerationToys.com, Urban-Collector.com, ZoloWorld.com, MonkeyDepot.com, HobbyLinkJapan.com, and Sekaido.com.
For a great selection of pop culture t-shirts and apparel, check out TShirtGurus.com and 80sTees.com.
One of the most powerful robots from Crest Industrial Enterprises, the CREST ASSAULT TYPE VERSION makes a dynamic appearance in the opening movie of Silent Line Series with Impact. This version includes newly sculpted parts on the legs, booster engines, and stealth equipment, along with the unit's heavy armor and deadly weapons. The new parts make the Assault Type Version unique, but can also be used on any Variable Infinity Armored Core.
Standing almost 8 ½ inches tall (1/72nd scale), the Crest Assault Type has 20 points of articulation. AC kits require easy snap fit assembly with included pictorial assembly instructions and do not need to be painted.
The CREST ASSAULT TYPE VERSION is scheduled for release this October priced at a SRP of $44.99. Check out our photo gallery below for tons of new images.


text:
"Develop the mind that rests on no thing whatsoever."
(perhaps someone could give a better translation).
Is this verse the teaching of non abiding mind? when one has no mind, how could it abide?
what is the conventional teaching about non abiding mind? is this the same as...
"the Budda takes his stand in no thing whatsoever."
Thank you for any advice you can give on the subject of non abiding mind.
White Lotus.


text:
Kelly Fuels is unifying its nine stores under a single retail brand and upping its investment in foodservice. By Erin Rigik, Associate Editor. Kelly Fuels Inc. is moving full steam ahead in 2012, rebranding its nine Michigan c-stores under the Kelly Express Mart brand, and giving its locations a full facelift with an express train
All Aboard the Kelly Express Mart
June 11, 2012 Erin Rigik Del Conte : 0 Comments