Determin if this is Standard or Ent edition

How do I tell if an install of sql server is standard or enterprise edition?
moondaddy@.nospam.nospamselect serverproperty('edition')
Andrew J. Kelly SQL MVP
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:%23zNH8yWOGHA.348@.TK2MSFTNGP11.phx.gbl...
> How do I tell if an install of sql server is standard or enterprise
> edition?
> --
> moondaddy@.nospam.nospam
>

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

sql

detach database unavailable

Any ideas why the detach databade option is unavailable
(dimmed out) on my SQL Server 7.0 Standard edition?Hi Jim
Detaching a database from the GUI was not possible in SQL 7. You have to the
stored procedure sp_detach_db.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jim" <jim.abel@.lmco.com> wrote in message
news:56e701c3b2ce$5a6e21c0$a601280a@.phx.gbl...
> Any ideas why the detach databade option is unavailable
> (dimmed out) on my SQL Server 7.0 Standard edition?|||Sorry Nevermind, I forgot that a database cannot be
detached when it is in use. I just didn't realize that
it will dim out the option in EM
>--Original Message--
>Any ideas why the detach databade option is unavailable
>(dimmed out) on my SQL Server 7.0 Standard edition?
>.
>|||I don't have an SQL7 to test on, but as I remember: EM7 didn't expose detach or attach options. And
while EM2000 does, when connecting to an SQL7, the options are not available (as Kalen points out).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jim" <jim.abel@.lmco.com> wrote in message news:0e5401c3b2d0$7b8d37e0$a001280a@.phx.gbl...
> Sorry Nevermind, I forgot that a database cannot be
> detached when it is in use. I just didn't realize that
> it will dim out the option in EM
> >--Original Message--
> >Any ideas why the detach databade option is unavailable
> >(dimmed out) on my SQL Server 7.0 Standard edition?
> >.
> >|||Thanks for the replys, I realized that I would need to
use the query analyzer shortly after my post but
appreciate the confirmation of my ssuspicions.
This post is complete.
Thany you
>--Original Message--
>Hi Jim
>Detaching a database from the GUI was not possible in
SQL 7. You have to the
>stored procedure sp_detach_db.
>--
>HTH
>--
>Kalen Delaney
>SQL Server MVP
>www.SolidQualityLearning.com
>
>"Jim" <jim.abel@.lmco.com> wrote in message
>news:56e701c3b2ce$5a6e21c0$a601280a@.phx.gbl...
>> Any ideas why the detach databade option is unavailable
>> (dimmed out) on my SQL Server 7.0 Standard edition?
>
>.
>

Desktop vs. Standard

Hello,
I purchased some software that comes with the desktop edition of SQL 2000.
I have a Windows 2003 server and about 20 clients who need to access the
database.
Are there any limits to the desktop edition that I should be aware of?
Does it work with Windows 2003?
Does it have a limit to the number of simultaneous users?
Does it have memory limits?
Thanks
I assume you mean Desktop Engine, also known as MSDE...
1. Yes
2. No. But there's a performance throttling kicking in when you have > 8 simultaneously executing
queries.
3. Max size for db is 2GB (data, not log).
More info at http://www.microsoft.com/sql/default.mspx.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"boe" <boe_d@.hotmail.nospam.com> wrote in message news:%23bmI5Dc3EHA.1188@.tk2msftngp13.phx.gbl...
> Hello,
> I purchased some software that comes with the desktop edition of SQL 2000.
> I have a Windows 2003 server and about 20 clients who need to access the
> database.
> Are there any limits to the desktop edition that I should be aware of?
> Does it work with Windows 2003?
> Does it have a limit to the number of simultaneous users?
> Does it have memory limits?
> Thanks
>
|||Thank you - good to know!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKv%23VNc3EHA.3472@.TK2MSFTNGP09.phx.gbl...
>I assume you mean Desktop Engine, also known as MSDE...
> 1. Yes
> 2. No. But there's a performance throttling kicking in when you have > 8
> simultaneously executing
> queries.
> 3. Max size for db is 2GB (data, not log).
> More info at http://www.microsoft.com/sql/default.mspx.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "boe" <boe_d@.hotmail.nospam.com> wrote in message
> news:%23bmI5Dc3EHA.1188@.tk2msftngp13.phx.gbl...
>

Desktop vs. Standard

Hello,
I purchased some software that comes with the desktop edition of SQL 2000.
I have a Windows 2003 server and about 20 clients who need to access the
database.
Are there any limits to the desktop edition that I should be aware of?
Does it work with Windows 2003?
Does it have a limit to the number of simultaneous users?
Does it have memory limits?
ThanksI assume you mean Desktop Engine, also known as MSDE...
1. Yes
2. No. But there's a performance throttling kicking in when you have > 8 simultaneously executing
queries.
3. Max size for db is 2GB (data, not log).
More info at http://www.microsoft.com/sql/default.mspx.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"boe" <boe_d@.hotmail.nospam.com> wrote in message news:%23bmI5Dc3EHA.1188@.tk2msftngp13.phx.gbl...
> Hello,
> I purchased some software that comes with the desktop edition of SQL 2000.
> I have a Windows 2003 server and about 20 clients who need to access the
> database.
> Are there any limits to the desktop edition that I should be aware of?
> Does it work with Windows 2003?
> Does it have a limit to the number of simultaneous users?
> Does it have memory limits?
> Thanks
>|||Thank you - good to know!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKv%23VNc3EHA.3472@.TK2MSFTNGP09.phx.gbl...
>I assume you mean Desktop Engine, also known as MSDE...
> 1. Yes
> 2. No. But there's a performance throttling kicking in when you have > 8
> simultaneously executing
> queries.
> 3. Max size for db is 2GB (data, not log).
> More info at http://www.microsoft.com/sql/default.mspx.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "boe" <boe_d@.hotmail.nospam.com> wrote in message
> news:%23bmI5Dc3EHA.1188@.tk2msftngp13.phx.gbl...
>> Hello,
>> I purchased some software that comes with the desktop edition of SQL
>> 2000.
>> I have a Windows 2003 server and about 20 clients who need to access the
>> database.
>> Are there any limits to the desktop edition that I should be aware of?
>> Does it work with Windows 2003?
>> Does it have a limit to the number of simultaneous users?
>> Does it have memory limits?
>> Thanks
>>
>

Designing Reports for SQL Reporting Services 2000

My customer has SQL Reporting Services on a server with SQL 2000 Standard Edition. The customer wants to develop his own Reporting Services reports. We have been recommending Visual Basic.NET Standard 2003 for this purpose in that it costs less than $100 (usually). However, with the advent of Visual Studio 2005, the VB.NET 2003 is becoming difficult or impossible to obtain. One option is Visual C#.NET Standard 2003 - I assume it will work - does anyone know for sure?

More importantly, when Visual C#.NET 2003 becomes unvailable, what options are left for developing RS 2000 reports?

Thanks for any suggestions.

Mark

>More importantly, when Visual C#.NET 2003 becomes unvailable, what options are left for developing RS 2000 reports?

None from Microsoft. There are third-party solutions, e.g. Cizer.

|||

You could also write a small tool that performs a RDL structure "downgrade" conversion (see e.g. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=988366&SiteID=1). However note that RS 2000 doesn't support a number of RS 2005 features (e.g. multi value parameters).

-- Robert