When you get used to issuing commands on the linux/unix prompt, one thing you’re sure to miss is that when you close and open another terminal or command line window the history is gone,

With a tip from the guys at powershell magazin, you can get that working for windows powershell.

That way you can always remember what have been up to recently on the command line.

You better think again. If you consider doing any of the following changes:

  • Adding database triggers
  • Adding new indexes or changing existing indexes within tables
  • Adding, changing, or deleting any primary or foreign key relationships
  • Changing or deleting existing stored procedures
  • Calling existing stored procedures directly, except as described in the SharePoint Protocols documentation
  • Adding new stored procedures
  • Adding, changing, or deleting any data in any table of any of the databases for the products that are listed in the “Applies to” section
  • Adding, changing, or deleting any columns in any table of any of the databases for the products that are listed in the “Applies to” section
  • Making any modification to the database schema
  • Adding tables to any of the databases for the products that are listed in the “Applies to” section
  • Changing the database collation
  • Running DBCC_CHECKDB WITH REPAIR_ALLOW_DATA_LOSS (However, running DBCC_CHECKDB WITH REPAIR_FAST and REPAIR_REBUILD is supported, as these commands only update the indexes of the associated database.)
  • Enabling SQL Server change data capture (CDC)
  • Enabling SQL Server transactional replication
  • Enabling SQL Server merge replication

And these unsupported database modifications are discovered during a support call then, to get support back… just perform a database restoration from the last known good backup that did not include the database modifications.

I really don’t get the implications of creating new stored procedures or indexes. It’ s perfectly common for a DBA to sometimes add non-business related objects to get some usage overview.

Hope I never get called to solve performance issues on a Sharepoint MSSQL database. I might inadvertently ruin their support eligibility.

Source: here.

Useful stuff.

Nice article with an Excel spreadsheet attached with all the DMVs and identifuing changes made from MSSQL 2012 to 2014.

This is a must for sysadmin … otherwise you just have to open RDP sessions all the time.

Remote Server Administration Tools for Windows 8.1 includes Server Manager, Microsoft Management Console (MMC) snap-ins, consoles, Windows PowerShell cmdlets and providers, and command-line tools for managing roles and features that run on Windows Server 2012 and Windows Server 2012 R2. 

This enables IT administrators to manage roles and features that are installed on computers that are running Windows Server 2012 or Windows Server 2012 R2 from a remote computer that is running Windows 8.1 Pro or Windows 8.1 Enterprise.

An old acquaintance of mine wrote a post on his blog where he mentions the weather and having having the flu coupled with uninspiring work result on a lack of good mood.

I don’t have the flu… guess my work is more uninspiring because my mood is way bad.


I get that companies have to find revenue somewhere. Some might “give” you free cloud services and have invasive technology, usage terms or conditions. Some might just be earnest about it and tell you to buy their stuff and in return they’ll try to keep up and give you some great value added services.

The guy who wrote this post must not be a DBA: “Just let the database do the processing and fetch only the results …”