- Visual Studio 2012 puts the “Ug!” in “Ugly”
- What a Year Brings
- Installing Sharepoint 2010 Farm on a Single VMWare VM
- Access 2010: A Rare Second Chance
- Waaaay too busy to post….
- I’ll just leave this here…..
- Can’t Save Sharepoint Doc Even with proper permissions
- Can I Kick It? Yes I Can!
- Lessons Learned from a Cheese Curd maker
- I’ll just leave this here….
- So You Want To Be An Air Traffic Controller?
- A Toast to Brent!
- Does “Denali” portend the end of OLAP?
- Anti-Oopsie Tip of the Day
- The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped.
- That DBA Look…
- TSQL Cursor Options
- 2008 != 2008R2
- SSMS Tab Bar is Nearly Useless
- I Cannot Believe How Buggy MS Access Has Become!
Category Archives: Procedures
I think I’m all done with this article. Well, maybe not. Microsoft seem to have taken the really bad Metro idea from Windows 8 and pushed it onto VS2012 also. All dull grey. VS2010 had a classy, visually “easy upon … Continue reading
If you are like most of us Sharepoint Admins (or SQL Server DBA’s in a Cluster Environment, for that matter), you will often want to run through a new service implementation on a Virtual Machine taking a snapshot and running the … Continue reading
Ran into this today. User can open and edit, but cannot then save an excel spreadsheet from a document library. Error msg says “document is read only”. But it isn’t read only. And the user has proper permissions to the … Continue reading
An excellent discussion on manipulating Excel Spreadsheets directly from SQL Server TSQL! http://www.simple-talk.com/sql/t-sql-programming/sql-server-excel-workbench/
I owe this to Brent Ozar. I’ve been a “dba” for a long, long time. But not an “official” DBA. It was always an adjunct function to my regular developer duties. I’ve been a long time “Development DBA”. In 2008, … Continue reading
The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped.
When attempting to drop a database user, you get the following message: One place to begin is your stored procedures. The database user has likley been used in the “WITH EXECUTE AS” option in a stored procedure: Hey, … Continue reading