links for 2009-12-18

by swjohnson 12/18/2009 5:01:00 PM

What I learned on 2009-12-16

by swjohnson 12/16/2009 5:05:00 PM

What I learned on 2009-12-08

by swjohnson 12/8/2009 5:02:00 PM

SQL Server 2005 -- Database 'XXXXX' is in transition -- Error 952

by swjohnson 11/24/2009 4:46:00 AM

We had a really weird one today for just one database on our server that has about 350 user databases on it.  We got a call from a software engineer and he couldn't access his database XXXXX and the website was also reporting connection errors.  He said he was doing some data exports from the database and was getting weird issues (don't you just love those helpful technical descriptions from the users who should know better).  

We signed in to SQL Server Management Studio (SSMS) and sure enough, we couldn't hit the DB either but all the other databases on the server were accessible and running fine.  (scratching my head here...)  The error message in SSMS was

   Msg 952, Level 16, State 1, Line 1
   Database 'XXXXX' is in transition. Try the statement later. 

and the SQL Server Logs showed

   SPID 465 - Setting database option OFFLINE to ON for database XXXXX. 

When I tried to look at the Activity Monitor, it returned an error with the same message and using select * from sys.sysprocesses returned the same error message.  (more head scratching here...)  A quick Google search turned up several possible solutions and only one appealed to me--find and kill the offending user's SSMS session. The other option was to restart the SQL Server service--the survey says "AHHHNNNNNT".  

First, I had the software engineer exit SSMS.  For some reason, as soon as the user's SSMS process terminated, we could access the database and Activity Monitor.  Second, I then killed all other SPID's the user had.  Finally, I had our hosting operations team kill any Citrix session the user may have had open in the background.   Basically, I just made sure everything was terminated for this user and then everyone was able to access the database again.    My hypothesis is that the SSMS process became corrupt and this was causing the error.     

Resources:

http://social.msdn.microsoft.com/forums/en-US/sqlgetstarted/thread/e779230a-87bc-4cee-b223-98a029097dc1/  

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=115305

links for 2009-11-18

by swjohnson 11/18/2009 5:05:37 PM
  • SSAS includes a tool called the Deployment Wizard which will do exactly what you need.  The Deployment Wizard uses the artifacts created by your SSAS project and can perform the deployment and/or generate an XMLA script that can be used to perform the deployment at a later time.  XMLA stands for XML for Analysis Services and it is the native protocol used by SSAS.  All commands sent to SSAS are in the XMLA format.  An XMLA script is an XML file.  The ability to generate the XMLA script allows the developer to provide the IT team what they need to perform the deployment.  In this tip we will review the BIDS artifacts, walk through the Deployment Wizard to create the XMLA script, then show the options to execute the script.

Tags:

Another Free Tool...DBSophic Trace Analyzer...

by swjohnson 11/18/2009 3:44:00 PM
I do lots of profiling on various SQL Server systems and I came across DBSophic's SQL Trace Analyzer today.  I have downloaded and ran a few small profiles against and I really liked what I saw.  Tomorrow, I will be running some larger traces against it and see how it stacks up.  

links for 2009-11-06

by swjohnson 11/6/2009 5:04:03 PM

Tags:

links for 2009-11-05

by swjohnson 11/5/2009 5:33:49 PM

Tags:

links for 2009-10-31

by swjohnson 10/31/2009 5:02:20 PM

Tags:

links for 2009-10-30

by swjohnson 10/30/2009 5:06:00 PM

Tags:


Feeds