First of all Happy new year to everyone. Hope it should be a good start for everyone. We have planned user group meeting this month. Going to start with fresh look on SQL Server Denali aka SQL Server 2012. SQL Server 2012 is expected to reach market by this year, so this month topic is based on SQL Server 2012 only. Venue and topic details below
Diwali Season Starts now.. We have planned session for this month before Diwali so that you guys are stuffed with information before going for festival. Session details are below
Next session is ready for this month. We skipped last month as we had a session on first week of August so lets have a wonderful UG this time
We had wonderful session this month. I reached the venue on time and I could see some of the participants and after some time everyone started reaching the venue. I really appreciate all the participants who came to the session , it’s really nice to see you guys. I have started my session and then followed by Amit Bansal and then by Madhi. Surprising we had a volunteer speaker who wanted to take a 10 min session.
We are back again this month. We are going to post pone this month UG a week , that is to first week of August. You know why ? We have a fantastic SQL Server guest for UG this month. He voluntarily wanted to take a session for Chennai folks. It’s none other than the Mr. Amit Bansal. He will be visiting Chennai first week of August , we have postponed our UG on first weekend of August so that Amit can gave a wonderful session for you folks.
VidhyaSagar
| #
Thanks Ashish, I’ve updated the script.
Ashish
| #
I was just searching some trace related articles and gone through your article. Found one incorrect information,
to disable the trace, the command should be
dbcc traceoff (….)
you might have by mistake mentioned it as traceon for disabling as well.
Ben
| #
I remember having to write a complicated procedure to do the same thing recently. This will be nice to use with a web app to only return a small subset. I think this will improve the speed especially when the entire result set is very large.
namanthakral
| #
got errors after executing this trigger
“SQL SERVER – Fix : Error : 17892 Logon failed for login due to trigger execution. Changed database context to ‘master’.”
and was really stucked in this mess but DAC saved my life
C:\Users\Administrator>sqlcmd -S LocalHost -d master -A
1> DROP TRIGGER block_ipaddress ON ALL SERVER
2> go
SQL NET » New Feature in SQL Server 2012
| #
[...] CLICK HERE TO READ THE ARTICLE [...]