It's been a little over six weeks since I last logged into SQLServerCentral, but I'm back from my sabbatical. Relaxed, refreshed, charged, and ready for work. And back to work it is, with my sabbatical ending with a trip to the UK for a few days at the Red Gate office and then speaking at SQL Bits. It feels like the start of a race, going from zero to full speed as fast as possible.
I'm ready to come back to work. I enjoyed the time off, and certainly had the chance to view the world in a much different light, interacting with people and projects in a way I haven't done in decades. But I also realized that the SQLServerCentral, and larger SQL Server/#SQLFamily, communities are close and engaging in a way that I don't see in the rest of the world. We have something special in our little technology niche, and I hope all of you appreciate it.
The time off also helped verify something I've thought for a long time: Red Gate is a fantastic company. The highest complement I could pay the is that they run the kind of company I'd want to run if I started another business. Talking with so many people from other industries and companies exposes the contrast in just how much difference a good company makes to a job.
The sabbatical is a nice perk, and one I'd certainly recommend to employers that really care about retaining their employees. I'm not confident many managers will agree, but I'd say that it's just the type of refreshing break that might help you get better work from those you depend on use their minds to grow your business.
Although SQL Data Types seem to cause a lot of grief for database developers and can be tricky in their use, we seem to be expected to know all about them, and so it is embarrassing to ask questions about them in forums. Rob Sheldon continues in his mission to answer all those questions that we hesitate to ask. More »
SQL in the City is coming back to London and Seattle in 2014. The London event will take place on October 24 (before Tech Ed Europe) and in Seattle on November 3 (before PASS Summit). Keep an eye on the event website and @redgate for updates. More »
Question of the Day
Today's Question (by Steve Jones):
Can I create a regular table in tempdb?
create table MyTable
, mychar varchar(200)
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
1 point in this category: T-SQL.
We'd love to give you credit for your own question and answer.
To submit a QOTD, simply log in to the
SQL Server 2012 brought in some great new features and one of the important ones is scalability and performance via AlwaysOn. AlwaysOn is a superset feature and is a combination of many things you will learn about. As the language suggests, this technology achieves a SQL Server infrastructure that can be "always on". For businesses that run 24x7 downtime means the loss of business. This type of risk is out of the question for these businesses. This book discusses in detail the concepts of SQL Server AlwaysOn starting from the basics.
Yesterday's Question of the Day
(by Phil Factor):
A database that is important to the organisation has become damaged and gone offline. You have the task of recovering it. You determine that it is set to the full recovery model, has a weekly full backup, and a daily differential backup. In addition it has an hourly transaction log backup. What should be the first step in recovering this database?
Answer: Try to take a tail-log backup by using the WITH CONTINUE_AFTER_ERROR option
If a database is offline and fails to start and you need to restore the database, first back up the tail of the log. Because no transactions can occur at this time, using the WITH NORECOVERY is optional. If a database is damaged, try to take a tail-log backup by using the WITH CONTINUE_AFTER_ERROR option of the BACKUP statement. (The NO_TRUNCATE option of BACKUP LOG is equivalent to specifying both COPY_ONLY and CONTINUE_AFTER_ERROR. COPY_ONLY specifies that the backup is a copy-only backup, which isn't a requirement here.)
If a tail-log backup cannot be created, any transactions committed after the latest log backup are lost.
(The TRUNCATE_ONLY isn't part of a restore procedure and has been discontinued.)
Since we have sys.dm_sql_referenced_entities, dynamic view, which contains the dependency tree, I gave it a try and used it to display all objects in xml format.
The stored procedure uses the view to retrieve the hierarchy, stores it in a table (#tree) which is later traversed using recursive CTE.
Just create the stored procedure, pass it an object name and expand the xml result.
I didn't include check for the level of recursion, but we all know that it'll break if the depth reaches 32. I don't mean to preach, but if any of your sql objects have dependency that deep, you're in trouble.
dk will take a look at it
In my new environment we have very big database. This is my first time working with large database. They asking...
mac os server
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.