January 30, 2014 at 7:48 am
rodjkidd (1/30/2014)
Serious Doh! Moment today.SSIS process has failed this morning. Business noticed before the support guys. Error says a problem with a column - the files uses ; as a delimiter, so I thought maybe there's an extra one there or something wrong with the file.
After a couple of misses with coping the package and importing into SSDT - it's 2008 on the server. I finally got it to run on my test system and it works...
Strange...
Went to talk to one of the Prod DBA's as my access on the server is limited, and he spots that the server has run out of space! Doh!
Nothing wrong with the package or job, other than the error message sent me on a wild goose chase! <facepalm>
Rodders...
SSIS error messages are the worst.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
January 30, 2014 at 8:01 am
rodjkidd (1/30/2014)
Serious Doh! Moment today.... {snip}...
Went to talk to one of the Prod DBA's as my access on the server is limited, and he spots that the server has run out of space! Doh!
Nothing wrong with the package or job, other than the error message sent me on a wild goose chase! <facepalm>
Heh... I love some of the error messages that come up. They sometimes cause a gaggle of geese to take flight. 🙂
Shifting gears a bit and sorry for the obvious recommendation, but I think it's time for your DBA to build (or buy) and deploy a disk space monitoring system. 🙂 Such a thing has allowed me to fairly accurately predict such problems months in advance so the folks in NetOps have time to get purchase orders approved, buy the extra disk space, install it, test it, etc, etc, before it comes anywhere near being an urgency.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2014 at 8:10 am
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Serious Doh! Moment today.... {snip}...
Went to talk to one of the Prod DBA's as my access on the server is limited, and he spots that the server has run out of space! Doh!
Nothing wrong with the package or job, other than the error message sent me on a wild goose chase! <facepalm>
Heh... I love some of the error messages that come up. They sometimes cause a gaggle of geese to take flight. 🙂
Shifting gears a bit and sorry for the obvious recommendation, but I think it's time for your DBA to build (or buy) and deploy a disk space monitoring system. 🙂 Such a thing has allowed me to fairly accurately predict such problems months in advance so the folks in NetOps have time to get purchase orders approved, buy the extra disk space, install it, test it, etc, etc, before it comes anywhere near being an urgency.
Yep, running out of disk space and not knowing about it = DBA Fail IMO
January 30, 2014 at 8:37 am
HowardW (1/30/2014)
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Serious Doh! Moment today.... {snip}...
Went to talk to one of the Prod DBA's as my access on the server is limited, and he spots that the server has run out of space! Doh!
Nothing wrong with the package or job, other than the error message sent me on a wild goose chase! <facepalm>
Heh... I love some of the error messages that come up. They sometimes cause a gaggle of geese to take flight. 🙂
Shifting gears a bit and sorry for the obvious recommendation, but I think it's time for your DBA to build (or buy) and deploy a disk space monitoring system. 🙂 Such a thing has allowed me to fairly accurately predict such problems months in advance so the folks in NetOps have time to get purchase orders approved, buy the extra disk space, install it, test it, etc, etc, before it comes anywhere near being an urgency.
Yep, running out of disk space and not knowing about it = DBA Fail IMO
Probably not the time to mention we have one of those...
Company has out sourced prod DBA team. Been up and running since start of year, so some things are still falling through the cracks. So don't know if they will implement their own monitoring or use the software in place. Depends on who "owns" the servers I guess.
I think they (the outsource company) will get another month of grace and then questions will be asked.
Pity as we had sorted out nearly all these types of issues last year - major re-org last year as well just before I joined. Oh so glad I'm on contract here!
Rodders...
January 30, 2014 at 8:42 am
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Another awesome SQL Spackle from Jeff today.Cheers Jeff!
Rodders...
Thanks Rodders. This one was aimed mostly at helping newbies to SQL Server understand the problem especially since there have been a fair number of similar questions in the past several months. I remember the first time I had to solve this problem in T-SQL. It wasn't pretty. :blush:
Jeff,
I quite understand;
But if this isn't something you need to do, no matter how much experience you have, it's a great point of reference.
And, a really great insight in to how to destruct a problem and come up with a neat solution. As you said in the article some people might tackle each sub type as one problem. Rather than as a whole. Of course sometimes the reverse is true!
So more blushing I'm afraid! 😀
Rodders...
January 30, 2014 at 8:51 am
rodjkidd (1/30/2014)
HowardW (1/30/2014)
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Serious Doh! Moment today.... {snip}...
Went to talk to one of the Prod DBA's as my access on the server is limited, and he spots that the server has run out of space! Doh!
Nothing wrong with the package or job, other than the error message sent me on a wild goose chase! <facepalm>
Heh... I love some of the error messages that come up. They sometimes cause a gaggle of geese to take flight. 🙂
Shifting gears a bit and sorry for the obvious recommendation, but I think it's time for your DBA to build (or buy) and deploy a disk space monitoring system. 🙂 Such a thing has allowed me to fairly accurately predict such problems months in advance so the folks in NetOps have time to get purchase orders approved, buy the extra disk space, install it, test it, etc, etc, before it comes anywhere near being an urgency.
Yep, running out of disk space and not knowing about it = DBA Fail IMO
Probably not the time to mention we have one of those...
Company has out sourced prod DBA team. Been up and running since start of year, so some things are still falling through the cracks. So don't know if they will implement their own monitoring or use the software in place. Depends on who "owns" the servers I guess.
I think they (the outsource company) will get another month of grace and then questions will be asked.
Pity as we had sorted out nearly all these types of issues last year - major re-org last year as well just before I joined. Oh so glad I'm on contract here!
Rodders...
Makes you wonder what else they might be missing.
That is a real basic thing to hit the wall on.
Unless you just launched something that chewed up all the disk space last night.
January 30, 2014 at 9:36 am
Greg Edwards-268690 (1/30/2014)
rodjkidd (1/30/2014)
HowardW (1/30/2014)
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Serious Doh! Moment today.... {snip}...
Went to talk to one of the Prod DBA's as my access on the server is limited, and he spots that the server has run out of space! Doh!
Nothing wrong with the package or job, other than the error message sent me on a wild goose chase! <facepalm>
Heh... I love some of the error messages that come up. They sometimes cause a gaggle of geese to take flight. 🙂
Shifting gears a bit and sorry for the obvious recommendation, but I think it's time for your DBA to build (or buy) and deploy a disk space monitoring system. 🙂 Such a thing has allowed me to fairly accurately predict such problems months in advance so the folks in NetOps have time to get purchase orders approved, buy the extra disk space, install it, test it, etc, etc, before it comes anywhere near being an urgency.
Yep, running out of disk space and not knowing about it = DBA Fail IMO
Probably not the time to mention we have one of those...
Company has out sourced prod DBA team. Been up and running since start of year, so some things are still falling through the cracks. So don't know if they will implement their own monitoring or use the software in place. Depends on who "owns" the servers I guess.
I think they (the outsource company) will get another month of grace and then questions will be asked.
Pity as we had sorted out nearly all these types of issues last year - major re-org last year as well just before I joined. Oh so glad I'm on contract here!
Rodders...
Makes you wonder what else they might be missing.
That is a real basic thing to hit the wall on.
Unless you just launched something that chewed up all the disk space last night.
Yep. Quite agree.
No, it's just been a slow creep for archived data, and heard back from the business owner that it is needed for auditing, so we've requested an extra drive for the archiving. Then we need to discuss just how much historic data is required.
Now I can go back to new project - which has had a large chunk of it parked and it seems to be the bit I was going to be most involved in! :ermm:
Rodders...
January 30, 2014 at 11:30 am
rodjkidd (1/30/2014)
Company has out sourced prod DBA team. Been up and running since start of year, so some things are still falling through the cracks. So don't know if they will implement their own monitoring or use the software in place. Depends on who "owns" the servers I guess.
That gives me leg cramps just thinking about that. Doing a disk space check should be second only to checking the Recovery Models and the Backups, both of which should be done the first day (or before) of "taking over".
I suspect that "no one" will soon become the owner of the servers.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2014 at 11:45 am
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Company has out sourced prod DBA team. Been up and running since start of year, so some things are still falling through the cracks. So don't know if they will implement their own monitoring or use the software in place. Depends on who "owns" the servers I guess.That gives me leg cramps just thinking about that. Doing a disk space check should be second only to checking the Recovery Models and the Backups, both of which should be done the first day (or before) of "taking over".
I suspect that "no one" will soon become the owner of the servers.
Of course they will. After all, that's what outsourcing is all about - lack of accountability and plausible deniability.
It depends on if the company is providing the servers and space, but this is pretty basic.
January 30, 2014 at 12:48 pm
Ed Wagner (1/30/2014)
Jeff Moden (1/30/2014)
rodjkidd (1/30/2014)
Company has out sourced prod DBA team. Been up and running since start of year, so some things are still falling through the cracks. So don't know if they will implement their own monitoring or use the software in place. Depends on who "owns" the servers I guess.That gives me leg cramps just thinking about that. Doing a disk space check should be second only to checking the Recovery Models and the Backups, both of which should be done the first day (or before) of "taking over".
I suspect that "no one" will soon become the owner of the servers.
Of course they will. After all, that's what outsourcing is all about - lack of accountability and plausible deniability.
It depends on if the company is providing the servers and space, but this is pretty basic.
One of the issues with outsourcing can be not having the right people involved in the evaluation process.
Who is responsible for what, and the process to escalate an issue are very important.
Monitoring was one of the first things we mapped out.
We didn't want a surprise.
Nothing is worse than having an issue, most users just go so far as 'it is broken'. It does not matter if it is still your responsibility or not,
'Just fix it'.
January 30, 2014 at 3:24 pm
Can somebody help me out? We have a third part vendor helping us code some piece of one of our applications. Not my choice, I would much prefer to keep it in house but that is a political battle that is long behind me. At any rate, I recently got the first draft of their data structures and every single table has a uniqueidentifier and the clustered primary key. :w00t:
There is no reason to use uiniqueidentifiers in this system. It is a single non-mirrored, no replication stand alone database. Now I know from experience that this is a horrible design decision because of index fragmentation and a host of other really bad things that happen when you have a clustered index on a guid.
Does anybody know of any good examples out there that explains this? My google-fu is elusive today.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 30, 2014 at 3:42 pm
Sean Lange (1/30/2014)
Can somebody help me out? We have a third part vendor helping us code some piece of one of our applications. Not my choice, I would much prefer to keep it in house but that is a political battle that is long behind me. At any rate, I recently got the first draft of their data structures and every single table has a uniqueidentifier and the clustered primary key. :w00t:There is no reason to use uiniqueidentifiers in this system. It is a single non-mirrored, no replication stand alone database. Now I know from experience that this is a horrible design decision because of index fragmentation and a host of other really bad things that happen when you have a clustered index on a guid.
Does anybody know of any good examples out there that explains this? My google-fu is elusive today.
Sean, my brother in this battle, the one word that I miss is 'federation.' If your client even prospectively intends to move to Azure or SQLS 2012/14 federation, inclusion of a GUID is IMO not only justified, it is a must. However, you/they should NOT put a primary index on it, and I am perfectly willing to file an 'amicus of the court' to support that.
That said, I still owe you a good QotD demonstrating the power of PIVOT, which I thought I would do during the Christmas break. Stay tuned, I will deliver. It is still on my To Do list.
January 30, 2014 at 3:47 pm
Would this help?
http://www.sqlskills.com/blogs/kimberly/guids-as-primary-keys-andor-the-clustering-key/
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/05/27/guid-vs-int-debate.aspx
Maybe even a post from a GUID lover:
http://blogs.msdn.com/b/sqlazure/archive/2010/05/05/10007304.aspx
Or even BOL on Using uniqueidentifier Data:
http://technet.microsoft.com/en-us/library/ms190215(v=sql.105).aspx
January 30, 2014 at 3:52 pm
Revenant (1/30/2014)
Sean Lange (1/30/2014)
Can somebody help me out? We have a third part vendor helping us code some piece of one of our applications. Not my choice, I would much prefer to keep it in house but that is a political battle that is long behind me. At any rate, I recently got the first draft of their data structures and every single table has a uniqueidentifier and the clustered primary key. :w00t:There is no reason to use uiniqueidentifiers in this system. It is a single non-mirrored, no replication stand alone database. Now I know from experience that this is a horrible design decision because of index fragmentation and a host of other really bad things that happen when you have a clustered index on a guid.
Does anybody know of any good examples out there that explains this? My google-fu is elusive today.
Sean, my brother in this battle, the one word that I miss is 'federation.' If your client even prospectively intends to move to Azure or SQLS 2012/14 federation, inclusion of a GUID is IMO not only justified, it is a must. However, you/they should NOT put a primary index on it, and I am perfectly willing to file an 'amicus of the court' to support that.
That said, I still owe you a good QotD demonstrating the power of PIVOT, which I thought I would do during the Christmas break. Stay tuned, I will deliver. It is still on my To Do list.
I agree there are times when a guid is the right and only choice. This system is NOT one of them. This is an new module for our self hosted website. There is no need to inhale the amount of space they are using for this. One of the tables has 20 guid columns and each of those if a foreign key to another table. I know this is a political battle but it just seems like a complete pita that everything they are doing is going to cause me tons of code changes to handle the fact that their keys are guids instead of (big)int identities. Trust me, guids is by far not the worst of the poor design choices. The real problem is there really is nothing that can be used a natural key. We could do something completely silly like add another column as an identity and use that as the clustered index. If we took that approach there is no point for the guid as far as the database is concerned.
Since my post I have found some good discussions and articles about this topic.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 30, 2014 at 6:26 pm
Sean Lange (1/30/2014)
Can somebody help me out? We have a third part vendor helping us code some piece of one of our applications. Not my choice, I would much prefer to keep it in house but that is a political battle that is long behind me. At any rate, I recently got the first draft of their data structures and every single table has a uniqueidentifier and the clustered primary key. :w00t:There is no reason to use uiniqueidentifiers in this system. It is a single non-mirrored, no replication stand alone database. Now I know from experience that this is a horrible design decision because of index fragmentation and a host of other really bad things that happen when you have a clustered index on a guid.
Does anybody know of any good examples out there that explains this? My google-fu is elusive today.
I'd started typing out many of the reasons I can think of, then I saw you wanted examples. Sorry that I don't have any, I just got carried away in my annoyance on your behalf.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
Viewing 15 posts - 42,706 through 42,720 (of 66,738 total)
You must be logged in to reply to this topic. Login to reply