![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Jul. 30th, 2008 01:50 pmWow, SQL Server Express 2005, with Management Studio Express, is secretly also kind of fucking shiny today.
(no subject)
Sep. 27th, 2007 09:11 amYou know, SQL Server is really starting to piss me off. Either it or my ignorance of it.
I run a job, and it fails. If I double-click on 'Failed', it tells me to view the history log for details. So I do, and the message is, 'The package execution failed. The step failed.'
Reeeal useful. I have to execute the package in that step (found in the log) manually, using dtexecui.exe, so that I can get why the package failed.
Two major irritations:
- Why do I have to go to three or four different places just to get an error message that's useful?
- Why do I keep clicking on that 'Failed' link, when it never tells me anything useful?
I run a job, and it fails. If I double-click on 'Failed', it tells me to view the history log for details. So I do, and the message is, 'The package execution failed. The step failed.'
Reeeal useful. I have to execute the package in that step (found in the log) manually, using dtexecui.exe, so that I can get why the package failed.
Two major irritations:
- Why do I have to go to three or four different places just to get an error message that's useful?
- Why do I keep clicking on that 'Failed' link, when it never tells me anything useful?
"So what's 184,900,950KB in GB?"
Aug. 31st, 2007 10:19 amA useful question!
"How far back do you want backups to go?"
Er, I do have the Google. 'twas a funny chat line. But thankee.
"How far back do you want backups to go?"
Er, I do have the Google. 'twas a funny chat line. But thankee.
