March 31, 2008 at 3:52 am
I have four servers, all of which have the same problem. It's not a server issue as far as I can tell.
March 31, 2008 at 1:30 pm
I have to admit it's not something I use very often - something esle to investigate!
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
June 2, 2008 at 9:28 am
God this is annoying. Why is it that when I install clean instances on any machine the DTA tables/Sprocs DO NOT GET CREATED!!! Why is it that when I create them from another DB that the tool errors out on the first step?? Does anyone have any clue how I can get it to work/install correctly????
June 3, 2008 at 4:09 am
I don't know. I wish I did. I have the same issue.
I think maybe Microsoft needs to be contacted about this, but since someone else always installs our SQL Servers (I'm not allowed to touch the install process), I can't provide details as to what screens come up and what options are chosen.
What edition of SQL Server are you installing? We went with Enterprise 2005.
August 29, 2008 at 10:32 am
So I installed SQL Server 2008 hoping that this problem would be fixed but was wrong. Exact same problem on 2008. DTA tables and sprocs NOT there, had to manually create them. Never gets past the first step and never gives any detail in the error. What a piece of crap.
August 30, 2008 at 7:33 am
Well that's seriously disappointing. I wonder why some people are able to have it installed from scratch and others aren't? There's got to be some setting or something that allows it to be installed some of the time and not others.
September 2, 2008 at 9:46 am
Well I posted a similar question on the MSDN forums and someone stated that the tables and sprocs are not installed until you connect, which does actually make sense (kind of a weird way to do it but at least it would explain it). However without the tables and sprocs, I can't connect no matter what account I use - even SQL Server login that I created with every possible permission i could give it. If I script the tables/sprocs out from another instance of SQL Server that has them I can connect but I can't do even the simplest of tasks with it like a select * from
query where the table has about 5 rows and 3 columns.
Seriously dissappointing - i agree!
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply