Always SQL Server 8.x from Management Studio

Greetings,
I originally have had SQL 2k SP3 installed before installing Visual Studio
2005 and SQL Server 2005. Anyway, that was a while ago. Now, for the first
time in a blue moon I have the need to be doing some SQL Server 2005 stuff
on my machine and the only server that SQL Server Management Studio finds or
connects to on this box is version 8.0.760. I can swear I had set up a 2k5
database in the past and did some work with it. I have installed SQL 2k5
Developer Edition.
My main question is, how do I connect to the 2k5 database, and if need be,
how do I add one so I can connect to it? This should be simple but it seems
not.
Thanks,
ShawnProbably you still have your SQL Server 2000 instance installed, and if you
worked with a SQL Server 2005 instance before on the same computer, most
likely this is a named instance.
Run SQL Server 2000 Service Manager and click the Server list to see the
installed instances (I can even see SQL Server 2005 instances there).
Run SQL Server 2005 Configuration Manager and look into SQL Server 2005
Services.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:

> Greetings,
> I originally have had SQL 2k SP3 installed before installing Visual Studio
> 2005 and SQL Server 2005. Anyway, that was a while ago. Now, for the fir
st
> time in a blue moon I have the need to be doing some SQL Server 2005 stuff
> on my machine and the only server that SQL Server Management Studio finds
or
> connects to on this box is version 8.0.760. I can swear I had set up a 2k
5
> database in the past and did some work with it. I have installed SQL 2k5
> Developer Edition.
> My main question is, how do I connect to the 2k5 database, and if need be,
> how do I add one so I can connect to it? This should be simple but it see
ms
> not.
>
> Thanks,
> Shawn
>
>|||> Probably you still have your SQL Server 2000 instance installed, and if
> you
> worked with a SQL Server 2005 instance before on the same computer, most
> likely this is a named instance.
> Run SQL Server 2000 Service Manager and click the Server list to see the
> installed instances (I can even see SQL Server 2005 instances there).
> Run SQL Server 2005 Configuration Manager and look into SQL Server 2005
> Services.
>
It does not show any SQL Server 2005 instances. Only the 2000 instance on
this machine and the 2000 instance on another machien. If it isn't showing
any 2005 instances running, how do I start it up? When I run SQL Server
2005 config man. everything seems as if 2005 is okay.
Thanks,
Shawn|||Try SQL Server Configuration Manager and select SQL Server 2005 Services.
Then look for the lines showing 'Service Type' as 'SQL Server'. There you
will see the instance name on the 'Name' column and you could check 'State'
to see if the instance is running or stopped.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:

> It does not show any SQL Server 2005 instances. Only the 2000 instance on
> this machine and the 2000 instance on another machien. If it isn't showin
g
> any 2005 instances running, how do I start it up? When I run SQL Server
> 2005 config man. everything seems as if 2005 is okay.
>
> Thanks,
> Shawn
>
>|||> Try SQL Server Configuration Manager and select SQL Server 2005 Services.
> Then look for the lines showing 'Service Type' as 'SQL Server'. There you
> will see the instance name on the 'Name' column and you could check
> 'State'
> to see if the instance is running or stopped.
Well, there's my problem... I do not have "SQL Server" but I have a crap
load of others. How do I get the "SQL Server" service to appear? Should I
reinstall sql 2k5?
Thanks,
Shawn|||If 'SQL Server' is not listed on the 'Service Type' column then you do not
have an instance of SQL Server 2005. You could install a new one.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:

> Well, there's my problem... I do not have "SQL Server" but I have a crap
> load of others. How do I get the "SQL Server" service to appear? Should
I
> reinstall sql 2k5?
>
> Thanks,
> Shawn
>
>|||> If 'SQL Server' is not listed on the 'Service Type' column then you do not
> have an instance of SQL Server 2005. You could install a new one.
How? Do I pop in the SQL Server 2005 (Server) disk? (as opposed to the
tools disk?). I've been spending hours and endless Google searches to
answer that very question and the answer is not clear (unless I'm using SQL
Express, which I'm not).
Thanks,
Shawn|||Hi Shawn,
Yes, install a new instance from your SQL Server 2005 media (in my case it
is SQL Server 2005 X Edition Disk 1'. Run setup and make sure you select 'SQ
L
Server Database Services' on the 'Components to Install' window.
If you already have a SQL Server 2000 default instance you can install a new
named instance for SQL Server 2005.
Installing SQL Server 2005 Service Pack 1 is a good idea too.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:

> How? Do I pop in the SQL Server 2005 (Server) disk? (as opposed to the
> tools disk?). I've been spending hours and endless Google searches to
> answer that very question and the answer is not clear (unless I'm using SQ
L
> Express, which I'm not).
>
> Thanks,
> Shawn
>
>|||> Yes, install a new instance from your SQL Server 2005 media (in my case it
> is SQL Server 2005 X Edition Disk 1'. Run setup and make sure you select
> 'SQL
> Server Database Services' on the 'Components to Install' window.
> If you already have a SQL Server 2000 default instance you can install a
> new
> named instance for SQL Server 2005.
> Installing SQL Server 2005 Service Pack 1 is a good idea too.
Done. That's all it was.
Thanks,
Shawn

Always SQL Server 8.x from Management Studio

Greetings,
I originally have had SQL 2k SP3 installed before installing Visual Studio
2005 and SQL Server 2005. Anyway, that was a while ago. Now, for the first
time in a blue moon I have the need to be doing some SQL Server 2005 stuff
on my machine and the only server that SQL Server Management Studio finds or
connects to on this box is version 8.0.760. I can swear I had set up a 2k5
database in the past and did some work with it. I have installed SQL 2k5
Developer Edition.
My main question is, how do I connect to the 2k5 database, and if need be,
how do I add one so I can connect to it? This should be simple but it seems
not.
Thanks,
ShawnProbably you still have your SQL Server 2000 instance installed, and if you
worked with a SQL Server 2005 instance before on the same computer, most
likely this is a named instance.
Run SQL Server 2000 Service Manager and click the Server list to see the
installed instances (I can even see SQL Server 2005 instances there).
Run SQL Server 2005 Configuration Manager and look into SQL Server 2005
Services.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:
> Greetings,
> I originally have had SQL 2k SP3 installed before installing Visual Studio
> 2005 and SQL Server 2005. Anyway, that was a while ago. Now, for the first
> time in a blue moon I have the need to be doing some SQL Server 2005 stuff
> on my machine and the only server that SQL Server Management Studio finds or
> connects to on this box is version 8.0.760. I can swear I had set up a 2k5
> database in the past and did some work with it. I have installed SQL 2k5
> Developer Edition.
> My main question is, how do I connect to the 2k5 database, and if need be,
> how do I add one so I can connect to it? This should be simple but it seems
> not.
>
> Thanks,
> Shawn
>
>|||> Probably you still have your SQL Server 2000 instance installed, and if
> you
> worked with a SQL Server 2005 instance before on the same computer, most
> likely this is a named instance.
> Run SQL Server 2000 Service Manager and click the Server list to see the
> installed instances (I can even see SQL Server 2005 instances there).
> Run SQL Server 2005 Configuration Manager and look into SQL Server 2005
> Services.
>
It does not show any SQL Server 2005 instances. Only the 2000 instance on
this machine and the 2000 instance on another machien. If it isn't showing
any 2005 instances running, how do I start it up? When I run SQL Server
2005 config man. everything seems as if 2005 is okay.
Thanks,
Shawn|||Try SQL Server Configuration Manager and select SQL Server 2005 Services.
Then look for the lines showing 'Service Type' as 'SQL Server'. There you
will see the instance name on the 'Name' column and you could check 'State'
to see if the instance is running or stopped.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:
> > Probably you still have your SQL Server 2000 instance installed, and if
> > you
> > worked with a SQL Server 2005 instance before on the same computer, most
> > likely this is a named instance.
> >
> > Run SQL Server 2000 Service Manager and click the Server list to see the
> > installed instances (I can even see SQL Server 2005 instances there).
> >
> > Run SQL Server 2005 Configuration Manager and look into SQL Server 2005
> > Services.
> >
> It does not show any SQL Server 2005 instances. Only the 2000 instance on
> this machine and the 2000 instance on another machien. If it isn't showing
> any 2005 instances running, how do I start it up? When I run SQL Server
> 2005 config man. everything seems as if 2005 is okay.
>
> Thanks,
> Shawn
>
>|||> Try SQL Server Configuration Manager and select SQL Server 2005 Services.
> Then look for the lines showing 'Service Type' as 'SQL Server'. There you
> will see the instance name on the 'Name' column and you could check
> 'State'
> to see if the instance is running or stopped.
Well, there's my problem... I do not have "SQL Server" but I have a crap
load of others. How do I get the "SQL Server" service to appear? Should I
reinstall sql 2k5?
Thanks,
Shawn|||If 'SQL Server' is not listed on the 'Service Type' column then you do not
have an instance of SQL Server 2005. You could install a new one.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:
> > Try SQL Server Configuration Manager and select SQL Server 2005 Services.
> > Then look for the lines showing 'Service Type' as 'SQL Server'. There you
> > will see the instance name on the 'Name' column and you could check
> > 'State'
> > to see if the instance is running or stopped.
> Well, there's my problem... I do not have "SQL Server" but I have a crap
> load of others. How do I get the "SQL Server" service to appear? Should I
> reinstall sql 2k5?
>
> Thanks,
> Shawn
>
>|||> If 'SQL Server' is not listed on the 'Service Type' column then you do not
> have an instance of SQL Server 2005. You could install a new one.
How? Do I pop in the SQL Server 2005 (Server) disk? (as opposed to the
tools disk?). I've been spending hours and endless Google searches to
answer that very question and the answer is not clear (unless I'm using SQL
Express, which I'm not).
Thanks,
Shawn|||Hi Shawn,
Yes, install a new instance from your SQL Server 2005 media (in my case it
is SQL Server 2005 X Edition Disk 1'. Run setup and make sure you select 'SQL
Server Database Services' on the 'Components to Install' window.
If you already have a SQL Server 2000 default instance you can install a new
named instance for SQL Server 2005.
Installing SQL Server 2005 Service Pack 1 is a good idea too.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"Shawn B." wrote:
> > If 'SQL Server' is not listed on the 'Service Type' column then you do not
> > have an instance of SQL Server 2005. You could install a new one.
> How? Do I pop in the SQL Server 2005 (Server) disk? (as opposed to the
> tools disk?). I've been spending hours and endless Google searches to
> answer that very question and the answer is not clear (unless I'm using SQL
> Express, which I'm not).
>
> Thanks,
> Shawn
>
>|||> Yes, install a new instance from your SQL Server 2005 media (in my case it
> is SQL Server 2005 X Edition Disk 1'. Run setup and make sure you select
> 'SQL
> Server Database Services' on the 'Components to Install' window.
> If you already have a SQL Server 2000 default instance you can install a
> new
> named instance for SQL Server 2005.
> Installing SQL Server 2005 Service Pack 1 is a good idea too.
Done. That's all it was.
Thanks,
Shawn

Always showing the parameter input area.

Greetings,

Is there a way to force the parameter input area to always show even when default values are specified? I want to always display the parameter area even when I set initial parameters.

Thanks

--|||

The strange thing is in one report I have a date parameter set to a default value of =Today() and in that report the parameter input area is always visible.

For a test I added a kludge parameter to the other report as a date and the input area is still in a collapsed state.

It must be the way the other parameters are processed.

|||

It's odd that your parameters area doesn't display just because the parameters are satisfied. Is this a drillthrough target by any chance? Drillthrough targets will have their parameters areas collapsed, since their parameterization is implied by the drillthrough parent.

The use of an expression for the default value ("=Today()) may short-circuit this, such that the viewer doesn't know ahead of time if the expression for the default value will evaluate. In that case, the viewer may just decide to show the parameters area in case the expression doesn't evaluate to a valid default value.

What build of Report Server are you using? On my test servers, the drillthrough target's parameters area is collapsed, even if I use an expression for the default value.

|||

"Prompt" properties of that parameter is blank?

|||

Thanks for the reply. I have not checked the forum in a while nor have I found a workaround.

This is not a drill through report and the prompt string has been specified.

I am working with 3 parameters and only one is a prompted parameter.

P1 Integer - Internal - No available values -default value of 0 - non-prompt

P2 Integer - Hidden - No available values - default value comes from query - non prompt

P3 - String - Prompt specified - Available values from query (forces drop down list) - Default value from query - prompt

I wish for the 3rd parameter, displayed in the parameter input area, to be visible when the report renders but it's not, the whole area is collapsed.

Could it be something to do of the order or timing of parameter processing?

|||

Made progress!

When I invoke the report via the url command the parameter area is always visible.

When I invoke the report via the navigation functionality of a report item the report is rendered but the parameter area collapsed.

Still dont know why....

Always showing the parameter input area.

Greetings,

Is there a way to force the parameter input area to always show even when default values are specified? I want to always display the parameter area even when I set initial parameters.

Thanks

--|||

The strange thing is in one report I have a date parameter set to a default value of =Today() and in that report the parameter input area is always visible.

For a test I added a kludge parameter to the other report as a date and the input area is still in a collapsed state.

It must be the way the other parameters are processed.

|||

It's odd that your parameters area doesn't display just because the parameters are satisfied. Is this a drillthrough target by any chance? Drillthrough targets will have their parameters areas collapsed, since their parameterization is implied by the drillthrough parent.

The use of an expression for the default value ("=Today()) may short-circuit this, such that the viewer doesn't know ahead of time if the expression for the default value will evaluate. In that case, the viewer may just decide to show the parameters area in case the expression doesn't evaluate to a valid default value.

What build of Report Server are you using? On my test servers, the drillthrough target's parameters area is collapsed, even if I use an expression for the default value.

|||

"Prompt" properties of that parameter is blank?

|||

Thanks for the reply. I have not checked the forum in a while nor have I found a workaround.

This is not a drill through report and the prompt string has been specified.

I am working with 3 parameters and only one is a prompted parameter.

P1 Integer - Internal - No available values -default value of 0 - non-prompt

P2 Integer - Hidden - No available values - default value comes from query - non prompt

P3 - String - Prompt specified - Available values from query (forces drop down list) - Default value from query - prompt

I wish for the 3rd parameter, displayed in the parameter input area, to be visible when the report renders but it's not, the whole area is collapsed.

Could it be something to do of the order or timing of parameter processing?

|||

Made progress!

When I invoke the report via the url command the parameter area is always visible.

When I invoke the report via the navigation functionality of a report item the report is rendered but the parameter area collapsed.

Still dont know why....