May 10, 2012 at 9:17 am
WayneS (5/10/2012)
Hey Threadizens,Regarding today's (10 May 2012) QOTD: several folks have stated that it could have been worded better. My question to you is how would you have worded it better? Post your ideas with the QotD discussion (not The Thread!), or PM me if you desire.
Personally, I thought that the question clearly states what is needed, and that there is only one possible correct answer. Though the answers do require you to know what is going on.
I view the QotD has having two purposes:
1. quiz on what you know
2. learn
So phase 2 of my learning is: how could I have done it better?
It read a little funny when I first saw it, but it seemed OK to me after you read it a few times, so I let it go.
Reading a few of the comments, I think I would have put it as an example and broken the sentence.
If I have a table with 25 columns and I run a SELECT *. When will I not get 25 columns in my result set?
May 10, 2012 at 9:33 am
Steve Jones - SSC Editor (5/10/2012)
Clearly it'sWAYNES'S WORLD, PARTY TIME, EXCELLENT
QOD (http://www.sqlservercentral.com/questions/T-SQL/89819/) and article (http://www.sqlservercentral.com/articles/Performance/89505/) published today.
Hey Steve... how about an "author day" where you do several articles (and maybe QotD) from one author?
... how about a "theme day" where you do several articles and the QotD on a specific theme (maybe the QotD comes from the article?)?
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
May 10, 2012 at 9:44 am
And on the same day:
http://sqlblog.com/blogs/jamie_thomson/archive/2012/05/10/datefromparts.aspx
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
May 10, 2012 at 9:49 am
WayneS (5/10/2012)
Hey Steve... how about an "author day" where you do several articles (and maybe QotD) from one author?
... how about a "theme day" where you do several articles and the QotD on a specific theme (maybe the QotD comes from the article?)?
Happy to do that. We used to try, but it was hard to get content aligned.
We could do two related articles and a QOD, and a script, if you submit them together.
May 10, 2012 at 11:51 am
Stefan Krzywicki (5/10/2012)
We're moving a bunch of Oracle to SQL Server here too, I'm happy that we're doing it, but interacting with Oracle is a pain.
One really annoying bit is the connection. The SSIS package just doesn't want to run as a job, wacky permissions errors. At least the Attunity source tool works well.
Don't get me started on SSIS & Oracle.
I had to import 390 tables to SQL Server, so I quickly created a package with the Import Wizard.
The Microsoft OLE DB provider for Oracle lost all the accents in the text (café became cafe) and it doesn't exist in 64-bit.
The Oracle OLE DB provider somehow messed up the mappings in the wizard and Oracle varchar2 datatypes were mapped to the datatype 130. (which doesn't exist of course)
So I went with the Migration Assistant, which did the job quite well but imported all sorts of metadata I didn't need (indexes, triggers, extended properties).
Fieuw, enough ranting on Oracle today in the thread 😀
(just a quick last one: why is the size of the Oracle client download almost as big as an entire SQL Server edition?)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 10, 2012 at 11:54 am
Koen Verbeeck (5/10/2012)
(just a quick last one: why is the size of the Oracle client download almost as big as an entire SQL Server edition?)
Because it is an older, more mature product with tons of depreciated code just floating around. 😛
May 10, 2012 at 11:55 am
WayneS (5/10/2012)
Hey Threadizens,Regarding today's (10 May 2012) QOTD: several folks have stated that it could have been worded better. My question to you is how would you have worded it better? Post your ideas with the QotD discussion (not The Thread!), or PM me if you desire.
Personally, I thought that the question clearly states what is needed, and that there is only one possible correct answer. Though the answers do require you to know what is going on.
I view the QotD has having two purposes:
1. quiz on what you know
2. learn
So phase 2 of my learning is: how could I have done it better?
I already responded in the discussion, but just to make it obvious;
it was a great question and I definately learned something. So purpose 1 and 2 fulfilled.
The question itself was indeed a bit weird to read at first - especially since I'm not a native English speaker - but I got it after reading it a few times.
Keep up the good work! I'm looking forward to your next question.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 10, 2012 at 12:04 pm
Koen Verbeeck (5/10/2012)
Stefan Krzywicki (5/10/2012)
We're moving a bunch of Oracle to SQL Server here too, I'm happy that we're doing it, but interacting with Oracle is a pain.
One really annoying bit is the connection. The SSIS package just doesn't want to run as a job, wacky permissions errors. At least the Attunity source tool works well.
Don't get me started on SSIS & Oracle.
I had to import 390 tables to SQL Server, so I quickly created a package with the Import Wizard.
The Microsoft OLE DB provider for Oracle lost all the accents in the text (café became cafe) and it doesn't exist in 64-bit.
The Oracle OLE DB provider somehow messed up the mappings in the wizard and Oracle varchar2 datatypes were mapped to the datatype 130. (which doesn't exist of course)
So I went with the Migration Assistant, which did the job quite well but imported all sorts of metadata I didn't need (indexes, triggers, extended properties).
Fieuw, enough ranting on Oracle today in the thread 😀
(just a quick last one: why is the size of the Oracle client download almost as big as an entire SQL Server edition?)
Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list of the Oracle tables obtained with a query against all_tables. It is slow, it is tedious, but it is more reliable. I worked out the permissions, needed to either encrypt the package with a password instead of a user key or set up a proxy, neither of which I'd done before, so at least I'm learning new things!
--------------------------------------
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
May 10, 2012 at 12:08 pm
Stefan Krzywicki (5/10/2012)
Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list of the Oracle tables obtained with a query against all_tables. It is slow, it is tedious, but it is more reliable. I worked out the permissions, needed to either encrypt the package with a password instead of a user key or set up a proxy, neither of which I'd done before, so at least I'm learning new things!
Never encrypt with user key in SSIS, it only gives troubles ahead, as you probably figured out by now 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 10, 2012 at 12:11 pm
Koen Verbeeck (5/10/2012)
Stefan Krzywicki (5/10/2012)
Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list of the Oracle tables obtained with a query against all_tables. It is slow, it is tedious, but it is more reliable. I worked out the permissions, needed to either encrypt the package with a password instead of a user key or set up a proxy, neither of which I'd done before, so at least I'm learning new things!
Never encrypt with user key in SSIS, it only gives troubles ahead, as you probably figured out by now 😀
Yep, but it is the default option and everything ran fine up until now, so I had no idea! I'm glad it doesn't insist on the inane password conventions and lets me use a truly strong password.
--------------------------------------
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
May 10, 2012 at 12:46 pm
Koen Verbeeck (5/10/2012)
Stefan Krzywicki (5/10/2012)
Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list of the Oracle tables obtained with a query against all_tables. It is slow, it is tedious, but it is more reliable. I worked out the permissions, needed to either encrypt the package with a password instead of a user key or set up a proxy, neither of which I'd done before, so at least I'm learning new things!
Never encrypt with user key in SSIS, it only gives troubles ahead, as you probably figured out by now 😀
My experience has been that "Don't Save Sensitive.." and relying on Trusted Connections is by far the easiest way to go.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
May 10, 2012 at 12:50 pm
RBarryYoung (5/10/2012)
Koen Verbeeck (5/10/2012)
Stefan Krzywicki (5/10/2012)
Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list of the Oracle tables obtained with a query against all_tables. It is slow, it is tedious, but it is more reliable. I worked out the permissions, needed to either encrypt the package with a password instead of a user key or set up a proxy, neither of which I'd done before, so at least I'm learning new things!
Never encrypt with user key in SSIS, it only gives troubles ahead, as you probably figured out by now 😀
My experience has been that "Don't Save Sensitive.." and relying on Trusted Connections is by far the easiest way to go.
So where do you get the passwords from for connections then? I don't know about Trusted Connections.
--------------------------------------
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
May 10, 2012 at 12:51 pm
Apparently, I just made one of the help desk guys very happy. He passed on a user problem with an Access db that has become unwieldy asking for solutions. My response was: "We don't support Access. If this database is necessary to the users to do their jobs, they can submit a project to have the db upgraded to a scalable, backed up, and monitored solution."
I thought he was going to throw a fit. Instead, he digitally "hugged" me because I apparently told the users exactly what he's been trying to explain to them for months.
Huh. I guess DBAs and Help Desk Geeks can get along after all. 😉
May 10, 2012 at 1:02 pm
Stefan Krzywicki (5/10/2012)
RBarryYoung (5/10/2012)
Koen Verbeeck (5/10/2012)
Stefan Krzywicki (5/10/2012)
Yeah, I created the import package manually. I ended up getting the table structures by using an openquery in a cursor loop through a list of the Oracle tables obtained with a query against all_tables. It is slow, it is tedious, but it is more reliable. I worked out the permissions, needed to either encrypt the package with a password instead of a user key or set up a proxy, neither of which I'd done before, so at least I'm learning new things!
Never encrypt with user key in SSIS, it only gives troubles ahead, as you probably figured out by now 😀
My experience has been that "Don't Save Sensitive.." and relying on Trusted Connections is by far the easiest way to go.
So where do you get the passwords from for connections then? I don't know about Trusted Connections.
Trusted connections, also known as windows users/qroups. SQL Trusts Windows to authenticate the user.
May 10, 2012 at 1:02 pm
Barry!!!!!!
Welcome back. How ya been?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 36,016 through 36,030 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply