Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2014 SP2, 2016 SP1 and 2017 RTM:
…Stay Tuned! 🙂
Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2016 RTM and SP1 and 2017 RTM,:
Starting from this month, we finally get AdventureWorks on github! The direct location is https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
Stay Tuned! 🙂
Directly from the SQL Server Release Service blog, here the latest updates for SQL Server 2016 RTM & SP1:
Starting with SQL Server 2017, the SQL Server releases will follow the Modern Servicing Model, read more here.
Stay Tuned! 🙂
It’s September, a month whose the start is the beginning of many things, especially in Italy. Kids start over the schools, Companies invest, and what about projects and events?
You know, I really love to do both. But in this post I’d let you know how I feel proud about my work in the past four years. Thanks to the help of my employees and co-ops, I did organise four SQL Saturdays in Parma (2014/355, 2015/462 and 2016/566), making our small town a big SQL Server City. Who would’ve thought it? Yes, maybe in my mind, there was something that pushed me to try, but it could have an epic fail. However, I did it, and it was an astonishing set of records. It started as a quest in an Role Play game, and now we’re in front of this great SQL Saturday. Something to be really proud of.
Two years ago, I felt the need to add a new event, which would have to support a new way of thinking about the IT roles that I was aware of. And that was when DevOps came out. A new buzzword that needed to get a deep explanation, in terms of culture and approach. Combining my passion to The Simpsons series (especially considering Homer Simpson) and DevOps stuff, I’ve made up DevOpsHeroes, whose acronym is DOH, the Homer’s exclamation. And now, for the second year, Developers, IT Operations people, DBAs and PMOs will share their experience about how to integrate, cooperate and make IT world more productive. Another event, another thing to be proud of.
After the introduction, let me give you some important details about these events, sorted by upcoming date:
DevOpsHeroes 2017 – Parma (http://www.devops-heroes.net/)
Sql Saturday 2017 – Parma (http://www.sqlsaturday.com/675)
However, this year I’d to thank my helpers at Engage IT Services Srl, the great support of Upgrade Srl (Andrea, Federica and Riccardo, that organised with us the DOH event), HPE and also many communities, like DotDotNet.org and mostly our great community GetLatestVersion.it. A special thanks goes to Windowserver.it, which will record sessions, live streaming and interviews. Speaking about SQLSaturday, the sponsor page depicts how the event is supported. A big thank goes to all of them!
What the future will reserve to us in Parma? I think that I could try to add another event, maybe on IoT topics, because I feel that the world will change following that direction and also, hopefully, my newborn Giulio will play with my and some robot 🙂
Alternatives could be changing the format, like with a TED event or something like it. Who knows? I’m pretty sure that I’ll get a lot of help from now on. This year has been a demonstration of it. I started alone, and now we work in five. The last thing to be proud of. Wonderful!
To repair Suspect database error in MS SQL 2005, 2008, 2012, 2014, 2016 and 2017 read this article to recover SQL Server database from Suspect mode.
Microsoft SQL Server serves as a storehouse for data that is needed for different software applications on a single system or across a network. Sometimes a user may face a situation where a database in the SQL Server instance currently under running state is marked as Suspect. This condition will lead to a failure in creating a connection with the database. Such a database which is tagged as Suspect can be accessed by removing the causes for this problem. The forthcoming article will discuss the causes for this problem to occur and the possible solutions to repair suspect database from SQL Server 2005, 2008, & 2012.
The error message shown to user is somewhat similar to the one given below
Starting up database ‘abc_d’.
Error: 9003, Severity: 17, State: 5.
The log scan number (189623:15:2) passed to log scan in database ‘abc_d’ is not valid.
The above-mentioned error shows that there is some corruption of the log file(.ldf) and does not adhere to the data file(.mdf). Other error messages can also be shown depending upon the cause due to which the database has been categorized as Suspect.
User queries help in getting a better idea about the problem and to recover SQL database.
“I am currently using SQL Server 2008 edition on my Windows 7 system and there are many applications of mine that are dependant on it. Recently I have been facing difficulties in connecting my applications to some of my Databases and they are being shown as Suspect. Kindly guide me to recover SQL database from Suspect mode.”
There are a number of reasons why SQL Server marks a particular Database as Suspect.
Some of these reasons are mentioned as follows
There exist a number of techniques for solving the issue of Suspect SQL database and broadly they can be classified as Manual and Automated. The upcoming section will try and explain a Manual technique for achieving this goal.
Quick Tip: If you want to skip the tedious & complex manual approach then it is highly advised to use an automatic tool such as SQL Recovery to efficiently recover SQL database from Suspect mode
Implement the steps given below to recover Suspect SQL Server Database and to access important data.
1. Bring Database in Emergency Mode using the following code
ALTER DATABASE abc_d SET EMERGENCY
2. Execute DBCC CHECKDB command.
This will scan and check the physical and logical integrity of objects present in the marked database
DBCC CHECKDB (abc_d )
3. Bring the Database in Single Mode using the below-mentioned query
ALTER DATABASE abc_d SET SINGLE_USER WITH ROLLBACK IMMEDIATE
4. After the Database is in Single Mode, execute the following code to repair suspect database
DBCC CHECKDB (abc_d, REPAIR_ALLOW_DATA_LOSS)
5. Lastly, restore Multiple access to the database by executing the query
ALTER DATABASE abc_d SET MULTI_USER
The Suspect database problem is a common issue faced by users of SQL Server database and it has various causes. There is a set of TSQL commands to overcome this error but it poses many issues during implementation. It is better to use automated tools designed specifically for this purpose to repair suspect database.