Wednesday, February 27, 2013

[SQL 2012] abrupt SQL Server restarts

[SQL 2012] abrupt SQL Server restarts


abrupt SQL Server restarts

Posted: 26 Feb 2013 08:18 PM PST

I have recently installed a SQL Server 2012 instance and have deployed a few databases on it.However, the server is restaring abruptly and nothing is clear from SQL Server logs.I see some wierd messages in event viewer like the below ones:Product: SQL Server 2012 Database Engine Services - Update '{402234FB3-7241-4B6D-83A4-92323BCS3DC8}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 2 user registry handles leaked from \Registry\User\S-1-5-80-1651743498233-604422593-37299121234-4324324703093-311232196992:Process 6056 (\Device\HarddiskVolume3\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-80-16517234234233-12334442-3729906164-4251703093-3124596992\Control Panel\InternationalProcess 6044 (\Device\HarddiskVolume4\Program Files\Microsoft SQL Server\MSSQL11.DEV\MSSQL\Binn\fdhost.exe) has opened key \REGISTRY\USER\S-1-5-80-1651231233-6021312593-31232139906164-42556757573093-3124596992\Control Panel\InternationalWhats the reason for the SQL restart? Would a Service pack upgrade help?

Extended Events Export to table

Posted: 26 Feb 2013 07:12 PM PST

Hi AllI kicked off a queries detail tracking(using an event file as data storage) extended events on my pre-prod environment yesterday which I ran for 5-6 hours yesterday amd then stopped it. Quite a lot of data was created(30gb) in *.xel files which was fine as it was being put on a large backup driveBefore I left work yesterday I wanted to export all this information to a table in order for me to do some tuning analysis. So I went right click->view target data then locked my computer and went home.I came in this morning and was alarmed to find the c:\ drive out of space! Awesome :)When you perform the above action SSMS creates a file on the folder C:\Users\[username]\AppData\Local\Temp\2 that is holding temporary results of what is on the view target data window.I cant find a way to import the extended events xel files into a table in SSMS without doing the view target data thing? Is there an easy way to do this?ThanksChris

SQL Agent cannot start

Posted: 03 Oct 2012 02:13 AM PDT

After clean install of SQL Server 2012 RTM Developer edition, SQL Agent fails to start with "access denied" error.The default user setup has set is "NT SERVICE\SQLSERVERAGENT".When I change the agent user to LOCALSYSTEM, it can start without problems.I checked windows permission in local security policy for "NT SERVICE\SQLSERVERAGENT", and they are ok. Also, that account is sysadmin in sql. Obviously, some permission is not set correctly by installer, but I don't know what else to check.

SQL View not Exporting to Excel via DTS Package

Posted: 26 Feb 2013 02:45 AM PST

Hi I hope I am posting this to the correct forum.I fairly new to SQL Server and SSDT so here goes.I have a package that does the following steps:1. File system task that delete a backup file.2. File system task Renames the current file to backup file name.3. File system task that copies a existing file that only has headers in it for the extract of the data for a view.4. Dataflow task that inserts the data from the SQL to the Excel file in step 3. [color=#925d400]This is where the process breaks, the data is not inserted into the Excel file.[/color]There are 4 more steps that do the same thing as steps 1-4 above the only difference is it is on different files in the same location as steps 1-4 and those 4 steps complete without any issues.I am wondering if anyone has come across this problem before and how they resolved the issue.BTW when I run the package from my local SSDT the process runs and works without any issues. The failure only happens when the package is deployed on the SQL Server.If this isn't the right forum for this question. Please let me know the correct forum and I will be happy to post it there.ThanksNB

No comments:

Post a Comment

Search This Blog