I’m honored to be recognized as SQL Server MVP for the 2nd time in row and thank you Microsoft to honored me again! Thank you also to our great SQL Community and SQL Family!
Announced and available for download the SQL Server 2014 CTP2:
…and something that is very welcome for the community is the live from the PASS Summit 2013 is here:
SQL Saturday Kosovo #225, happened last week and I’m very happy that we did for the first time in Balkan region!
Special thanks goes to the sponsors Ipko Foundation, PASS, Microsoft, ICK (Innovation Center Kosovo), Redgate, Wrox, PluralSight, xSQL Software, Digjitale.com, Nescafe as well as Albanian SQL Server Users Group > ALSSUG.
We had just one track this time and with great speakers & their strong experience ( Dejan Sarka, Niko Neugebauer, Mladen Prajdic, Turgay Sahtiyan and Matija Lah), and for more details about their presentations you can find here.
As first time SQL Saturday in our country, the event went well and we had 118 registered attendees and 82 were present in the event for all the day of the 18th May, 2013. Thanks to the Niko as my mentor for this successfully event and I need to say thank you also to my friends who helped me a lot during the organization of the event (Betim Drenica, Florim Maxhuni, Milot Rexhepi).
Starting to look forward for the next one, soon! … stay tuned!
Some of the photos of our event:
I’m so exciting to announce that the SQL Saturday Kosovo is going to be held on May 18, 2013 and it’s our firs time SQL Saturday where I will speak also. However I’ve started the challenge journey to organize things properly. The most important thing here for our local community is that the list of the speakers will be all the MVPs for SQL Server.
More information will be in our official website at SQL Saturday #225 Kosovo.
SQL Server is in the Cloud as Windows Azure SQL Database, but in the Cloud, still have some limitations that are not supported and here are some of them (short info):
SQL Server 2008 R2 features that are not supported by Azure SQL Database:
- SQL Server Utility
- Master Data Services
SQL Server 2008 features that are not supported by Azure SQL Database:
- Change Data Capture
- Data Auditing
- Data Compression
- Extended Events
- Filestream Data
- Integrated Full-Text Search
- Policy-Base Management
- Resource Governor
- SQL Server Replication
- Transparent Data Encryption
SQL Server 2005 features that are not supported by Azure SQL Database
- Common Language Runtime (CLR and CLR User-Defined Types)
- Database Mirroring
- Service Broker
- Table Partitioning
- XML Indexing
Other features that are not supported as well:
- Backup and Restore
- Extended Store Procedure
- SQL Server Agent
For more information you can check here.
An error that is known how to solve it, I was the victim today with it and when I started the SSMS, I saw that error. I’m telling you here how to fix it as fast info and references from MS.
This error usually comes when your DB no longer exists or it is in suspect mode or has been detached or offline etc, and you will have the pop-up message with error description and the number 4064:
Ok, as you can see the user Blue cannot connect in the default database and the login failed!
Fixing this error is really easy, so you can try again to login with that user but first before to Connect, you must go to the Options that is in right corner below and you will be asked for the Connection Properties on the second tab of the login dialog box and you must enter the master database in the drop-down box, see the fig below and hit Connect:
Now you will be able to connect in your SQL Server. So what’s next!? As I said, some of the reason why it happened are described above, so now you can check for the correct DB that must be as default DB of that user. After that to be sure for the next connection you need to change the default DB via T-SQL or GUI:
GUI: Open the SSMS on the right, you have object Explorer, go to Security > Logins > Find your login and right click > Properties. You will have the dialog box like shown in the fig below.
Or you can use the T-SQL script:
ALTER LOGIN [Blue] WITH DEFAULT_DATABASE=[TESTING2];
For more info about this error, you can check here.
Being part of the SQL Server community is a fantastic thing! Not only do you have the technical support of a global community, but you also have the strength the SQL Server community behind you offline as well! We know the power of the community – we’ve seen the #SQLFamily reach out to each other in the virtual world and beyond to lend a helping hand, on technical matters or not!