text:
Right now, your transaction log backups are set up to run every 15 minutes, every hour, or maybe every few hours.
It's time for a reality check. Figure out what internal customer owns the data inside the database, and walk into their office. Ask them how much data they're comfortable losing.
You're probably going to have to repeat the question a couple of times because they won't believe these words are coming out of your mouth. After they eventually recover, they'll blurt out words like "NONE" and "ZERO" and "ZOMG". Give them a quick overview of how much it costs to have a no-data-loss system – typically in the millions of dollars – and then ask for another answer.
They're going to ask for a list of options and their costs. Forget the fine-grained details for now – let's just assume one of your solutions involves transaction log backups.
Is it more expensive to run your log backups:
- A – Every hour
- B – Every 15 minutes
- C – Every 5 minutes
- D – Every minute
It's a trick question – they all cost the same.
Nope – it actually means less overhead. To keep the numbers easy, let's say you generate 60GB of transaction log data per hour. Would you rather back up 1GB per minute in small chunks, or kick the server in the junk every hour trying to back up 60GB all at once? The users would definitely notice the latter – the server will slow to a crawl while it handles that firehose of log data for a sustained period.
Yes, but if you think you're really going to manually restore log backups through the GUI, one at a time, you haven't been through a real mission-critical crash. Long before disaster strikes, you need to be familiar with a script-based method to automatically restore all of the log files in a directory. Test it, get comfortable with it, and then when the outage hits, you can let your script restore everything ASAP, no clicks required.
If you have too many databases and your jobs can't keep up, it's time to start breaking up the log backups into multiple jobs. Some of my clients use two jobs, for example – one to back up all odd-numbered databases by the database ID in sys.databases, and another one to back up all the evens. The log backups don't stress out their servers by any means, and users don't notice the impact of two simultaneous log backups in two different databases.
I'm just as serious as you were when you randomly picked 15 minutes or 1 hour as the log backup schedule. The point is that it's not for the geeks to decide – it's for the customer to decide. Ask your business user about the business needs for their data, and then give them a menu of options to meet that goal.
You think they're all going to insist that all data is mission-critical, but you'd be surprised. Once they see the costs involved with log shipping, AlwaysOn Availability Groups, SAN replication, and so forth, they're able to make better informed decisions about which data really is priceless, and which data we could really re-enter at minimal cost.
But until you ask them this question, they assume you're never going to lose data.
120 Comments. Leave new
What happen with all "VSS" freezing points ? Will this impact performance ?
What happen if I got 200 db´s on one instance in one job?
Thanks for advice, Magnus
Magnus – typically VSS freeze points are only used for full backups, not log backups. I would advise against using VSS for log backups.
Do you have suggestions on helping "BUT MORE LOG BACKUPS MEAN MORE FILES!". I have tried to build an automated restore routine based on backups in a folder and have failed. Anything out there you would recommend looking at?
Garry – sure, in our 6 Month DBA Training Plan emails ( https://www.brentozar.com/go/needs ) we talk about this one from MSSQLTips: http://www.mssqltips.com/sqlservertip/1584/auto-generate-sql-server-restore-script-from-backup-files-in-a-directory/
I like the script you reference and can make it work for most things. But what if you have a directory full of FULL, DIFF and TLog files for multiple databases that are not named easily to identify. Have you seen a routine that will read the file information for each file and build a restore sequence based on the results?
No, fix the file names.
The easiest way I know of to fix the file names is to use Ola Hallengren's maintenance scripts.
Just to clarify – reading the file information for each file is an incredibly bad idea due to taking additional time when you can least afford it.
Everytime I take a backup, the sql agent job outputs the restore script for each db backed up automatically and we store the scripts on the backup server. I'll look for the link where I got the idea from. That way all your restore scripts are ready to go for each server.
You can dump RESTORE WITH HEADERONLY together with fileinfo to a temptable and from there generate restorescripts…
Easiest option is to setup your backups to go to different sub folders for each database, so you have sub folders for FULL, DIFF or LOG etc. for each one – makes it clearer what needs to be restored and in what order.
Gary – that's an interesting approach. Do you have a script to automate the restores by folder? Or are you talking about doing human intervention for restores?
Automatical scripts are fine, but (at least in SQL 2014) you could use the Management Studio too.
It lets you select one ore more backup files at once in the Add-Backup-Media dialog. Furthermore it reads the backup headers and uses only the necessary files, even if you select more. Also it supports the restore-to-point-in-time (something that is a little bit harder with the scripts).
If you have different folders for FULL / DIFF / LOG, you have to open the Add-Media-dialog three times (once for every directory) and multiselect the files to restore (theoretical you could press Ctrl-A to select all but it could need some time to read the headers from all LOG-Backups of the last month if you do a one-minute backup).
Thomas – yeah, it's just usually painful when you talk about restoring dozens, hundreds, or thousands of databases through the GUI.
You can set up your primary database as the target for Log Shipping and let Log Shipping create the jobs you are talking about for you. After inital set up, bring your databases on-line as the primary. The Log Shipping jobs will still work — just restore with NORESTORE option and have your TRN's in the same directory you specified when setting up LS.
Works like a charm!
I have found sp_RestoreScriptGenie to be incredibly useful. Note that this script assumes that msdb is still available and that the backups are in their original location at the time of backup which limits its utility in some situations.
Hi, Garry, I have a script solution for you at SQL PASS 2014 Summit.
Personally I prefer to regenerate a backup script with every logfile taken. This is then moved, along with the logfile, to a dedicated backup storage server. Actually having a file ready with the restore that potentially only needs editing with a STOP AT time is very nice when things go pecs up. I would post the one I use here – but at c.380 lines it's little long for the comment box I think.
I'd need to find somewhere to upload and post the link if anyone's interested?
Sure, consider Github or Pastebin.
I'm interested. Do you have a link?
Interesting view, and I do think these days that an automated restore routine is important, it's also potentially an issue in alerting/monitoring if you have logs every minute. You need to know if you have issues, like a full drive, but you also don't want to be inundated with alerts. Potentially that would lead someone to turn off alerts for the time it might take them to respond, and not turn them on.
I also think there could be an issue here with the size of msdb and logging activity if you're a person that backs a full once a week since you need to keep these log files back to the earliest full.
I'm not sure I agree, but I'm not sure I disagree. Thanks, Brent, for something to think about.
Steve – rather than alerting on the jobs, I typically want to flip it around and say, "Give me an alert when the number of databases with >2 minutes of data loss exposure is >0." That way I have a little bit of flex time, and I only get one alert.
Any one-off Transaction log backup failure is not that critical when next one picks up with the backup-chain not broken. I have a script monitoring solution from CMS to show you at SQL PASS Summit 2014 that you can schedule at any interval for notification down to specific db level.
If you backup transaction log at every minute, you sure not want to be paged for every minute backup failure and on every database. If the next minute the backup transaction log is successful, that last one wasn't immediately critical. You might want to look into the root cause when dawn breaks. I got a a solution with CMS and using powershell nd T-SQL to manage enterprise databases to show you at SQL PASS Summit 2014 if I get there.
A question & statement of immeasurable value:
"Ask your business user about the business needs for their data…"
"But until you ask them this question, they assume you're never going to lose data."
You mention the cost of various replication strategies, and how the cost can inform decisions about the value of data. Very good advice. The cost of a given replication strategy can extend to significant changes in hardware, data layout, batch workload scheduling, and even application level code/design. Until all the pieces are put together, its hard to know.
Sometimes discussions of data business value to shape recovery objectives can be tough – my people skills can be stretched in those discussions. But I greatly prefer having those discussions before a data loss crisis – or before a performance crisis in which replication is a contributor – rather than during a crisis, or even in post-mortem.
On the "BUT MORE LOG BACKUPS MEAN MORE FILES!" and "if you think you're really going to manually restore log backups through the GUI, one at a time", here is what we are currently doing:
Perform a full backup of the database overnight to a device.
Backup log files throughout the day, appending to the backup device holding last night's full database backup.
So, if a restore to a point in time is required, through the SSMS GUI, it is easy to view and select any or all log backups to restore through (up to the desired point in time). We don't have to pull up each log backup file through the GUI.
Of note, we are not dealing with extremely large databases. Sizes range from MB's to 250 GB.
Since "BUT MORE LOG BACKUPS MEAN MORE FILES!" implies to me that each log backup (hourly, minutely, etc.) is going to a unique file name, I am wondering if this is the recommended method (as opposed to our current method) for log backups.
Hope I'm clear on this.
Thanks Brent and everyone there! We check out brentozar.com daily.
Pat – two big problems with that. First, if you want to sweep the backup files off to tape, it's much more challenging if they're currently in use. Second, if something goes wrong during a backup and the file becomes corrupt, all of your backups can be corrupt.
Hi, Pat, the backup info is in the MSDB that can be queried (and restore script automatically generated, saved as file) from CMS and using Pwershell and T-SQL for the enterprise database management of hundreds of SQL Servers including notification and audit. That is what I plan to show at SQL PASS Summit 2014.
This is the short end of SQL Server because there is no centralized backup catalog like Oracle RMAN can use catalog. Maybe SQL Server can improve on this in the future in order to be a big enterprise player. In the meantime, CMS and scripts will do for enterprise. Don't pay for expensive backup software.
Good food for thought, but there is a considerable cost/benefit, risk/reward analysis I would have to do to change my hourly schedule now, to include asking the business. I realize there's always a risk to having a failure – even with clusters and high-tech SANs, but the risk is so minuscule (once in my 15-year career).
We only put the local backups to tape once/week (keeping in mind the backup drive is presented from a SAN at another location) so we have bigger fish to fry in the near term 😉
Allen – you must be a lucky charm! How often have you had car accidents, and have you thought about canceling your car insurance? No sense in paying for it if you don't need it.
Life insurance too – might as well cancel that, because you've never died, right?
Have a good one. 😉
I would ask myself how much data would I like to loose, and then ask the data owner the same question. It's like the question about physically separate the datafiles from the logfiles.
Is it a Performance reason? Yes, but primarly for disaster recovery.
Hey Brent, you keep up the good work! This couldn't be stressed less.
Would you consider synchronous mirroring/AG a zero-loss solution?
Tobi – if a user accidentally deletes or updates something, how would you recover?
Make a tail log backup and use point-in-time restore. I don't need 1min backup for that.
Interesting approach. Have you had to do a restore to fix a single deleted record with that, and how long did it take?
Ah I see. You propose log-shipping with lag? That is indeed a nicer solution.
HA/DR does not replace backup. You can recover logical corruption much faster and precise with backups.
Hi Brent, thanks for that article. I have to say that the 1 hour log backup scheduling has been picked up randomly here too. Or at least we inherit from it. My biggest concern here is that TSM (IBM Tivoli) is used to perform backups in our environment and secure them and ship the tapes off-site, etc… but we do not have any control of it. We can ask for a restore but I doubt I can ask for something like "can you please take last night full + the 600 log backups that were taken after it?" to the TSM admin. But granted I am sure TSM can be automated too but I doubt any one in charge knows how to do that…
Benjamin, where I work, our Tivoli solution has a nice web-app front end that resembles a folder structure. It's not practically more difficult to select 600 files, than it is to select 6.
Before they gave us R_W access, we had Read access, and could at least give them a screenshot of where the files live.
Benjamin, I am one of those TSM admins. There is a GUI that should make your recovery very user-friendly. It should even be available from the Start menu.
At some point I should have a PowerShell script to drive the process from a CLI perspective. But the TSM TDP for SQL Server has a fairly straight forward CLI command 'tdpsqlc' that fairly closely mimics the native SQL Server CLI commands for performing a restore. To be practical with any significant quantity of log files a script is really needed.
Hi Brent.
As usually, nice post.
I'm facing a server with more than 150 DDBBs, all of them in full recovery model.
I have developed an T-SQL that checks the actual size used by each db and launch the log backup based on the size of the log.
What do you think about this approach?
It allows us to have more backups for the heavy used DBs and less files and backups for the rest.
So in some way I'm measuring the amount of data we can loose in Mb, not in time.
Greetings from Spain and congratulations for your site, its a great resource for the SQL Server mere mortals.
Jorge – thanks, glad you like the site.
I would ask the business if they're okay with it, and if they're okay with databases being out of sync when you restore. Databases will be at different times, and that's usually not okay for the business.
On the "BUT MORE LOG BACKUPS MEAN MORE FILES!", in a log shipping scenerio I find that the restore process takes 20-30 seconds to process even the smallest TRN file that has no actual data changes, but only the relevant markers. So a restore process takes 2 minutes every hour even if there is no activity in the DB during that hour. If my math is correct, that would work out to 30 minutes of "restores" every hour, even when there's nothing to restore. This pretty much makes the Warehouse unusable if we prevent user connections while performing the restores.
Al – if restoring a tiny log takes 20-30 seconds, you've got a problem, and you need to get that problem fixed.
I was waiting to see this post drop since the Dell backup webcast! Good stuff. Although I have to ask…are there any figures, or example tests with figures available to support the first assertion, saying that there is less overhead backing up more often? Not sure what the best measurement of that would be…even just cumulative job time over an hour with either 4 backups at 15 min or 60 backups at 1min, on a busy system. I get the idea that one big long log backup is more likely noticeable to the users than a constant stream of small ones, that makes sense, just wondering if people have done the testing…so I don't have to ;)…to establish how exactly the performance changes as you change the increment…and in which direction!
Of course, your point about RPO is well taken. Luckily our business has sometimes proposed some laughably lenient expectations on RPO, but if your system can handle it easily, every 5 min or 1 min, I suppose sounds like a good idea. Regarding the many-files issue, if you aren't employing some automation for tlog restores its time to get scripting, because doing it manually just sounds terribly laborious and prone to user error (with the CIO tapping his watch behind you).
Nick – thanks, glad you liked the post. Like you mentioned, it's tough to get a single set of measurements that will make everyone happy, but cumulative job time is a great start. If you run those tests, make sure to clean out your MSDB backup history first as well – updating that can affect job times.
Hi Brent ,
Question regard log shipping with readable mode when back up log every minute . in standard log shipping for long transaction each trn file will be restored and rollback until the transaction completed (i.e when rebuild one index than take 5 minutes – it means that the log shipping will restore the first file 5 time and rollback it 4 time , the second file restore 4 time and rollback 3 time etc' ).
We can work around it by customized script to restore log shipping only every X minutes ( 15 ? ) and rollback only open transaction in the last restore trn file .
Any recommendation ?
Eyal – log shipping with readable mode is for running reports on the log shipped subscribers, not disaster recovery. Those two things aren't compatible. If you need a reporting server, build a reporting server – you won't want to do restores every minute on that box.
Hi Brent ,
I need both reporting server and disaster recover . Do you have any suggestion for the report server to avoid the multiple log shipping restore and rollback when apply the every minutes log ?
Thanks Eyal
Eyal – sure, the backup schedule has nothing to do with the restore schedule. You can just do restores once per day if you want as long as the backup files are available on a central server that isn't affected by the main server going down.
Brent ,
But the issue is the multiple restores and rollbacks of any trn file that cause by the frequency of the backup vs. long transaction .
For example for transaction of Index rebuild that take 5 minutes the log shipping will restore the first file 5 time and rollback it 4 time , the second file restore 4 time and rollback 3 time etc'.
Eyal – I think you're confusing how rollbacks work with how restores work. If you don't run RESTORE WITH RECOVERY, then the rollbacks aren't going to happen multiple times.
Can anyone recommend an automated restore script that would work well with the default folder structure and file names used by Ola Hallengren's Maintenance Solution script in cases where the backup info in msdb and the Ola's commandlog table is gone? I'd like to be prepared for a worst-case scenario.
Mark – did you read the other comments with the MSSQLtips link?
I could easily adapt the MSSQLtips script (Ola's script uses separate subfolders for the three types of backup files). But if someone else has already done it (or something similar), I'd rather not reinvent that wheel.
Ola's scripts also put those three subfolders under a subfolder for each database. I think that the MSSQLtips script assumes that all of the files are in one folder, but I could be wrong about that.
I found these, but haven't decided which to implement yet:
I thought others might find this information useful.
OK. I agree with Brent's assertion that our backup strategy should not be based on arbitrary rules, but instead it should be driven by the actual negative impact to the company shoud data be lost. In some cases, the loss of a single transaction can be devistating…it's very rare, but it all comes back to a DBA's favorite pat answer, "It depends". In this case, it depends on the value of the data that could be lost, the finanancial and legal ramifications,etc… and that information has to come from the business. This doesn't mean the business always knows best when it comes to backup strategy because they do not always fully understand what they are asking for, but that's why it is important to engage in a dialogue about he pros, cons, risks, costs, etc… with the business in order to come to the proper solution.
Now, to the main reason I am responding to this post…I feel like I've entered the twilight zone. Please tell me what I am missing about this discussion………
I do not understand the angst about relying upon the SSMS GUI to generate restore scripts. I see recommendations to duplicate functionality that is already available to us natively in SQL Server. I've been restoring databases for years using the SSMS GUI with just a few clicks of the mouse no matter how complicated the restore scenario, how far back I wanted to restore to ( as long as the backup files still existed ), or the number of backup files involved….in our shop, each backup operation writes to its own distinct file. When formulating a restore, SSMS intelligently navigates the combinations of full, diff, and log backups and the timeline provides a very simple way to pinpoint your desired recovery point. It even properly traverses forked recovery paths when they exist, something that not even all of the leading third-party tools can do ( one example, Idera SQLsafe, which we use extensively here ). I have yet to run into a scenario in which SSMS did not provide the simplest and quickest route to the desired restore. To restore a database with SSMS: point, click a few times, and out pops your restore script, complete with hundreds of individual file restores if that is what is required with very frequent log backups like Brent is proposing above. Again, what am I missing? I am genuinely intrigued.
I ran out of patience trying to read this. What's the question?
Sorry, I should have lead with that. Why the concern over relying upon SSMS to generate restore scripts? What functionality is SSMS not providing that is necessary to restore a database quickly and reliably?
One database isn't a big deal. Try restoring 50 or 100 when a server disappears.
OK. After running through some more dramatic scenarios, I am seeing some of what I was missing. We have pretty comprehensive SOPs on how to recover in the worst of situations, and have had to do so on several occassions. But after this exchange and some deep thought ( ouch! ), I do see a gap in our DR plans….we need to be able to restore msdb to the point of failure in order to have all of the backup data we need to recover fully and quickly when msdb has also been lost. Currently we only do nightly full backups of msdb. I believe this will be easier and more reliable than a home-grown scripting solution based on existing backup files, although having one in reserve as another recovery option wouldn't hurt…one more layer of protection. I'm not too concerned about handling multiple databases, as we can generate the scripts via SSMS so quickly, by the time one database is done restoring, we can have the next DB set or two ready to go….as long as we have the msdb data to do so. This will definitely spawn some additional requirements discussions in our shop. I always appreciate being challenged to think deeper into issues like this. Just when I think I have it figured out, I discover or learn something new. Keep challenging us!
I'm a fan of Idera's SQLsafe product, as it gives you a lot of the automation you need when you have lots of databases to backup, and want to be able to quickly find the files for a particular backupset, etc. You can also use their SQL virtual database product to attach a backup without having to restore it, which can be handy with large databases. And you get backup set compression and encryption, but that's no longer an issue with 2012.
I agree, Brian! SQLsafe has been the backbone of our backup infrastructure for years. It provides a very effective enterprise-level backup/restore solution. It also has built-in functionality to backup directly to TSM, bypassing disk. You do give up the ability to use Virtual Database with this approach, but it does allow you to save on disk space for backups and the associated $$$. You can extract a backup file from TSM to disk to use Virtual Database if needed. Not as convenient, but possible. Their console/GUI is great and fascilitates quick troubleshooting, browsing, and restores. It even supports point-and-click restoration of databases from one server to another, very handy! The only negatives in my opinion are 1) obviously it adds cost to your infrastructure and 2) it doesn't navigate forked recovery paths properly.
Ya, truly a tricky question to ask, but hourly differential backup and 10 min once transactional log backup will do good for most of the application right !!! OMG
…and don't call me Shirley.
Richie stole my joke 🙂
Though I have never managed a server with this much data or databases (and probably never will), I see the logic of a little slow down over time, to a big wait when it might be at a critical time. I have capture a few of the scripts to practice. thanks.
just a quick note on the number of files from our experience.
One day out of the blue our full backups started to take a very long time to complete (from a few hours to over a day!). It took us some time to find the cause, which was the large number of small transaction log backup files.
We're backing up around 60 instances to a Data Domain, most of them backing up trnlogs every 15 minutes (and 1 full/day).
A problem with the cleanup job resulted in an increasing number of small files on the Data Domain. Once we manually deleted the older trnlog backup files the duration of the full backups went back to normal.
Btw, eventually the vendor pointed us in the right direction.
So, this seems to be a case where more files could be an issue. Just wanted to let you guys know in case someone experiences the same symptoms
Thierry – correct, that's one of many reasons we don't recommend folks use dedupe appliances with SQL Server: https://www.brentozar.com/archive/2009/11/why-dedupe-is-a-bad-idea-for-sql-server-backups/
Hey thanks for the tremendously useful link Brent. I was unaware of that and will certainly go have a chat with my colleague on Monday (the one responsible for our DD). Oh I can already picture him turning pale lol 🙂
My network administrator says you're off your rocker! He said that every time you back up the log file, all transactions in the database are going to stop because they can't write to the log while the log is bring backed up. He says that if we follow your suggestion, that we will be locking our database every minute and chaos and anarchy will reign.
I'm trying to avoid a fist fight, or at least a heated argument, Could you provide me the information I need to keep peace in our office!
Jeff – you know, that's a great question. I would actually challenge *him* to prove that. I know for sure it's not the case, but I can't find any documentation proving it.
The network admin is effectively saying, "I believe planes can't carry margaritas." You won't find any documentation that says planes can't carry margaritas.
I don't think he understood the backup. I expected the physical log file to be locked while it was being copied. I explained the log file structure and that the backup was just a copy of the data within the file, with very distinct start and stop points. He's on board now.
Well I am sitting at home watching 20 txlogs restore over the last 4hrs with no end in sight… seems regardless of how big or small my txlog file is, there's huge wait time between each as they restore. more isn't better in my case.
Don – you may be falling victim to an MSDB that hasn't been purged in years. Here's the background on that: https://www.brentozar.com/archive/2009/05/brents-backup-bottleneck-msdb/
Hi Brent
I have tested changing our hourly backups to minutely, and it seems to work fine. I know when I go to management and recommend we change to minutely backups, they're going to ask why we couldn't do it more frequently. We have fairly small databases, and the minutely t-log backups are taking ~5 seconds. Is there any reason not to continue your line of thinking and go with 30 seconds? How about 15 seconds? 10? 5?
Dave – sure, in mission-critical environments, some shops have a WHILE 1 = 1 loop that just keeps backing up log files.
Great post Brent!
We already do run our t-logs on a minute schedule for our mission critical systems. A question though, I notice that if there are heavy transactions, that sometimes results in the backup taking more than a minute. For instance, when we add large tables to transaction replication read-only subscribers, sometimes the backups take several minutes while the snapshot and distribution agents are busy writing schema and data changes over. Anyway to mitigate that?
Hi Brent,
Great post! We already have our mission-critical databases on a 1 minute transaction log backup schedule, and have never experienced any problems with it. A question though, I notice that when there are heavy transactions happening, the backups take longer to complete, sometimes several minutes, missing the schedule in between. An example would be adding a large table to a transaction replication read-only subscription. On the subscriber I've noticed it can take a long time for backups to complete while the snapshot and distribution agents are loading the schema and data. Is there anyway to mitigate this?
I'm not sure this would be quite the same situation, but your mention of replication and hitting bottlenecks with log backups reminds me of a similar situation we had with log backups and CDC…basically, make sure your VLFs are well configured (not too many) because we had one database with high VLFs and CDC, and the log reader for CDC/replication was having a hard time churning through the log during big expensive operations like index maintenance. Shrinking and regrowing out the log file at fixed intervals to get rid of the massive VLF count really seemed to improve performance and resolve our issues with it.
Brent mentions splitting backup jobs up; but he doesn't mention how to do this if you're using Ola Hallengren's SQL Backup scripts (MaintenanceSolution.sql).
Since I've never tried to do this before and found myself needing to split transaction log backups into multiple jobs, I found myself needing to modify Ola's scripts. Here's how I changed the 'transaction log' backup job:
@description=N'sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d DatabaseAdminTools -Q "DECLARE @odds nvarchar(max);SELECT @odds = coalesce(@odds+"," , "") + name from sys.databases where database_id > 4 AND database_id % 2 = 1;EXECUTE [dbo].[DatabaseBackup] @Databases = @odds, @Directory = N"H:\Backup", @CompressionLevel=1, @Compress="Y", @BackupSoftware=N"SQLBACKUP", @BackupType = "LOG", @Verify = "Y", @CleanupTime =336, @CheckSum = "Y", @LogToTable = "Y", @Execute="Y"" -b'
[DatabaseAdminTools] is the name of the database I keep our maintenance scripts in, yours may differ.
The secret sauce is this line (incredibly simple, but I'd never tried it before):
DECLARE @odds nvarchar(max);SELECT @odds = coalesce(@odds+"," , "") + name from sys.databases where database_id > 4 AND database_id % 2 = 1;
And then use "@odds" as the parameter to @Databases.
George – HAHAHA, Odds scares me just because it implies gambling, but I like where you're going with that, heh.
I have a question regarding log shipping, i have created a log shipping every went well, now my Q is 1.How do i know the transaction log has been restore to the the database? 2. Where are the transaction logs came from?
You can use a logshipping monitor server, or you can query logshipping tables to see that information. Example: http://msdn.microsoft.com/en-us/library/ms188331.aspx
For more info on transaction logs, see Jes' video here: https://www.youtube.com/watch?v=lcmYeE-cqQo
sorry i meant the log shipping got successfully.
I'd like to add that after running these t-log backups once a minute for about half a year now, I've started to notice msdb bloat (1,000% growth). I tracked the culprit down to the msdb.dbo.backupset table which contains a row for each backup set. The msdn page references the sp_delete_backuphistory stored procedure as a way to limit the growth of this and other associated tables. I'd recommend anyone setting up a frequent backup schedule consider creating a sql agent job to run this stored procedure and clear out old backup records every so often.
I found that the sp_delete_backuphistory sp can cause locking issues, even if only deleting a small amount of data, so I delete out the backup history manually, (as part of the nightly full backup) which works well.
After a nightly full, we delete the prior transaction log backup history, so msdb does not bloat. although it means that the history is not available for prior days, we currently only keep transaction logs since the last full (might increase to last full -1, to give some extra granular restore ability), so this works for us.
Would anyone recommend log shipping every 1 min for a single db server with over 1000 databases? If not, what timing and why?
Brian – start here: https://www.brentozar.com/archive/2015/02/many-databases-can-put-one-sql-server/
This blog post is in Portuguese (I can translate it), but I think it can help on thinking about how many databases a single instance stands for… =)
How is this strategy affected by our VMware administrator performing server snapshots once a day? During the snapshot process, it appears a full DB backup is being performed. Does this ruin my SQL backup chain (full, diff and transaction)?
Pat: your question makes it sound like you've never tested your backups. O_O
You want to get started on that right away, because some snapshot products do indeed break the backup chain in a big, ugly way.
You are very observant Brent, we have not tested our backups. There's no time for that (so says the company), they'll just work.
Until just two days ago, I didn't even know that the VMware snapshot backup was backing up the databases as part of it snapshot. According to the backupset history, the backup (from the snapshot) is a copy only so I think I'm OK, but still not entirely convinced.
I need to test it and I need to convince the company to spend some time to develop server restoration documents. In the mean time, I've convinced our VMware manager to only snapshot our SQL servers once a week and not daily.
Thanks for the great column, loved the reading of this.
Hi Brent,
Very interesting your points about log backups. I´ve ready your blog post to the end, and I thought taking log backups on a minute basis will only protect your database on situations where you can´t take tail log backups when a crash occurs, right?
If I understood it right… don´t you think the probability to get some of these hundreds or even thousands of log backup files corrupted is higher than a crash scenario where you can not take the tail log backup?
I´m talking about the cost vs benefits on taking that kind of log backup strategies.
Best Regards,
Edvaldo Castro
Edvaldo – correct. In my decade-plus of working with SQL Server, I've seen sooooo many instances where the server was down and unable to take a tail of the log backup. Hardware crashes, storage failures, SQL Server refusing to start, you name it.
If you're worried about backup files being corrupted, that's a separate problem – go fix that! Don't back up to corrupt storage. 😀
Regarding costs (vs. benefit):
Each log file is about 92 KB, even if there was no transaction to log. So you would have an overhead of ~129 MB per database, if you log every minute (vs. only once per day or once per hour).
The total backup time would not increase (beside the little overhead), because it makes not much difference, if you write 50 GB log backup at once or split it in many small parts (for the I/O subsystem it should be better to write 30 MB every minute over the whole day instead of writing 50 GB at once).
Restore: on my local PC it takes about 1-2 seconds to "restore" an empty / nearly empty log backup file. If you would take log backups every minute, your total restore time could be increased by 1440 min per day * 2 sek / 60 sec = 48 min in the worst case (slow restore, crash just before the next full / diff backup; no log shipping set up). If you would backup all 5 min (as we do) the restore time would be increased by max. 10 min.
Regarding the chance that one of the 1440 log backups is corrupt vs. the chance, that one of e.g. 24 log backups is corrupt:
– corruption could / should only occur because of I/O-errors (firmware error; backup to a bad tape / local or external HDD without RAID / parity). Logical errors (because of a bug in SQL Server) should be negligible
– there is a slighly higher chance for many files to be corrupt than for few – if the I/O-error is in the file table instead of the data part of the HDD
– if there is an error in a 1-hour backup file, you'll loose up to 60 min data (+ all data in following log backups)
– if there is an error in a 1-minute backup file, you'll loos only 1 min data, because you can restore all the files before
Thomas – great in-depth thinking there!
We take short interval backups as you've suggested. I then routinely run a script which restores a VerifyDB using a script restore to test the viability of those backups to restore the database, then perform some DBCC checks on the VerifyDB to determine if there might be issues with the resulting database if we ever had to actually restore it. Much more frequently than I would have ever guessed ( on average now about 1 run in 9 ), the script hums along with the FULL, the DIFFERENTIAL, and then at some point say LogFile = 70 or 220 ( or in one of this morning's failures LogFile 2 ), the script fails with the error…
Database 'VerifyDB' cannot be opened. It is in the middle of a restore. [SQLSTATE 42000]
I can't believe that sql server backups are that unreliable. What is the flaw in my process?
Unfortunately, I can't really troubleshoot your scripts from here.
Just wondered if there might be some switch or a timing problem I was not taking into consideration. In general the script is something like.
RESTORE DATABASE VerifyDB FROM DISK='Full backup file' WITH STATS = 1, MOVE 'prod_log' TO 'Verify.ldf', MOVE 'prod' TO 'Verify.mdf', NORECOVERY, REPLACE — restores until Jan 27 2016 10:09PM
RESTORE LOG VerifyDB FROM DISK='tranlog' WITH STATS = 1, FILE = 2, NORECOVERY — restores until Jan 27 2016 10:01PM
RESTORE LOG VerifyDB FROM DISK='tranlog' WITH STATS = 1, FILE = 3, NORECOVERY — restores until Jan 27 2016 10:02PM RESTORE LOG VerifyDB FROM DISK='tranlog' WITH STATS = 1, FILE = 4, NORECOVERY — restores until Jan 27 2016 10:03PM
RESTORE LOG VerifyDB FROM DISK='tranlog' WITH STATS = 1, FILE = 5, NORECOVERY — restores until Jan 27 2016 10:04PM
and a few hundred more
Results typically look like
RESTORE DATABASE VerifyDB FROM DISK='full backup file' Move…
6 percent processed. [SQLSTATE 01000]
13 percent processed. [SQLSTATE 01000]
20 percent processed. [SQLSTATE 01000]
27 percent processed. [SQLSTATE 01000]
34 percent processed. [SQLSTATE 01000]
41 percent processed. [SQLSTATE 01000]
48 percent processed. [SQLSTATE 01000]
55 percent processed. [SQLSTATE 01000]
62 percent processed. [SQLSTATE 01000]
69 percent processed. [SQLSTATE 01000]
76 percent processed. [SQLSTATE 01000]
83 percent processed. [SQLSTATE 01000]
90 percent processed. [SQLSTATE 01000]
97 percent processed. [SQLSTATE 01000]
100 percent processed. [SQLSTATE 01000]
Processed 1832 pages for database 'VerifyDB', file '[database]' on file 1. [SQLSTATE 01000]
Processed 3 pages for database 'VerifyDB', file '[database.log] file 1. [SQLSTATE 01000]
RESTORE DATABASE successfully processed 1835 pages in 0.196 seconds (73.107 MB/sec). [SQLSTATE 01000]
often will go sometimes a few sometimes 70 to 200 or more transaction files in before…
RESTORE LOG VerifyDB FROM DISK='tranfile' WITH STATS = 1, FILE = (?), NORECOVERY — restores until Jan 27 2016 10:01PM
Msg 927, Sev 14, State 1, Line 1 : Database 'VerifyDB' cannot be opened. It is in the middle of a restore. [SQLSTATE 42000]
Is there a down side to using copy-only full backups in combination with normal transaction log backups?
I ask because we are looking into a sql 2014 upgrade and using Availability Groups. You can do only copy-only fulls from a secondary, although the transaction log backups seem to work well no matter what replica you run them on. As long as you have the copy-only full, and and an unbroken set of transaction log files that cover the period in which the copy-only full ran, you seem to be able to restore without any troubles.
JohnH – that question isn't really related to this blog post. When you've got a general question about databases, your best bet is to head over to http://DBA.StackExchange.com. (I'd rather teach you how to fish.) Enjoy!
Hi Brent,
Please feel free to redirect me! I'm asking you as I think you can probably give me quick and straight advice.
We have a single database, not too big only 60Gb running on SQL Server 2008 R2. It's merge replicated every minute to 3 subscribers. I've kind of inherited the backup plan, which is a single backup of the Database, Log and system databases every evening including full server backups with Backup Exec.
We've had 2 major server failures over the last 10 years, both were recovered with minimal data loss (acceptable to the company) using these backups. Downside is it took a few hours, but because of our multiple sites users are just redirected to continue working.
Would we benefit by adopting a more frequent log backup plan?
Jim – rather than asking me, ask your business users. Head on over to http://BrentOzar.com/go/fail and get our HA/DR RPO/RTO worksheet, fill that out, and share it with your business users. They'll tell you if things need to be better. Hope that helps!
What happens when you're generating new transaction logs faster than they can be written to disk?
We have our transaction log backups happening every 20 minutes. As a test I tried reducing it to once per minute as you propose here but what I found is that for awhile transaction log backups would occur once per minute, but then there would be a spike in transaction log activity and the next backup would take 20 minutes to complete, then the one after that 20 minutes and so forth until the next differential or full backup occurred and the backups would go back to one per minute for awhile until the problem repeats.
For us we have a single database being backed up so creating multiple transaction log backup jobs won't help either…. is there another way around this besides faster disks or eliminating activity which causes the transaction logs to grow?
Brad – it's so funny you ask that! That's exactly how I first wanted to go into consulting. I ran into that exact problem, and we brought in a consultant who said, "This looks impossible – there's no way you're doing that many transactions per second. I've never seen a server go that fast."
At that moment, I knew I wanted to be a consultant, because I already had more experience than that guy.
You basically have three options:
* Write less transactions
* Speed up the reads on the transaction log drive
* Speed up the writes on the log backup target
Troubleshooting each of those is beyond what I can do fast in a blog post comment, but hopefully that gets you started on the journey. And congrats!
I had to restore 5 minute interval logs from a tape library once. It took well over a day because the tape robot was retrieving tapes all the time, and rewinding / fast forwarding to some very small log backup somewhere on the tape. Now, I use a script to determine the percentage usage of the log file, and trigger a log backup once it's over 10%. Never looked back.
Peter – have you explained to the business that you can lose hours of data? As long as they're cool with that…
Why do you write your backups primary to tapes? Get some hard drives (no, don't use the same SAN as for your data), create the 5-min-log backups on this drives and let your backup software write those files to the tapes when a sufficient amount (or time) is reached. When you need to do a restore (and have all the log files on the disks already deleted), you can restore the files from tape to disk (should be fast, if they are many written in one large block) and then a SQL restore from disk.
PS: Bonus points for using the MIRROR_TO option to write a copy of the backup stream to a second location (same drive type, so another HDD and no HDD plus tape).
The risk of not being able to restore the data for days is offset by a mirror setup which we have on line. Furthermore, we have the data in cash registers, so while we had some corruption trouble with the database, which was 10TB at the time, we never lost a byte of data.
If we backup every minute, or backup based on the size, what's the difference? That increment can be very small. While we rebuild indexes using Ola's scripts, there's a lot of log activity, but especially during the night, there's hardly any update, delete or insert at all. No, I'd rather backup logs on demand, I've learned the hard way. IMHO there's no merit to timed log backups.
Peter – sure, as long as nobody ever accidentally runs a delete or an update without a where clause.
Oops. It's trashed on both the primary and the mirror. Enjoy!
Brent, how do you schedule transaction log backups every minute? Is that using an SQL Server capability? Don't the backups block so you can't run another backup (of the same type) until the current backup finishes?
I can appreciate pushing the frequency to the wall. On our most critical SQL Server DB, we take transaction log backups every 15 minutes. Most complete in seconds. However, there are occasional amazingly large transaction log backups that take over an hour!
We have been using the Windows Task Scheduler and I note that it blocks: if a backup is running when the next is to start, the next isn't run.
My next script will now probably start itself again to keep taking transaction log backups continuously (or sleep to limit frequency to one minute before).
What do you think of taking more frequent differential backups? We are still taking daily fulls (which are taking about 5 hours for 3TB). We have also resorted to taking 2 transaction log backups before the full (won't need to do that when we switch to a continuous transaction log backup model) to keep the amount of log contained in the full to a minimum (and we keep taking transaction log backups every 15 minutes).
Steffan – using SQL Server Agent.
If you have log backups that take over an hour, that means you have no point-in-time recovery during that hour. If the server dies, you just lost up to an hour of data. That's usually a sign that you need to do performance tuning on your backup process: tweaking compression settings, backing up to a faster share, checking your network throughput, etc.
Is it possible to restore Transaction Logs to a database every hour without having to restore the full backup first?
Can you set database to No Recovery, apply transaction Logs, then set to Recover. Do that every hour? is that possible?
John – for Q&A, head over to https://dba.stackexchange.com/
You can set the database to STANDBY. This allows you to read (not write) from it and you can restore the next log backups any time you want (and set it to standby again).
And of course you can execute a RESTORE myDb WITH RECOVERY when you need it as full usable database (but after this you will no longer be able to append more log backups).
Hey, Brent. Long-time listener, first-time caller (bet it's been a minute since anyone heard that). I'm planning our backups and want to implement minutely log backups. My concern is what happens if a log backup runs long? Do the other log backup jobs fail or stack up and run as soon as the other job ends? My guess is they fail but I'm curious if they fail "elegantly" (i.e., the backup chain isn't broken and everything is fine, just the job fails) or does it bugger everything up? I see similar questions asked above but they weren't exactly the same and I couldn't gleam my answer from those questions or some google-fu. Thanks for the help.
Jon – why not give it a shot? While one of your Agent job doing a log backup is running, try triggering it again and see what happens.


text:
FRANKFURT (Reuters) - Carmaker Opel, General Motors' (GM.N) ailing European brand, could use a little ancient wisdom if it wants to reverse the $3.5 billion losses of the last three years: know thyself.
Specifically, know whether your customers really do want to pay extra for the latest driver assistance features or whether dreams of being an upscale marque will chase away your dwindling band of loyal buyers.
"What kind of brand is Opel, and what customer group are we trying to address?" asked Jaap Timmer, European Opel dealers' president and a supervisory board member ahead of a key meeting last Thursday. "First it's supposed to be premium, then it's not premium - we need a clear strategy."
In January 2010, then-Opel Chief Executive Nick Reilly first formulated his plan to move the brand up the value chain as a "leading European manufacturer of high quality, desirable automotive products, based on German Engineering", competing head to head with rival Volkswagen (VOWG_p.DE).
Opel churned out cars that steadily became every bit as good as Volkswagen's in many cases, but its brand image did not keep pace. Company insiders voiced frustration that people still "have to explain themselves" when buying an Opel.
The results were devastating. In Germany, its single largest market, Opel's share slid to a record low of 7 percent in the first four months of 2012 - a third the size of the Volkswagen (VOWG_p.DE) brand and easily trailing luxury names BMW (BMWG.DE), Mercedes-Benz (DAIGn.DE) and Audi.
With Europe's car market shrinking 20 percent since a peak in 2007 before the financial crisis struck, the strategy was at best ill-timed. Opel's acute crisis and heavy losses became such a top priority for Detroit that headquarters dispatched Vice Chairman Stephen Girsky to Germany to oversee Opel's overhaul personally.
A new 10-point turnaround plan broadly centres on reducing overcapacity, investing in new models and powertrains, lowering material costs as well as extracting savings through an alliance with French rival Peugeot (PEUP.PA).
Yet apart from management's intent to close a German factory in Bochum at the start of 2017 and vague ideas of shifting some Chevrolet production to underutilized plants in Europe, few concrete details have been revealed.
The purpose of Opel's move upmarket was to better differentiate it from Chevrolet, which GM global marketing chief Joel Ewanick wanted to compete with rival value brands, something Opel was less well placed to do, with almost all its assembly line workers employed in high-wage western Europe.
Former Opel labor leader Klaus Franz was critical of Ewanick's plans at the time. He feared the brand would lose its existing more price-conscious customer base. Going upscale was the "Saab-isation" of Opel, Franz declared, in reference to GM's Swedish premium marque, which died a slow death.
Timmer, too, believes Opel should orient itself more in line with Volkswagen's Skoda brand, which is aimed at cost-sensitive buyers, than the premium VW brand itself.
"I think that might have been a mistake by Reilly," he said.
It's a sentiment shared by many at Opel who worry that GM's borderline resentment of its unit's troubles is rubbing off on car buyers, making them less likely to reach deeper into their pockets for a Zafira Tourer MPV with an expensive trim package.
"Consumers feel much more comfortable spending 40,000 euros of their hard-earned money on a well-equipped family van if it has a good image and stands for success, not for an Opel," complained one manager who asked not to be named.
Opel Chief Executive Karl-Friedrich Stracke signalled to industry insiders in Monaco recently he might reverse course.
"We moved up too quickly in the ranks," he told an Automotive News Europe conference, "and we lost some of our affordable customers with our pricing philosophy. That's what we have to go back to with our content and prices in the future."
Stracke wants Opel to focus on "traditional and attainable potential customers" as part of midterm business plan he presented to his board last Thursday.
"Attainable sounds to me like a euphemism for value-oriented and not premium," says Metzler Bank analyst Juergen Pieper. "If you're analysing it realistically, though, it's the right conclusion, since it would be an illusion to think that Opel could position itself as premium among mass-market brands over the next 10 years."
GM's gambit of pushing unions into wage concessions by playing one plant off against the other in the media or openly wavering in its commitment to Opel has also lost it customers, says Ferdinand Dudenhoeffer, head of the Center Automotive Research (CAR) in Duisburg.
In the wake of emerging from bankruptcy in the United States in 2009, GM was poised to sell Opel. But in November that year GM's board of directors overruled management and reversed that decision, deciding to keep Opel. Doubts about Opel's long-term future linger among German consumers, however.
"Someone who is uncertain about the future of a brand won't buy a car from that company," explained Dudenhoeffer. "GM and Opel have themselves to blame."
Despite its woes, Opel has enjoyed some critical successes. It has won the European Car of the Year award twice in the last four years, once for the Opel Ampera electric car, which sells for 43,900 euros and is known as the Chevrolet Volt in the U.S. Dudenhoeffer believes Opel is three years ahead of Volkswagen with the Ampera.
What's more, Opel's engineers have focused on improving their cars' interiors through more luxurious seats, such as the orthopaedic-certified AGR seats offered in the Astra for example.
Yet Opel's image cost it thousands in lost revenue per car. While Volkswagen can sell a basic 1.4 litre four-door Golf hatchback starting at 17,760 euros in Germany, a comparable Opel Astra can already be had for just under 15,000 euros.
"Long-term success is not possible without a strong brand," said Bernd Buechner, the head of Millward Brown in Germany, an agency that annually ranks global brands. "But Opel is fighting with problems on all fronts, and consumer confidence in the brand is severely damaged."
Rehabilitating Opel's image is "absolutely crucial", acknowledges Johan Willems, a member of Stracke's senior management team responsible for communications.
"The brand itself needs a lot of attention at the moment, especially in Germany," he adds. "Our leadership team is working hard and putting a lot of emphasis on this. Nothing is more important."
Millward Brown's Buechner thinks all is not lost. He believes the extended-range Ampera could produce a halo effect for Opel, as the Volt is doing for Chevy in America.
"There are brands that were able to reverse their poor image. Just think of Audi and Skoda, or Jaegermeister (liqueur)outside of the auto industry. The Ampera can be the crystallisation point of a successful turnaround for Opel with the right marketing strategy," he said.
Reporting by Christiaan Hetzner; Editing by Will Waterman

subset: commoncrawl


text:
Installation by Siegrun Appelt with 72 headlights and control system.
The 72 headlights, distributed on 8 masts, show - via computer programmed random principle - a precisely choreographed interplay of lights that swich on and off. The light overacts the physical borders of the place and its structures, connects spatially also changing light shade constellations. The environment appears graphic in the light or loses itself in the darkness. In the light cone passerbies become participants, in the shade observers. The light continually creates new, alternating perspectives of perception and becomes more tangible as a reality influencing medium. Due to the permanent modulation of the aligned light direction, the light not simply functions as means of illumination, but becomes visible and recognizable as a source and cause of the visible.
Thus the perception and visibility of the environment prove to be technoid and mediatized functions of basic conditions. While usually the formative ubiquity of mediated images barres the view onto their causes and intentions, the installation refers to the medial character of those images, which we make ourselves from the world and our relationship it. The title of the work 5.3449019547362e+133 refers to the number of possible variants of the interaction of the different lighting sequences. It shows that a human life cycle would not be long enough, to see and experience the whole spectrum of possibilities. To that extent the installation also foregrounds the volatility of light and the passing of time as well as the transience of life, a continuum that itself is constant subject to change and in which coincidence and necessity are the driving forces.


text:
The public will be invited to participate in the reading of thirteen poems, composed by artist Stephen Bram in 1999, drafted in a single session plus one later revision. Asked about the context of their creation, Bram wrote "At the time I made them I was living in Munich and didn't know anyone very much. My German was rudimentary so there wasn't much to read and I couldn't follow television or radio. Even the internet was slow back then. I used to complain that I was suffering from narrative deprivation."
About 3-ply
3-ply is an independent publishing initiative that focuses on publication, writing, editing and translation as an extension of art practice.


text:
The 3rd International Conference On Geotechnical Research and Engineering (...
The 3rd International Conference on Geotechnical Research and Engineering (ICGRE'18) aims to become the leading annual conference in fields related to geotechnical engineering. The goal of ICGRE'18 is to gather scholars from all over the world to present advances in the relevant fields and to foster an environment conducive to exchanging ideas and information. This conference will also provide an ideal environment to develop new collaborations and meet experts on the fundamentals, applications, and products of the mentioned fields.
All accepted and presented papers will be published in the conference proceedings, under an ISBN reference in a USB drive. The online version of the proceedings will also be published under an ISSN reference and each paper in the proceedings will be assigned unique DOIs by CrossRef. Furthermore, selected papers from the conference will be submitted for possible publication in the following journals from Avestia Publishing (publication fees may apply):
International Journal of Civil Infrastructure (IJCI)
ICGRE is an acronym for International, Conference on Geotechnical Research and Engineerng.
To view the website for the previous event in this conference series, please visit: www.2017.icgre.org.


text:
Don't fancy splashing out, queuing for a table and joining the hoarde this valentines? Well I have a treat in store!
If you haven't been so fortunate to stumble across the joy of brioche crayfish stuffed rolls never fear, I am hear to awake you senses, tantalise your eyes and tickle your tastebuds. This recipe is inspired by the ever popular and outlandishly beautiful lobster rolls that have been popping up all over my instagram feed the last couple of weeks, but a cheaper and easier valentines variation.
Lets just get right up on in there shall we…
Despite the trend for so many to dine out on Valentines, I am rather a fan of eating in and there is nothing like and impressive bit of home cooking, some candlelight and a bottle of wine to awaken those passionate embers and get the fires of romance burning. Sound like a 50 shades of grey novel… well, i'm not gonna spell out the rest, you get the idea.
As a wheat-free foodie, rolls of the brioche variety are mostly a no go. One of the things I have always hankered to try are the decadent lobster rolls at Burger and Lobster. Since as yet they don't offer a variation to the normal sort, I have set about making my own with spelt flour (instead of the usual bleached wheat) In case you have never heard of spelt, it is a gluten-containing grain that is in the same family as wheat, but a whole lot easier to digest. It can be bought in most larger supermarkets and online too. Doves Farm is the brand I like to use. The recipe is enough to make 6 rolls, even though the quantities for the crayfish filling is only enough for two. I figure that if you are going to go to the trouble of making brioche you want a little leftover, no?!
If you are fine digesting wheat, or don't fancy making them you can buy them pre-made in the supermarket. It certainly speeds up the process and you can get the rolls from chopping board to belly in a matter of minutes. Also, just to clarify spelt is not a gluten free flours, it is just a little lower in gluten than wheat, so this is not a recipe for diagnosed coeliacs.
Spelt Brioche Rolls Recipe
Makes 6 Large Rolls
You will need either 6 large roll cases, or alternately make mini ones in 10 muffin cases
- 7 g (one sachet) active dry yeast
- 1 1/2 teaspoons flakey sea salt
- 500g white spelt flour
- 6 tablespoons honey
- 150g g unsalted butter, melted and cooled
- 4 large eggs + 1 egg (for the egg wash), at room temperature
In a small bowl, combine the yeast with the honey and warm water to activate the yeast. Allow it to sit in a warm area until the yeast mixture is foaming and bubbly, about 5-10 minutes.
Combine the flour and salt in the bowl (you can also do this in a mixer. In a separate bowl, whisk together the melted butter, remaining honey, eggs, and the yeast mixture.
With the stand mixer on low speed, slowly pour the egg mixture into the flour mixture. Increase the speed to medium to fully incorporate the egg mixture into the flour mixture. Continue to mix the dough for another 5 minutes on medium speed. The dough should be very silky and not stiff like regular bread dough. Alternately you can do this by hand. It takes a lot of kneading so stick with it. The dough will look like is has split at first, until the egg mixture gets fully incorporated.
Remove the bowl from the stand mixer, if using. Shape the dough into a smooth bowl and cover tightly with plastic wrap. Place the bowl in a warm area and let the dough rise until it roughly doubles in size, about 1 hour.
Unwrap the bowl, punch down the dough, and wrap again tightly with plastic wrap. Place the bowl in the refrigerator for at least 2 hours. (Note: when punching the dough, you may lightly flour your hands to prevent sticking.)
Remove the dough from the refrigerator. Grease a muffin or hotdog case and add 1/2 cup (85-90 g) of the dough into each case.
For the egg wash, break 1 egg into a small bowl and whip with a fork or small whisk to combine the white and yolk well.
Brush the tops of the brioche rolls with egg wash. Place the brioche rolls in a warm place to proof covered with a tea towel for 40 minutes, until they have risen, by half the size.
Preheat oven to 190°C/ 375°F.
Bake the rolls in the preheated oven for 16-18 minutes, until the tops are golden brown and a wooden skewer inserted into the centre of a roll comes out clean, then transfer to cooling rack and cool completely. Store cooled rolls in an airtight container for 3-4 days
For the Buns
Serves 2
- flakey sea salt
- 150g cooked crayfish
- 2 tablespoon creme fraiche, plus more if desired
- 1 tablespoon garlic oil
- 1 avocado, halved and sliced
- 1 tablespoon lemon juice
- 1 tablespoon chopped fresh parsley
- Dash cayenne pepper, plus more to taste
- salt and freshly ground black pepper
- 1 tablespoons unsalted butter, room temperature
In a small bowl, combine the creme fraiche, lemon, parsley, cayenne, garlic oil, and season generously with salt and pepper. Add the crayfish tails and gently stir until well coated. Taste and adjust seasoning, adding more creme fraiche if desired. Chill lobster mixture for 15 to 30 minutes.
If you are using rolls, spread the outside edges of the buns with butter. Heat a large frying pan over medium heat and toast buns, buttered side down, until golden brown, about 2 minutes per bun. For the rolls, slice them in half down the middle, cutting out a smell segment (to fit in more of the yummy crayfish filling), butter and toast them cut side down on the frying pan then fill each bun (or roll) with crayfish mixture and sprinkle with an extra dash cayenne and a few parsley leaves and serve immediately.
It is almost imperative that you drink this with a chilled white wine or a glass/ bottle/ jeroboam of champagne (whatever you fancy.) Just be sure to have a wonderful v-day.
Tess x


text:
EAU: Efficient Address Updating for Seamless Handover in Multi-homed Mobile Environments
EAU: Efficient Address Updating for Seamless Handover in Multi-homed Mobile Environments - Descarga este documento en PDF. Documentación en PDF para descargar gratis. Disponible también para leer online.
1 Software Research Institute 2 Institute of Software
Abstract : Dynamic address configuration is essential when maintaining seamless communication sessions in heterogeneous mobile environments. This paper identifies some significant problems when using the Stream Control Transmission Protocol SCTP Dynamic Address Reconfiguration SCTP-DAR extension. We illustrate that SCTP-DAR can enter a deadlock state during the handover phase, ultimately resulting in communication failure. Deadlock arises as a result of the basic design rationale of SCTP-DAR, i.e. using a data oriented transmission scheme to transmit address update messages. This paper proposes a new transmission control mechanism for efficiently exchanging up-to-date address information between association endpoints. In particular we introduce an address operation consolidation algorithm which eliminates address operation redundancy. In addition, a priority based transmission re-scheduling algorithm for address updating operations is proposed to detect and remove potential deadlock situations. The above schemes have been verified through experiments.
Keywords : Multi-homing Heterogeneous Networks Mobility Dynamic Address Configuration
Autor: Yuansong Qiao - Shuaijun Zhang - Adrian Matthews - Gregory Hayes - Enda Fallon -
Fuente: https://hal.archives-ouvertes.fr/


text:
Anki Anki Overdrive Expansion Car - Nuke
Item number K7GXK
Anki Overdrive Expansion Car - NukeUnleash this awesome vehicle on your Anki Overdrive set.
What makes Anki Overdrive the world's most intelligent battle racing system? Tech so advanced, it feels like the future.
Each Supercar is a self-aware robot, driven by powerful artificial intelligence (A.I.) and equipped with deadly strategy. Whatever track you build, they'll learn it. Wherever you drive, they'll hunt you down. The better you play, the better they become.
Whether you battle A.I. Opponents or friends, your tactical options are unlimited. And with continuous software updates, the gameplay always stays fresh. Customize weapons. Swap out cars.
Each Supercar is loaded with cutting-edge features, including an optical sensor, a dedicated 50MHz CPU, and two high performance motors, for precision maneuvering with 1 millimeter accuracy.
An Anki Overdrive Starter Kit is required to play (see item number K7GXC). Each player must have a compatible iOS or Android device (sold separately). Wifi required for battles between iOS and Android devices. Check device compatibility at anki.com/devices


text: This program is sold out.Call us at (202) 633-3030 to get on the Wait List. Additional tickets may become available or additional sessions may be added. Lidia Bastianich's American Dream Evening Program Wednesday, April 4, 2018 - 6:45 p.m. Code: 1L0196 Tickets Reserving your tickets... Text Size - + Lidia Bastianich (Photo: Diana Delucia Photography) For cookbook author, television personality, and restaurateur Lidia Bastianich, her story begins with an upbringing in Pula, a formerly Italian city turned Yugoslavian under Tito's communist regime. She enjoyed a childhood surrounded by love and security—despite the family's poverty—and learned everything about Italian cooking from her beloved grandmother, Nonna Rosa. When the communist regime began investigating the family, they fled to Trieste, Italy, where they spent two years in a refugee camp waiting for visas to enter the United States, an experience that shaped Bastianich for the rest of her life. At 12, she started a new life in New York. She began working in restaurants as a young teenager, the first step in a food career that would make her name. Drawing on her new book, My American Dream (Knopf), Bastianich shares the vivid story of the fulfillment of that dream. Join her for a conversation with Joe Yonan, food and dining editor for the Washington Post, as she discusses her close-knit family, her professional ascent, and the dedication and passion for food that led to multiple restaurants, many best-selling cookbooks, and 20 years on public television as the host of her own cooking show. The ticket price includes a copy of My American Dream. National Museum of the American IndianRasmuson Theater4th St & Independence Ave SWMetro: L'Enfant Plaza


text:
Thursday, March 23, 2006
Still no sign of Mocha
There's still no sign of Mocha until today.
Aunty Lucy called last evening again to check if I have better luck than her. She was disappointed to receive a negative response and lamented "Hai. She must be dead lor. If not, why is she not around? So many days never eat already not hungry meh? Or maybe she knocked down by car? Very heart pain leh."
*SIGH* I told her I will check with the sweeper the next time I see him. Maybe he will have some news. "Ya lor ya lor, you ask him ok, then update me." Aunty Lucy said with a tinge of hope.
I guess knowing what happened (even if Mocha's dead) is better than not knowing what has happened. I'm now going through the same feelings when I first lost Cotton - until now, I'm still not sure if she's alive.
2 comments:
- jennifer_yq said...
when nana(one of my community cat) went missing, we did everything we could to try to locate her..we called authority, asked the sweeper and walked around the nearby blocks dozens of times..in the end, we just said to ourselves that maybe someone adopted nana..this may be the case of mocha..maybe someone like mocha and adopted her..
- Celeste Lock said...
I wish it was the case Jennifer but... hai.
Subscribe to: Post Comments (Atom)


text: Had a late lunch here with a guest today. It was about 4:00 pm, so we decided to go light (so we thought) with an order of Steak nachos and a Carnitas taco each. The tacos were pretty good, but the nachos were possibly the best I've ever had! The chips were piled high with re-fried beans, lettuce, tomato, cheese, guacamole, etc. just a mountain of deliciousness! We topped it all off with a beer, then headed one block north to the Cody Road bourbon distillery. This is such a great town! I can't wait to return!


text:
paris. there is alot of hype surrounding pariee. it's the city of love. the cultural heartbeat of europe. the food-mecca of the world. so, let me just say that i had high expectations of the place. and well, it succeeded my expectations, times ten.
beauty was literally at every corner. even the friggin side walks, are cobbled stone...! need i say more? i will add that i was exceptionally luck with the weather (so ive been told) and three out of four days were perfect, sunny, crisp spring days.
each morning was started with a fresh orange juice, just baked croissant and espresso with a little milk at a cafe or an open air market along boulevard garibaldi.
each and everyday was filled with miles of walking, but we didn't mind, because the ambiance and mystic of the place completely takes your mind off of your aching feet.
we picnicked in the eiffel tower gardens, meandered along the river looking at stalls and watched painters mimic their surroundings, sipped espresso at outdoor cafes and gobbled fresh baguettes at every opportunity.
paris is awe-inspiring. we were exceptionally proactive whilst there and filled our days with the usual, eiffel tower, the avenue des champs-elysée and the louvre. however we were able to do a few things that might not be high on the lp guides of things to do like, taking an evening bike tour of the city, visiting the catacombs and taking the train to do a self-guided tour of château de versailles.
these were probably the highlights of my very first trip to the city of lights and ones that i highly recommend! we joined the fat tire bike company which lead us around the cities hot-spots at sunset. it was magnific...! the tour itself included red wine, the cities top sites, an ice-cream stop and an evening river cruise, which presented the city in all her shining glory. for €30, you'll be hard pressed to find a tour as fun and inclusive as that one.
the next two were both self guided trips that are a piece of cake to navigate. even if you don't speak a single word of french, like myself! first up is the catacombes. in short, they are an array of tunnels, forgotten about until the late 18th century, which then became a storage space for around six million people, collected from numerous parisian graveyards following an array of infections that came from the numerous inhabitants of the area. next is the château de versaille. an amazingly beautiful place that was home to marie antoinette and louis xvi in the 18th century. to properly wander this magnific place, you need to set aside a day in order to walk the gardens and explore the various rooms and estates located on the ground. this short train ride from ol' paree is well worth a visit.
well that sums up my first mini-vacay to paris. the pictures really do tell the tale on there own... don't you think?
au revoir.
pics. (above) view from our hotel window, view of the eiffel tower from the river seine, the avenue des champs-elysée, the notre dame cathedral, a painter on one of the many bridges along the seine, mona needs no introduction, napoleons apartments at the louvre, one of the many beautiful streets in the latin quarter, sunset on our bike tour, the louvre at dusk, the eiffel tower at night, the catacombs, château de versaille, marie antoinette's estate at versaille, me at the château, the basilica of sacré-cœur at montmartre and to top it all off, my favourite picture of paris.


text:
Global Digital Asset Management Market 2017-2021
About DAM
DAM is the management of rules and processes used by an organization to organize, store, secure, and distribute their digital assets. Digital assets include images of all formats, PDFs, video files, podcasts, word documents, spreadsheets, and presentations. DAM involves management tasks and decisions concerning the receipt, cataloging, storage, retrieval, and distribution of digital assets. DAM software solutions help enterprises to manage their digital contents such as images, videos, texts, and audio files. The software maintains a set of database records and each record contains metadata about the name of the file, its format, and other information about the file content and its use. DAM software is used to create and manage the database, thereby enabling organizations to store rich media in a cost-effective manner.
Technavio's analysts forecast the global DAM market to grow at a CAGR of 20.5% during the period 2017-2021.
Covered in this report
The report covers the present scenario and the growth prospects of the global DAM market for 2017-2021. To calculate the market size, the report considers the revenue generated from the sales of DAM software.The market is divided into the following segments based on geography:
Press Release
Technavio Announces the Publication of its Research Report – Global DAM Market 2017-2021
Technavio recognizes the following companies as the key players in the global DAM market: Adobe, Cognizant Technology Solutions, Dell EMC, HP, and IBM
Other Prominent Vendors in the market are: ADAM Software, Adgistics, Adnovate, Aetopia, Amazon, AssetBank, BrandWizard, Brandworkz, Bynder, Canto, Celum, ConceptShare, DMX, DuraSpace, Entermedia, Extensis, Filecamp, FotoWare, Genus, Globaledit, Google, GRR System, Digizuite, Hyland, MediaBeacon, MediaSilo, MediaValet, MerlinOne, Microsoft, North Plains Systems, Nuxeo, OpenText, Picturepark, Pixfolia, ResourceSpace, Saepio, WebDAM, Widen
Commenting on the report, an analyst from Technavio's team said: "The growing adoption of mobile devices and smartphones and the rise in popularity of mobile apps have increased the use of video management software, an essential revenue contributor to the DAM market. With the ubiquity of smartphones and tablets, video management software providers have started offering apps for mobile platforms such as iOS and Android. The adoption of mobility solutions in organizations to access enterprise documents through smart devices is also increasing rapidly."
According to the report, the increased use of mobile devices has created rich content for organizations. Organizations rely on digital media for most of their functions, and are adopting office document solutions to create rich media and create more content. This is driving organizations to shift from static to dynamic documents. Dynamic documents are interactive and include buttons, embedded calculations, links, and contents such as images, videos, drawings, embedded webpages, and forms. They can be easily created and secured by integrating them with existing document management systems. This helps organizations to streamline the communication of complex ideas and enables workers to deliver better proposals and presentations.
Further, the report states that data privacy and security risks are one of the major barriers for the adoption of cloud services in organizations, especially in the public cloud. Cloud security management is a challenging task for vendors as numerous instances of online hackings and security breaches have been discovered.
Companies Mentioned
Adobe, Cognizant Technology Solutions, Dell EMC, HP, IBM, ADAM Software, Adgistics, Adnovate, Aetopia, Amazon, AssetBank, BrandWizard, Brandworkz, Bynder, Canto, Celum, ConceptShare, DMX, DuraSpace, Entermedia, Extensis, Filecamp, FotoWare, Genus, Globaledit, Google, GRR System, Digizuite, Hyland, MediaBeacon, MediaSilo, MediaValet, MerlinOne, Microsoft, North Plains Systems, Nuxeo, OpenText, Picturepark, Pixfolia, ResourceSpace, Saepio, WebDAM, Widen
Learn how to effectively navigate the market research process to help guide your organization on the journey to success.Download eBook


text:
Monday, October 4, 2010
Gabriella's First Laugh
Testing testing! Please disregard hubby and my complete dorkiness. We were just so hyped that she was laughing oh so adorably!
Update: Yes it appears it works! Haha I'm always waaay too slow to the game in figuring out how to do things. :-)
2 comments:
- bbjoys said...
That is adorable!
- October 4, 2010 at 10:19 AM
- Sarah Swift said...
This is just the cutest thing that I have ever seen...ever!
- October 4, 2010 at 2:01 PM
Subscribe to: Post Comments (Atom)


text:
After reading The Foundation Trilogoy (after 20+ years when he started to write the rest of foundation stories), Isaac Asimov wrote :
"I read it with mounting uneasiness. I kept waiting for some-thing to happen, and nothing ever did. All three volumes, all the nearly quarter of a million words, consisted of thoughts and of conversations. No action. No physical suspense. What was all the fuss about then,? Why did everyone want more of that stuff? -- To be sure, I couldn't help but notice that I was turning the pages eagerly and that I was upset when I finished the book, and that I wanted more, but I was the author, for goodness' sake. you couldn't go by me."
Well, I like the stuff.
More from the same text.
"I was on the edge of deciding it was all a terrible mistake and of insisting on giving back the money, when (quite by accident, I swear) I came across some sentences by sceince-fiction writer and critic, James Gunn, who, in connection with the Foundation series, said, "Action and romance have little to do with the success of the Trilogy-- virtually all the action takes place offstage, and the romance is almost invisible -- but the stories provide a detective-story fascination with the permutations and reversals of ideas." Oh, well if what was needed were "permutations and reversals of ideas," then that I could supply."
I agree that most of Asimov's that I have read don't have much details about surroundings and he does not harp much on painting the characters but the stories are gripping neverteless. I just finished reading Foundation. I plan to read Inscrutable Americans before I start with third foundation story Foundation and Empire.


text:
Ubisoft released what happens with the third iteration of Donald Duck: Goin' Quackers (USA) Gamecube Iso. A title that originally debuted as a new concept on the Nintendo 64, Goin 'Quackers' saw a slight improvement for the PlayStation 2 and GameCube versions now. It is a platform game, to the bone – which is more geared towards a younger audience than anything else. It should give parents and eventually devote Goin 'Quackers Disney fans an eye.
You are in my webbed feet of one of the most captivating characters, Disney, Donald Duck. Only with your help, and his undying love for Daisy, you have the option to save them. Much more interesting than the plot, gameplay, of course. To say that is heavily dependent on Goin Quackers titles like Crash Bandicoot, Naughty Dog would be a huge understatement. It adheres to one of three formulas: to roll forward (top), side-scrolling, and sometimes vice versa-scrolling (in the direction of the screen). All this takes place in 3D, but it is the product of a 2D drawing in many ways. Move through the levels is self-explanatory, forcing him to jump over obstacles and enemies to avoid.
Processor= 733MHz
Graphics= 16MB
LikE uS on Facebook.com\haidersafdar110 : Click me


text:
You go, girls
The CBC is currently running contest for the best highschool rock band in the lower mainland.
It's now down to 10 bands including 2 girl fronted bands.
Mother Father is a mostly girl band (3 girls 1 guy)
Elsa is the singer/songwriter and her band is made up of guys.
They both have my vote. Rock and roll, like politics needs more women.


text:
It's April. I'm probably supposed to say "Happy Autism Awareness Month", but I'm not going to. Being autistic in April is hard. I don't need you to display blue lights for autism awareness. I don't need you to be aware of autism. Honestly. I don't.
Month: March 2017
I want to be wrong about Julia
Earlier this week I posted to my Facebook page a few thoughts about Sesame Street's new puppet, Julia, who "has autism". I'm putting those thoughts here, for reference, and following them with some further thoughts having now watched the new videos including Julia that have been added to the Sesame St website.
TeachMeet Human Rights
On Tuesday 14 March, I attended TeachMeet Human Rights in Sydney. It was a wonderful event, with many excellent presentations. I was honoured to be invited to present a 7 minute talk on Autism and Inclusion.
Inclusion in education is a human right, yet there is much about our education system that makes it inaccessible to autistic students. I spoke about the experience of autistic students and how to make schools and classrooms more welcoming and accessible, using strategies to avoid the practice of seclusion and restraint that we have seen occurring recently.
scared to stim
I spend so much of my time in public *not stimming*. I really wish I was more comfortable letting others see me move the way I want to….. need to.


text:
Hire A Court Room
Hire A Court Room is free HD wallpaper. This wallpaper was upload at December 14, 2018 upload by admin in .You can download it in your computer by clicking resolution image in Download by size:. Don't forget to rate and comment if you interest with this wallpaper.
Description wallpaper for Hire A Court Room
- Title: Hire A Court Room
- Author:
- Upload:
- Link: http://www.ucl.ac.uk/residences/information/ast/images/P6220008.JPG?hires
- Tag:
- Category: Uncategorized
- View: 0 View


text:
So, in lieu of a reflections post, I'm making brownies today and sharing the recipe here. This is just a re-post from an abandoned food blog collaboration amongst friends. I figured I may as well move some of the better recipes over to this space - enjoy!
This is my favorite brownie recipe ever. For me, the perfect brownie should be super indulgent. None of that dry cakey-ness that passes for brownies at the super market. The perfect brownie should have an ever so slightly crunchy 'skin' on the exterior that leads way to chewy melt-in-your-mouth chocolate goodness inside. It's ok if there are chocolate chips in there, but the base of the brownie should really be able to stand on its own.
Before I became a baker my favorite brownie mix was Ghiardelli's- those brownies embodied what a real brownie should be. Then I set foot in the kitchen and for years I absolutely loved the brownie recipe in Tartine- the use of chocolate in them instead of cocoa powder made for intensely rich brownies. But then these fell into my
Browned Butter Espresso Brownies
(Slightly adapted from Bon Appetit)
- 10 tablespoons unsalted butter
- 1 1/4 cups sugar
- 3/4 cup cocoa powder
- 1/4 teaspoon salt
- 1 teaspoon vanilla extract
- 2 teaspoons espresso or strong coffee
- 2 large eggs
- 1/3 cup + 1 tablespoon all-purpose flour
- Preheat the oven to 350 degrees Fahrenheit. Prepare an 8x8" square pan by lining it with foil.
- Melt the butter in a small saucepan; use a wooden spoon or spatula to stir the butter around occasionally. The butter will begin to boil, once this happens keep an eye on it and stir more frequently. The bubbles will get very big and then start to shrink back down and you'll start to see brown specks making their way up to the top. Once the brown specks appear start to scrape the bottom of the pan. When the butter is a light golden brown color, (this shouldn't take more than a minute or two) take the saucepan off the heat.
- In a large mixing bowl combine the sugar, cocoa powder, and salt with a whisk. Stir in the browned butter, making sure to scrape all the brown speckled goodness out from the bottom of the pan as well. Stir everything well with your wooden spoon or spatula and add the vanilla extract and espresso (or strong coffee), stirring well to incorporate. Add in the eggs and stir well to combine. Add the flour and stir just until incorporated.
- Pour the batter into the prepared pan and smooth the top with a spatula. Bake for 25 minutes, or until the top starts to crack slightly. Let cool completely before cutting.
- Enjoy! Brownies will keep for a few days in an airtight container; they'll keep even longer in the refrigerator.


text:
Introduction To Before The Dawn
Before The Dawn is a multiplayer horror game, where a slasher is put to a mission to hunt and kill 7 survivors and the survivors objective is(obviously) surviving .
The game will have customization options for survivors (items,hairstyles,etc)
As for slashers skins will be available for example (Slender-man=Xmas Slender-man)
Im Open to suggestions !
Oh and by the way it wont be easy for slashers if someone makes it to the firetower
(look at image for inspection)
Leave a comment
Log in with itch.io to leave a comment.


text:
All right, so I know in a recent post, I mentioned that I usually don't keep my dolls in their original fashion. Well, this doll is another exception. Even though her fashion is a bit more on the monochromatic side, I think it suits her beautiful carrot colored hair and adorable freckled face just fine. Don't you?
FR Nippon Posh Girl Misaki


text:
* The race will start "off the trailer". There will be no shakedown round nor any test passes permitted. The driver nor the car may make a pass the day of the race at the track we are racing at that day.
* All entries limited to one power adder.
* Instant green with autostart tree will be used.
* The only competition fowls will be, red lighting, crossing or touching the center line, startup timeout.
* If both competitors foul, first is worse and will result in the loss.
* Negotiated starts allowed. Racers may set out their opponent by giving the back tire and/or agree to go on their leave.
KOTS Starter must be informed before staging.
* After callouts are made before the first round, accepted or refused, the remaining racers will draw for pairing.
* No callouts permitted after 1st round.
* If a racer is broke, he will not be available for call outs or card draw.
* Racers may only receive one drawn bye run. If a racer draws a second bye run card, the cards will be re-shuffled and everyone will draw again.
* All bye runs (drawn or competition) must be a legal FULL THROTTLE pass. Failure to make a full throttle pass will result in disqualification and the racer will be out.
* Every car paired by callout has to at least do a burnout or his opponent will be paired with any available racer who has a bye. If there are no available cars to pair with the able car, the able car will be allowed the bye run. This does not apply to a drawn pairing that has a car that is unable to burnout.
* Any bye runs must go down last after all paired runs.
* Red card in each pair gets lane choice.
* Bye runs are determined by odd card. A racer can draw the bye run more than once.
* Racers are not guaranteed to hear the call to the scales or lanes. There will be a set schedule posted for what time to be at the scales suited up and ready to draw cards. Racers must be there at the specified time ready to go. If a racer isn't there by that time, the official will draw last card(s) for the absent driver(s). After callouts and card draw pairing is done, racers have 5 minutes to get suited up and strapped in. The first pair will be sent to the burnout box as soon as it is cleared by the track officials. Each racer must be in or rolling in by the time the pair ahead has turned off the track. If a racer has a failure to start or other problem, they will be given 1 minutes to resolve the problem. After the 1 minute, they will be disqualified. Once the burnouts are done, racers may stage at their leisure as long as the car is not disabled and not being worked on. If it is, the 1-minute rule applies.
KOTS action only at Motor Mile Dragway!
Thanks to all the racers fans and sponsors for a
memorable 14 years.
Class Rules
Street Race 2018 (edited 5-30-18)
Off the Trailer, Heads UP, Pro Tree, Draw For Pairings, No Times Shown
* SB stock valve angle, non raised intake runner – 2650. See ENGINE section
* SB non-stock valve angle or SVA with raised intake runner – 2700
- SB stock OEM block, 8.2 deck or modular - deduct 100lbs
* BB nitrous, aftermarket block, stock bore space, stock valve angle +-2°, non-raised intake runner up to 588ci – 3100 See ENGINE section
* BB nitrous, aftermarket block, stock bore space, stock valve angle +-2°, non-raised intake runner 589 - 638ci – 3250 See ENGINE section
- BB stock OEM passenger vehicle block - deduct 150lbs
+ Head Hunter, Victor or equivalent conventional BB heads add 75
+ Ford "A" heads by any manufacturer add 75lbs.
- Deduct 50lbs for true Holley style 4150 four venturi carburetors on 4150 cast manifolds. 4150 throttle bodies do not receive weight break.
+ Add 50lbs for a single stage fogger instead of a plate system. Permitted on small blocks only.
+ Small blocks may add a second stage with a 50lb penalty.
- Single entry 1 N2O / 1 fuel or single N2O dry plate deduct 50 lbs.
- Deduct 50lbs if running full exhaust to at least the rear end housing pinion U-joint.
+ Add 50lbs for any small block with more than 440ci up to 460ci.
* YSI cast wheel - 2700
* YSI billet wheel – 2800
* F1A-91, V-30 94A & 6-71 carbed roots – 2850
* F1C-91 & conventional roots 6-71 – 2900
* F1R and 8-71 carbed roots - 3200
+ Add 50lbs for non-stock valve angle or raised intake runner heads
- Deduct 50lbs for belt driven centrifugal.
+ Add 50lb if running methanol as primary fuel
- Deduct 50lbs if running full exhaust to at least the rear end housing pinion U-joint.
* T-76 96mm max turbine, (S400 chassis only) 2900
* T-76 any mid frame chassis, any turbine 3100
* Borg Warner S488 – 3100 (no other turbos over 76mm permitted, S488 not permitted methanol, water injection or air to water intercooler)
+ Add 50lbs for non-stock valve angle or raised intake runner heads
+ Add 50lb if running methanol as primary fuel
- Deduct 50lbs if running full exhaust to at least the rear end housing pinion U-joint.
* SB standard bore space – No minimum weight.
* SB non-standard bore space or B/O/P - 2400
* BB with conventional heads within 6 degrees of stock valve angle 2500
* BB with non-conventional/Pro Stock/Symmetrical type cylinder heads 2750
+ Cast tunnel ram/sheet metal/dual carbs on SB N/A add 50
* Standard bore space engines only.
* Must retain OEM frame from the strut towers or forward most suspension bolt to driver's footwell.
* Stock style front suspension only unless elsewhere noted. Bolt in aftermarket K-Members permitted.
* Must retain factory front strut towers if it came with them from the factory.
* Bolt on front Smith Racecraft type front clips and Mustang II conversions permitted on pre-1979 vehicles that retain the stock floor pan to behind the driver's seat.
* Must have working headlights & tail lights.
* Firewall must remain intact and in the OEM location.
* Must retain stock wheelbase +/- 1"
* Maximum front end overhang measured from front wheel center-line, 45" or stock from OEM.
* No beam tripper / flag / extender permitted.
* All entries except naturally aspirated must utilize a single carb or throttle body & cast intake manifold.
* No billet heads or blocks permitted except on naturally aspirated entries.
* Maximum cubic inch for small blocks 460ci.
* Maximum cubic inch for big blocks 638ci.
+ Stock valve angle non-raised intake runner entries must not alter valve angle in any way including angle milling. No offset rocker arms. No altering intake runner floor height. No welding or epoxy in intake runner floor except for repairs. Repairs in maximum of 2 cylinders per head and must match profile of un-repaired runners. If you have any of these modifications, add 50lbs.
* Any automatic transmission type permitted.
* Lock up converters are prohibited.
* Any commercially available gasoline based race or pump fuel permitted . Any commercially available ethanol or ethanol gasoline blend permitted. Methanol entries permitted only VP M1 or Renegade Pro. No other type fuels permitted.
* Foggers are limited to a maximum two .125" orifice solenoids or one of any size.
* Big blocks limited to a plate system only.
* Push systems or cold nitrous systems prohibited.
* Maximum cubic inches SB-460ci and BB-638ci. Owner may be asked to remove a cylinder head to check bore and stroke, valve angle, ect. This will only be done after the final round. Refusal to do so if asked will result in forfeiture of winnings and points.
* 76mm compressor inducer cannot exceed 76.2mm tip to tip and the compressor exducer cannot exceed 116 mm.
* S488 entries allowed as manufactured by Borg Warner only.
* Small blocks only.
* All turbocharger entries must be willing to remove the compressor cover for tech inspection. This will only be done after the final round. Refusal to do so if asked will result in forfeiture of winnings and points.
* Permitted blowers - Procharger F-1R, Vortech V-30 94B, or smaller
* Roots blown may use 2 carbs
* Any OEM production vehicle stock blowers permitted.
* Small blocks only.
* Any suspension permitted.
* Wheelie bars are prohibited.
* All combos limited to a 275/60-15 or 28x10.5 (non-W).
* 28X10.5W or 325/50R15 permitted with a 50lb penalty.
* 26x8.5, MT3553 or MT3453 drive tires may deduct 50lbs.


text:
Rain Jacket | Dress (Similar Style Here) | Sandals | Purse
T-Shirt (Similar Style Here) | Shorts | Sandals
Over-the Knee Boots | Skirt | Jeans
Top: Similar Style Here and Here
Chanel Foundation | Laura Mercier Tinted Moisturizer | Sunglasses | Earrings (Similar Style Here)
After about a month long hiatus from blogging, I'm finally back. Stress has definitely gotten the best of over the last few weeks. I've been in one of my busiest times at work and I haven't been able to think about much else. Luckily, we are wrapping up our projects and I'm finally able to get back into my daily routines.
Which means August and most of September have been fairly boring. I've just been working, catching up on sleep and trying to stay sane. But amongst all of the crazy, there has been so much good happening. I feel incredibly blessed to live the life that I do! Now, I'm gearing up for a busy personal schedule to finish out September and October.
What have y'all been up to lately?
Be sure to follow me on Facebook, Twitter, Instagram and Pinterest!


text: I have horrible eye sight ! I have consulted dozens of doctors about lasik and they feel I'm a good candidate, but the thought of it scares me to death :shame: After all it is your eyes! Is anyone else considering having it or has had it. I'd love to hear any experiences. Thanks guys!


text:
Why Book With Us
- Best Rate Guaranteed
- No Hidden Fees
- Daily Yoga Class
- 15% discount for Restaurant & Spa
The place to be in UbudRebmania
A lot more than we expected. Then again, everything is in Bali. Great people, very helpful. Always smiling. The room is AMAZING! We had a problem with...View More