We recommend that our clients install SQL Server at each of their satellite
offices. Every night we DTS the central database out to the satellite
offices. That way, if the link goes down, or if the main server were to go
down, we'd have one or more backup databases to switch over to.
One client is looking to save on SQL Server licensing costs. They understand
that the main server will need to be SQL Server, but they're reluctant to
pay extra for additional servers which won't normally be used. They're
asking if they could have MSDE installed at the satellite offices, rather
than SQL Server, and is there any way the main SQL Server database can be
pumped down to the satellite MSDE databases nightly. Is this possible with
DTS or any other way?
If you have any suggestions or reference links, that would be very much
appreciated!
Thanks,
- Joe Geretz -
As long as the MSDE installation does not violate Microsoft's EULA for MSDE
or the database is not greater than 2GB in size or the usage of the MSDE
instances will not be hampered by the built in processing governor in MSDE,
then I would see no problem.
Jim
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:ulI7Pp3FEHA.712@.tk2msftngp13.phx.gbl...
> We recommend that our clients install SQL Server at each of their
satellite
> offices. Every night we DTS the central database out to the satellite
> offices. That way, if the link goes down, or if the main server were to go
> down, we'd have one or more backup databases to switch over to.
> One client is looking to save on SQL Server licensing costs. They
understand
> that the main server will need to be SQL Server, but they're reluctant to
> pay extra for additional servers which won't normally be used. They're
> asking if they could have MSDE installed at the satellite offices, rather
> than SQL Server, and is there any way the main SQL Server database can be
> pumped down to the satellite MSDE databases nightly. Is this possible with
> DTS or any other way?
> If you have any suggestions or reference links, that would be very much
> appreciated!
> Thanks,
> - Joe Geretz -
>
Showing posts with label install. Show all posts
Showing posts with label install. Show all posts
Tuesday, March 27, 2012
Downsize from SQL Server to MSDE?
We recommend that our clients install SQL Server at each of their satellite
offices. Every night we DTS the central database out to the satellite
offices. That way, if the link goes down, or if the main server were to go
down, we'd have one or more backup databases to switch over to.
One client is looking to save on SQL Server licensing costs. They understand
that the main server will need to be SQL Server, but they're reluctant to
pay extra for additional servers which won't normally be used. They're
asking if they could have MSDE installed at the satellite offices, rather
than SQL Server, and is there any way the main SQL Server database can be
pumped down to the satellite MSDE databases nightly. Is this possible with
DTS or any other way?
If you have any suggestions or reference links, that would be very much
appreciated!
Thanks,
- Joe Geretz -
As long as the MSDE installation does not violate Microsoft's EULA for MSDE
or the database is not greater than 2GB in size or the usage of the MSDE
instances will not be hampered by the built in processing governor in MSDE,
then I would see no problem.
Jim
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:ulI7Pp3FEHA.712@.tk2msftngp13.phx.gbl...
> We recommend that our clients install SQL Server at each of their
satellite
> offices. Every night we DTS the central database out to the satellite
> offices. That way, if the link goes down, or if the main server were to go
> down, we'd have one or more backup databases to switch over to.
> One client is looking to save on SQL Server licensing costs. They
understand
> that the main server will need to be SQL Server, but they're reluctant to
> pay extra for additional servers which won't normally be used. They're
> asking if they could have MSDE installed at the satellite offices, rather
> than SQL Server, and is there any way the main SQL Server database can be
> pumped down to the satellite MSDE databases nightly. Is this possible with
> DTS or any other way?
> If you have any suggestions or reference links, that would be very much
> appreciated!
> Thanks,
> - Joe Geretz -
>
sql
offices. Every night we DTS the central database out to the satellite
offices. That way, if the link goes down, or if the main server were to go
down, we'd have one or more backup databases to switch over to.
One client is looking to save on SQL Server licensing costs. They understand
that the main server will need to be SQL Server, but they're reluctant to
pay extra for additional servers which won't normally be used. They're
asking if they could have MSDE installed at the satellite offices, rather
than SQL Server, and is there any way the main SQL Server database can be
pumped down to the satellite MSDE databases nightly. Is this possible with
DTS or any other way?
If you have any suggestions or reference links, that would be very much
appreciated!
Thanks,
- Joe Geretz -
As long as the MSDE installation does not violate Microsoft's EULA for MSDE
or the database is not greater than 2GB in size or the usage of the MSDE
instances will not be hampered by the built in processing governor in MSDE,
then I would see no problem.
Jim
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:ulI7Pp3FEHA.712@.tk2msftngp13.phx.gbl...
> We recommend that our clients install SQL Server at each of their
satellite
> offices. Every night we DTS the central database out to the satellite
> offices. That way, if the link goes down, or if the main server were to go
> down, we'd have one or more backup databases to switch over to.
> One client is looking to save on SQL Server licensing costs. They
understand
> that the main server will need to be SQL Server, but they're reluctant to
> pay extra for additional servers which won't normally be used. They're
> asking if they could have MSDE installed at the satellite offices, rather
> than SQL Server, and is there any way the main SQL Server database can be
> pumped down to the satellite MSDE databases nightly. Is this possible with
> DTS or any other way?
> If you have any suggestions or reference links, that would be very much
> appreciated!
> Thanks,
> - Joe Geretz -
>
sql
Downsize from SQL Server to MSDE?
We recommend that our clients install SQL Server at each of their satellite
offices. Every night we DTS the central database out to the satellite
offices. That way, if the link goes down, or if the main server were to go
down, we'd have one or more backup databases to switch over to.
One client is looking to save on SQL Server licensing costs. They understand
that the main server will need to be SQL Server, but they're reluctant to
pay extra for additional servers which won't normally be used. They're
asking if they could have MSDE installed at the satellite offices, rather
than SQL Server, and is there any way the main SQL Server database can be
pumped down to the satellite MSDE databases nightly. Is this possible with
DTS or any other way?
If you have any suggestions or reference links, that would be very much
appreciated!
Thanks,
- Joe Geretz -As long as the MSDE installation does not violate Microsoft's EULA for MSDE
or the database is not greater than 2GB in size or the usage of the MSDE
instances will not be hampered by the built in processing governor in MSDE,
then I would see no problem.
Jim
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:ulI7Pp3FEHA.712@.tk2msftngp13.phx.gbl...
> We recommend that our clients install SQL Server at each of their
satellite
> offices. Every night we DTS the central database out to the satellite
> offices. That way, if the link goes down, or if the main server were to go
> down, we'd have one or more backup databases to switch over to.
> One client is looking to save on SQL Server licensing costs. They
understand
> that the main server will need to be SQL Server, but they're reluctant to
> pay extra for additional servers which won't normally be used. They're
> asking if they could have MSDE installed at the satellite offices, rather
> than SQL Server, and is there any way the main SQL Server database can be
> pumped down to the satellite MSDE databases nightly. Is this possible with
> DTS or any other way?
> If you have any suggestions or reference links, that would be very much
> appreciated!
> Thanks,
> - Joe Geretz -
>
offices. Every night we DTS the central database out to the satellite
offices. That way, if the link goes down, or if the main server were to go
down, we'd have one or more backup databases to switch over to.
One client is looking to save on SQL Server licensing costs. They understand
that the main server will need to be SQL Server, but they're reluctant to
pay extra for additional servers which won't normally be used. They're
asking if they could have MSDE installed at the satellite offices, rather
than SQL Server, and is there any way the main SQL Server database can be
pumped down to the satellite MSDE databases nightly. Is this possible with
DTS or any other way?
If you have any suggestions or reference links, that would be very much
appreciated!
Thanks,
- Joe Geretz -As long as the MSDE installation does not violate Microsoft's EULA for MSDE
or the database is not greater than 2GB in size or the usage of the MSDE
instances will not be hampered by the built in processing governor in MSDE,
then I would see no problem.
Jim
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:ulI7Pp3FEHA.712@.tk2msftngp13.phx.gbl...
> We recommend that our clients install SQL Server at each of their
satellite
> offices. Every night we DTS the central database out to the satellite
> offices. That way, if the link goes down, or if the main server were to go
> down, we'd have one or more backup databases to switch over to.
> One client is looking to save on SQL Server licensing costs. They
understand
> that the main server will need to be SQL Server, but they're reluctant to
> pay extra for additional servers which won't normally be used. They're
> asking if they could have MSDE installed at the satellite offices, rather
> than SQL Server, and is there any way the main SQL Server database can be
> pumped down to the satellite MSDE databases nightly. Is this possible with
> DTS or any other way?
> If you have any suggestions or reference links, that would be very much
> appreciated!
> Thanks,
> - Joe Geretz -
>
Sunday, March 25, 2012
Download/Install SQL RS 2005 Alone--not the whole chunk of SQL2005
Hey all,
Is there anywhere that I could download trial version of SQL 2005 Reporting
services alone...not the whole junk of SQL Server 2005. I need just the
Reporting services. another question is I have SQL 2005 Developer Edition
CTP(community tchnology preview) DVD and I am looking at a way to upgrade
only reporting services from 2000 to 2005.But the set up wont let me do just
that. It insists that I upgrade the server also. Please let me know!!!Hi,
You can only download the complete package of SQL Server 2005 and I believe
it will be by its release. Reporting Service 2005 is a part of SQL Server
2005. Compare it to the Analysis Server part: you can't download it seperate
from the SQL Server part.
For your upgrading problem: Maybe it is a 'feature' of the CTP install,
haven't tried it this way. But you could try to install the SQL Server 2005
at a new instance and make SRS to install/upgrade at the instance of the 2000
version.
Hope this would help you.
Jan Pieter Posthuma
"Balaji" wrote:
> Hey all,
> Is there anywhere that I could download trial version of SQL 2005 Reporting
> services alone...not the whole junk of SQL Server 2005. I need just the
> Reporting services. another question is I have SQL 2005 Developer Edition
> CTP(community tchnology preview) DVD and I am looking at a way to upgrade
> only reporting services from 2000 to 2005.But the set up wont let me do just
> that. It insists that I upgrade the server also. Please let me know!!!
>
Is there anywhere that I could download trial version of SQL 2005 Reporting
services alone...not the whole junk of SQL Server 2005. I need just the
Reporting services. another question is I have SQL 2005 Developer Edition
CTP(community tchnology preview) DVD and I am looking at a way to upgrade
only reporting services from 2000 to 2005.But the set up wont let me do just
that. It insists that I upgrade the server also. Please let me know!!!Hi,
You can only download the complete package of SQL Server 2005 and I believe
it will be by its release. Reporting Service 2005 is a part of SQL Server
2005. Compare it to the Analysis Server part: you can't download it seperate
from the SQL Server part.
For your upgrading problem: Maybe it is a 'feature' of the CTP install,
haven't tried it this way. But you could try to install the SQL Server 2005
at a new instance and make SRS to install/upgrade at the instance of the 2000
version.
Hope this would help you.
Jan Pieter Posthuma
"Balaji" wrote:
> Hey all,
> Is there anywhere that I could download trial version of SQL 2005 Reporting
> services alone...not the whole junk of SQL Server 2005. I need just the
> Reporting services. another question is I have SQL 2005 Developer Edition
> CTP(community tchnology preview) DVD and I am looking at a way to upgrade
> only reporting services from 2000 to 2005.But the set up wont let me do just
> that. It insists that I upgrade the server also. Please let me know!!!
>
Download Windows server
Hi!
I am confused ...downloaded Microsoft SQL server 2005 (for reporting services) to my Windows 2002 (32-bit systems), but it asks me to install the service packs as well...
I get the following answer though "Your OS does nor support the Service Pack required for this SQL server release."
I am confused ...downloaded Microsoft SQL server 2005 (for reporting services) to my Windows 2002 (32-bit systems), but it asks me to install the service packs as well...
So Windows XP Service Pack 2 is already installed.
And I need to download Windows server 2000 or 2003 R2, but where could I find a free trial version?
Do I also need Asp.net and IIS?
I would be very grateful for some help... to clarify which components needed.
Since you're wanting RS, you'll need to install SQL Server Express with Advanced Services. Here's the link:
http://msdn.microsoft.com/vstudio/express/sql/compare/default.aspx
This product is supported on XP SP2, so you won't need to do any OS upgrades.
Thanks,
Sam Lester (MSFT)
I get the following answer though "Your OS does nor support the Service Pack required for this SQL server release."
So my OS is 2002...
How do I check which SP required?
I did not find any .net Framework 2.0 SP.|||I managed to download SQL Server 2005 Express Edition with Advanced
Services SP1, and noticed Reporting services are available but how about "Analysis services" ?
|||
Analysis Services does not ship with any of the Express SKUs. It is part of the other SKUs (Enterprise, Standard, etc). If you want to play around with it, you can download the evaluation version found here:
http://www.microsoft.com/sql/downloads/trial-software.mspx
Thanks,
Sam Lester (MSFT)
Download SQL Server 7.0
Hi,
I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
and especified this necessitily installation SQL Server 7.0 before.
Thanks.
Dlson Fernandes
You gotta buy it
Paul Bergson
"Dlson Fernandes" <dilsonfernandes@.bol.com.br> wrote in message
news:uU580E9VFHA.584@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
> and especified this necessitily installation SQL Server 7.0 before.
> Thanks.
> Dlson Fernandes
I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
and especified this necessitily installation SQL Server 7.0 before.
Thanks.
Dlson Fernandes
You gotta buy it
Paul Bergson
"Dlson Fernandes" <dilsonfernandes@.bol.com.br> wrote in message
news:uU580E9VFHA.584@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
> and especified this necessitily installation SQL Server 7.0 before.
> Thanks.
> Dlson Fernandes
Download SQL Server 7.0
Hi,
I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
and especified this necessitily installation SQL Server 7.0 before.
Thanks.
Dlson FernandesYou gotta buy it
Paul Bergson
"Dlson Fernandes" <dilsonfernandes@.bol.com.br> wrote in message
news:uU580E9VFHA.584@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
> and especified this necessitily installation SQL Server 7.0 before.
> Thanks.
> Dlson Fernandes
I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
and especified this necessitily installation SQL Server 7.0 before.
Thanks.
Dlson FernandesYou gotta buy it
Paul Bergson
"Dlson Fernandes" <dilsonfernandes@.bol.com.br> wrote in message
news:uU580E9VFHA.584@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need download SQL Server 7.0 urgentily. Im going to install SMS 2.0,
> and especified this necessitily installation SQL Server 7.0 before.
> Thanks.
> Dlson Fernandes
Download SQL Server 7.0
Hi,
I need download SQL Server 7.0 urgentily. I´m going to install SMS 2.0,
and especified this necessitily installation SQL Server 7.0 before.
Thanks.
Dílson FernandesYou gotta buy it
--
Paul Bergson
"Dílson Fernandes" <dilsonfernandes@.bol.com.br> wrote in message
news:uU580E9VFHA.584@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need download SQL Server 7.0 urgentily. I´m going to install SMS 2.0,
> and especified this necessitily installation SQL Server 7.0 before.
> Thanks.
> Dílson Fernandes
I need download SQL Server 7.0 urgentily. I´m going to install SMS 2.0,
and especified this necessitily installation SQL Server 7.0 before.
Thanks.
Dílson FernandesYou gotta buy it
--
Paul Bergson
"Dílson Fernandes" <dilsonfernandes@.bol.com.br> wrote in message
news:uU580E9VFHA.584@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need download SQL Server 7.0 urgentily. I´m going to install SMS 2.0,
> and especified this necessitily installation SQL Server 7.0 before.
> Thanks.
> Dílson Fernandes
Download Reporting Services
I have SQL Server 2000 . where I can download Reporting Services and how to install it? because in microsoft.com all explanations are very confused.
thanks
You can download Evaluation Edition and SP2:
SQL Server 2000 Reporting Services Evaluation Edition
SQL Server 2000 Reporting Services Service Pack 2 (SP2)
For SQL Server 2000 Reporting Services installation CD please contact your local Microsoft sales office
Wednesday, March 21, 2012
Downgrade Install Plan
We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:
1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.
2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).
3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).
4. Apply sp4.
5. Restore user databases.
Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.
Thanks!
Michelle
1. What is the version of current SQL Server? SQL Server 2005 requires SP1 for Windows 2003 Enterprise Edittion on x64 machines.
2. I do not think you can install SQL Server 2000 with SQL Server 2005 product key.
The following issues are clear.
1. SQL Server 2000 and SQL Server 2005 can be installed side by side successfully.
2. 32-bit SQL Server 2000/2005 can be installed side by side successfully on x64 machines.
3. 32-bit SQL Server 2005 and 64-bit SQL Server 2005 can be installed successfully on x64 machines.
|||I did talk to our Microsoft Solution Specialist and he explained thatwe should already have the required license and media to install SQL
Server 2000 with our most recent media kit shipment. I don't think that
I will be prompted for a license key at all.
I'm hoping that the server admin team will be finished with the
hardware/os in the next couple of days so that I can start on my
portion. I'll document any issues that I have.
Thanks,
Michelle|||
Michelle,
Did you have any problems with your original installation plan? We are trying to do the same installation and it is unclear how to install 2000 with 2005 disks and keys. There is no prompting on install.
|||I did not have any problems but in hindsight had wished that I hadinstalled SQL Server 2005 as the default instance and 2000 as a named
instance. I believe that this would have made the upgrade to 2005
simpler. We have since built other machines this way.
Downgrade Install Plan
We are upgrading an application that is not yet supported on SQL Server 2005. The upgrade involves new hardware (including a new sql server). Any gotchas or advice regarding this plan:
1. Install Windows 2003 64 bit, configure hardware appropriately for running SQL Server.
2. Install SQL Server 2000 64 bit using the 2005 license key (is that how you 'downgrade'? I didn't see a 'how-to' article regarding this).
3. Restore backups of system databases from current SQL Server to new SQL Server (note: current SQL Server is running 32 bit - I realize that I need to make sure that I have the same service pack on the new server as that on the current server).
4. Apply sp4.
5. Restore user databases.
Not sure if the 32 vs. 64 bit thing is of any concern or if 'downgrading' is as simple as this.
Thanks!
Michelle
1. What is the version of current SQL Server? SQL Server 2005 requires SP1 for Windows 2003 Enterprise Edittion on x64 machines.
2. I do not think you can install SQL Server 2000 with SQL Server 2005 product key.
The following issues are clear.
1. SQL Server 2000 and SQL Server 2005 can be installed side by side successfully.
2. 32-bit SQL Server 2000/2005 can be installed side by side successfully on x64 machines.
3. 32-bit SQL Server 2005 and 64-bit SQL Server 2005 can be installed successfully on x64 machines.
|||I did talk to our Microsoft Solution Specialist and he explained that we should already have the required license and media to install SQL Server 2000 with our most recent media kit shipment. I don't think that I will be prompted for a license key at all.I'm hoping that the server admin team will be finished with the hardware/os in the next couple of days so that I can start on my portion. I'll document any issues that I have.
Thanks,
Michelle
|||
Michelle,
Did you have any problems with your original installation plan? We are trying to do the same installation and it is unclear how to install 2000 with 2005 disks and keys. There is no prompting on install.
|||I did not have any problems but in hindsight had wished that I had installed SQL Server 2005 as the default instance and 2000 as a named instance. I believe that this would have made the upgrade to 2005 simpler. We have since built other machines this way.Monday, March 19, 2012
Doubt with Client Network Utility
Hi. I've been worling with Ms SQL Server 7 / 2000 and on every installation
I've done, after installing the Server I had to Install Connectivity Only on
Clients in order to configure Client Network Utility to add the Server
Alias.
Does MSDE have an option like this ? Does MSDE Needs a Client Network
Utility on a Client PC?
Thanks,
Juan M. Rodriguez
Servicios Profesionales
teg solutions argentina s.a.
juan@.tegsolutions.com
Tel: 54-11-4590-2222
Fax: 54-11-4590-2201
www.tegsolutions.com
La calidad no est en el trabajo que hace la gente, sino en la gente que
hace el trabajo.
hi Juan,
"Juan Rodriguez" <juan@.tegsolutions.com> ha scritto nel messaggio
news:O40GyxCZEHA.2812@.TK2MSFTNGP11.phx.gbl...
> Hi. I've been worling with Ms SQL Server 7 / 2000 and on every
installation
> I've done, after installing the Server I had to Install Connectivity Only
on
> Clients in order to configure Client Network Utility to add the Server
> Alias.
> Does MSDE have an option like this ? Does MSDE Needs a Client Network
> Utility on a Client PC?
> Thanks,
MDAC installs the Client Network Utility (cliconfg.exe) as well... and it's
usually required from all apps... =;-)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks !
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:2l2h5lF7msb3U1@.uni-berlin.de...[vbcol=seagreen]
> hi Juan,
> "Juan Rodriguez" <juan@.tegsolutions.com> ha scritto nel messaggio
> news:O40GyxCZEHA.2812@.TK2MSFTNGP11.phx.gbl...
> installation
Only
> on
> MDAC installs the Client Network Utility (cliconfg.exe) as well... and
it's
> usually required from all apps... =;-)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
I've done, after installing the Server I had to Install Connectivity Only on
Clients in order to configure Client Network Utility to add the Server
Alias.
Does MSDE have an option like this ? Does MSDE Needs a Client Network
Utility on a Client PC?
Thanks,
Juan M. Rodriguez
Servicios Profesionales
teg solutions argentina s.a.
juan@.tegsolutions.com
Tel: 54-11-4590-2222
Fax: 54-11-4590-2201
www.tegsolutions.com
La calidad no est en el trabajo que hace la gente, sino en la gente que
hace el trabajo.
hi Juan,
"Juan Rodriguez" <juan@.tegsolutions.com> ha scritto nel messaggio
news:O40GyxCZEHA.2812@.TK2MSFTNGP11.phx.gbl...
> Hi. I've been worling with Ms SQL Server 7 / 2000 and on every
installation
> I've done, after installing the Server I had to Install Connectivity Only
on
> Clients in order to configure Client Network Utility to add the Server
> Alias.
> Does MSDE have an option like this ? Does MSDE Needs a Client Network
> Utility on a Client PC?
> Thanks,
MDAC installs the Client Network Utility (cliconfg.exe) as well... and it's
usually required from all apps... =;-)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks !
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:2l2h5lF7msb3U1@.uni-berlin.de...[vbcol=seagreen]
> hi Juan,
> "Juan Rodriguez" <juan@.tegsolutions.com> ha scritto nel messaggio
> news:O40GyxCZEHA.2812@.TK2MSFTNGP11.phx.gbl...
> installation
Only
> on
> MDAC installs the Client Network Utility (cliconfg.exe) as well... and
it's
> usually required from all apps... =;-)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Sunday, March 11, 2012
double click SQL Server Express and install with sa password
Hi!
Is it possible to double click the sql server express installer, it will install sql server 2005 in silent mode, set sa password..
Just want alternative of command installation on double click
setup.exe /qb INSTANCENAME=<InstanceName> SAPWD=<StrongPassword>
is it possible
thanks in advance
No, double-clicking the installer will always launch in UI mode, not quite mode.
Mike
|||Thanks for your answer
Is there any way, the installer automatically checks the settings file while installation. On double click it reads instructions from the ini file and continue installation...
Asif Mahboob
|||Perhaps these will help.
SQL Server 2005 UnAttended Installations
http://msdn2.microsoft.com/en-us/library/ms144259.aspx
http://www.devx.com/dbzone/Article/31648
Sunday, February 26, 2012
Domain user account
New to SQL Server. Plan to install SQL Server 2005 standard edition on Windows 2k3. After searched a lot of places, still don't understand what exactly "domain user account" is. Could someone explain it to me?
1. Is this a OS account where SQL Server is running?
2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it?
3. Or, is this an account in SQL Server?
1. Is this a OS account where SQL Server is running?
2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it?
3. Or, is this an account in SQL Server?
Where is this account located? How do I manage it?
TIA.
A domain account in the Windows world is a user account in a shared security database. The current domain system is called Active Directory. It does not only store user accounts but a wide range of data used in a networking system (groups, computers, printers, software packages...). Those entities are stored on domain controllers, i.e. Windows Server with some services implementing the server side of a domain. You can have multiple domain controllers which replicate the domain data like user accounts with each other. Computers and users which are part of the domain can be authenticated by those domain controllers, so they can get authorized to execute tasks on their or other computers in the domain.
So:
1) Typically not, only if your SQL Server is running on a Windows Server which is also domain controller.
2) Yes, the account is from a domain controller, or from the security database of a domain which is hosted on its domain controllers. A DNS server plays no specific role here, except that Active Directory does need a DNS server. You create those account with Start->Programs->Administrative Templates->Active Directory Users And Computers. This management console is installed on domain contollers. You can manually install it from adminpak.msi which exists on Servers under windows\system32.
3) No. You can "import" a domain account to give it login rights and assign database roles.
The nice part about domain accounts is, that you have a centralized place for user authentication, once authenticated on a system that authentication can be used agains other computers of the same domain and be authorized to do things on those computers. In contrast, in a workgroup you would need to log on to every computer indivually, except when you manage to have your user account and password synchronized manually on all machines you want to access.
--
SvenC
Thank you for your response.
I should state my situation more clearly. Three MS 2003 servers. Plan to install sql server 2005 on them. One as principle, one as mirror, and one as witness. Don't have any control on domain controller.
I can see my computers on my MS Windows Network. I guess that I only have computer account on domain controller. Is it true only the administrator on domain controller can add a domain user account? If a domain user account has been added, how do I use this account in my local 2003 server to run sql server services? Where to put domain user name and password? How do I know this domain user is in trusted domains? In order to setup mirroring, should I use this account on all three machines?
My database will only be used to accept client requests from IIS on another machine. If running sql services under domain user account is too much trouble, create same local user account on all the machine and run service under this same user account, will this work for mirroring. Do I need to create certificate?
Just try to find an easy way to setup mirroring. MS BOL is not much helpful.
|||You can set a domain account as your service account, using the SQL Server Configuration Manager tool. The SQL Server 2005 setup program will also allow you to select a domain account as the service account. For questions on setting up database mirroring, you should however post on the Database Mirroring forum instead of this one.
Thanks
Laurentiu
Domain user account
New to SQL Server. Plan to install SQL Server 2005 standard edition on Windows 2k3. After searched a lot of places, still don't understand what exactly "domain user account" is. Could someone explain it to me?
1. Is this a OS account where SQL Server is running?
2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it?
3. Or, is this an account in SQL Server?
1. Is this a OS account where SQL Server is running?
2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it?
3. Or, is this an account in SQL Server?
Where is this account located? How do I manage it?
TIA.
A domain account in the Windows world is a user account in a shared security database. The current domain system is called Active Directory. It does not only store user accounts but a wide range of data used in a networking system (groups, computers, printers, software packages...). Those entities are stored on domain controllers, i.e. Windows Server with some services implementing the server side of a domain. You can have multiple domain controllers which replicate the domain data like user accounts with each other. Computers and users which are part of the domain can be authenticated by those domain controllers, so they can get authorized to execute tasks on their or other computers in the domain.
So:
1) Typically not, only if your SQL Server is running on a Windows Server which is also domain controller.
2) Yes, the account is from a domain controller, or from the security database of a domain which is hosted on its domain controllers. A DNS server plays no specific role here, except that Active Directory does need a DNS server. You create those account with Start->Programs->Administrative Templates->Active Directory Users And Computers. This management console is installed on domain contollers. You can manually install it from adminpak.msi which exists on Servers under windows\system32.
3) No. You can "import" a domain account to give it login rights and assign database roles.
The nice part about domain accounts is, that you have a centralized place for user authentication, once authenticated on a system that authentication can be used agains other computers of the same domain and be authorized to do things on those computers. In contrast, in a workgroup you would need to log on to every computer indivually, except when you manage to have your user account and password synchronized manually on all machines you want to access.
--
SvenC
Thank you for your response.
I should state my situation more clearly. Three MS 2003 servers. Plan to install sql server 2005 on them. One as principle, one as mirror, and one as witness. Don't have any control on domain controller.
I can see my computers on my MS Windows Network. I guess that I only have computer account on domain controller. Is it true only the administrator on domain controller can add a domain user account? If a domain user account has been added, how do I use this account in my local 2003 server to run sql server services? Where to put domain user name and password? How do I know this domain user is in trusted domains? In order to setup mirroring, should I use this account on all three machines?
My database will only be used to accept client requests from IIS on another machine. If running sql services under domain user account is too much trouble, create same local user account on all the machine and run service under this same user account, will this work for mirroring. Do I need to create certificate?
Just try to find an easy way to setup mirroring. MS BOL is not much helpful.
|||You can set a domain account as your service account, using the SQL Server Configuration Manager tool. The SQL Server 2005 setup program will also allow you to select a domain account as the service account. For questions on setting up database mirroring, you should however post on the Database Mirroring forum instead of this one.
Thanks
Laurentiu
Friday, February 24, 2012
Domain Groups For Clustering Service ?? SQL Server 2005
When I install the Cluster with Version of SQL 2005 CTP September ...
After the Service Accounts (Clusters) page,
Domain Groups For Clustering Service Page appears.
How Can i configure this page...there is no information about it on BOL of
SQL 2005
In my opinion , fill them with New SQL Groups is created when SQL Server
Installs such as
SQLServer2005MSSQLUser$InstanceName,SQLServer2005S QLAgentUser$InstanceName
and SQLServer2005MSFTESQLUser$InstanceName.
But in this Phase, those group was not created automatically...
So, I try to generate those groups Manually, but Failed...with error message
like "One or more domain groups could not be verified ..."
And i Try to use Domain Admins...but Failed with same error messages...
i found about BOL directions in "Setup\help\1033" folder like follows
(
For each clustered service in the instance of SQL Server that you are
installing, enter the domain and group name in the format
<DomainName>\<GroupName>, subject to the following guidelines:
The domain and group names must already exist. If necessary, ask your domain
administrator for the names of existing domain groups, or to create domain
groups for your failover cluster.
The account under which SQL Server Setup is running must have privileges to
add accounts to the domain groups.
Each service should use a different domain group.
The SQL Server domain groups should not be shared with any other application.
Note that SQL Server accounts will not be removed from the groups if SQL
Server is uninstalled or if the accounts are changed. A domain administrator
must ensure that all unwanted accounts are removed following removal of SQL
Server.
)
So, I made three domain groups and put into builtin Administratos group.
and then proceed ahead.
Failed with same error messages...
help me...!!!
"JEYAI"?? ??? ??:
> When I install the Cluster with Version of SQL 2005 CTP September ...
> After the Service Accounts (Clusters) page,
> Domain Groups For Clustering Service Page appears.
> How Can i configure this page...there is no information about it on BOL of
> SQL 2005
> In my opinion , fill them with New SQL Groups is created when SQL Server
> Installs such as
> SQLServer2005MSSQLUser$InstanceName,SQLServer2005S QLAgentUser$InstanceName
> and SQLServer2005MSFTESQLUser$InstanceName.
> But in this Phase, those group was not created automatically...
> So, I try to generate those groups Manually, but Failed...with error message
> like "One or more domain groups could not be verified ..."
> And i Try to use Domain Admins...but Failed with same error messages...
|||You need to manually add the service accounts you specify during setup into
the groups before running setup (if you're having this issue - you shouldn't
really have to do this). I had the exact same issue and manually adding the
service account to them worked fine. Generally there will be 3 groups
(SQLServer/Agent + FullText). If you use the same service account for the
services then just add that to each of the 3 domain groups you create.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JEYAI" <JEYAI@.discussions.microsoft.com> wrote in message
news:79B54E21-BEB4-43E9-9880-7EAFE0FD5F92@.microsoft.com...[vbcol=seagreen]
>i found about BOL directions in "Setup\help\1033" folder like follows
> (
> For each clustered service in the instance of SQL Server that you are
> installing, enter the domain and group name in the format
> <DomainName>\<GroupName>, subject to the following guidelines:
> The domain and group names must already exist. If necessary, ask your
> domain
> administrator for the names of existing domain groups, or to create domain
> groups for your failover cluster.
>
> The account under which SQL Server Setup is running must have privileges
> to
> add accounts to the domain groups.
>
> Each service should use a different domain group.
>
> The SQL Server domain groups should not be shared with any other
> application.
>
> Note that SQL Server accounts will not be removed from the groups if SQL
> Server is uninstalled or if the accounts are changed. A domain
> administrator
> must ensure that all unwanted accounts are removed following removal of
> SQL
> Server.
> )
> So, I made three domain groups and put into builtin Administratos group.
> and then proceed ahead.
> Failed with same error messages...
> help me...!!!
> "JEYAI"? ? ?:
|||Thanks Jasper,
Following your directions,
I made three domain groups named as SQLUsers,AgentUsers,FTUsers
and put them into Built in Administrators group.
and then put the Service Account named as SQLService and administrator
account into three new groups.
But, in the page of Domain Groups For Clustering Service ,
Same Error message occured...
What did i miss ?
"Jasper Smith"?? ??? ??:
> You need to manually add the service accounts you specify during setup into
> the groups before running setup (if you're having this issue - you shouldn't
> really have to do this). I had the exact same issue and manually adding the
> service account to them worked fine. Generally there will be 3 groups
> (SQLServer/Agent + FullText). If you use the same service account for the
> services then just add that to each of the 3 domain groups you create.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "JEYAI" <JEYAI@.discussions.microsoft.com> wrote in message
> news:79B54E21-BEB4-43E9-9880-7EAFE0FD5F92@.microsoft.com...
>
>
|||The readme file describes this.
In section 3.5.15, there are descriptions of Security Groups and Domain
Controllers.
Microsoft SQL Server September 2005 Community Technology Preview
http://download.microsoft.com/downlo...up_issues_238p
Sincerely,
Anthony Thomas
"JEYAI" <JEYAI@.discussions.microsoft.com> wrote in message
news:5B999CCC-1E77-4F3D-B52B-E34DC95752BA@.microsoft.com...[vbcol=seagreen]
> Thanks Jasper,
> Following your directions,
> I made three domain groups named as SQLUsers,AgentUsers,FTUsers
> and put them into Built in Administrators group.
> and then put the Service Account named as SQLService and administrator
> account into three new groups.
> But, in the page of Domain Groups For Clustering Service ,
> Same Error message occured...
> What did i miss ?
> "Jasper Smith"? ? ?:
into[vbcol=seagreen]
shouldn't[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
domain[vbcol=seagreen]
privileges[vbcol=seagreen]
SQL[vbcol=seagreen]
of[vbcol=seagreen]
group.[vbcol=seagreen]
BOL[vbcol=seagreen]
Server[vbcol=seagreen]
SQLServer2005MSSQLUser$InstanceName,SQLServer2005S QLAgentUser$InstanceName[vbcol=seagreen]
messages...[vbcol=seagreen]
After the Service Accounts (Clusters) page,
Domain Groups For Clustering Service Page appears.
How Can i configure this page...there is no information about it on BOL of
SQL 2005
In my opinion , fill them with New SQL Groups is created when SQL Server
Installs such as
SQLServer2005MSSQLUser$InstanceName,SQLServer2005S QLAgentUser$InstanceName
and SQLServer2005MSFTESQLUser$InstanceName.
But in this Phase, those group was not created automatically...
So, I try to generate those groups Manually, but Failed...with error message
like "One or more domain groups could not be verified ..."
And i Try to use Domain Admins...but Failed with same error messages...
i found about BOL directions in "Setup\help\1033" folder like follows
(
For each clustered service in the instance of SQL Server that you are
installing, enter the domain and group name in the format
<DomainName>\<GroupName>, subject to the following guidelines:
The domain and group names must already exist. If necessary, ask your domain
administrator for the names of existing domain groups, or to create domain
groups for your failover cluster.
The account under which SQL Server Setup is running must have privileges to
add accounts to the domain groups.
Each service should use a different domain group.
The SQL Server domain groups should not be shared with any other application.
Note that SQL Server accounts will not be removed from the groups if SQL
Server is uninstalled or if the accounts are changed. A domain administrator
must ensure that all unwanted accounts are removed following removal of SQL
Server.
)
So, I made three domain groups and put into builtin Administratos group.
and then proceed ahead.
Failed with same error messages...
help me...!!!
"JEYAI"?? ??? ??:
> When I install the Cluster with Version of SQL 2005 CTP September ...
> After the Service Accounts (Clusters) page,
> Domain Groups For Clustering Service Page appears.
> How Can i configure this page...there is no information about it on BOL of
> SQL 2005
> In my opinion , fill them with New SQL Groups is created when SQL Server
> Installs such as
> SQLServer2005MSSQLUser$InstanceName,SQLServer2005S QLAgentUser$InstanceName
> and SQLServer2005MSFTESQLUser$InstanceName.
> But in this Phase, those group was not created automatically...
> So, I try to generate those groups Manually, but Failed...with error message
> like "One or more domain groups could not be verified ..."
> And i Try to use Domain Admins...but Failed with same error messages...
|||You need to manually add the service accounts you specify during setup into
the groups before running setup (if you're having this issue - you shouldn't
really have to do this). I had the exact same issue and manually adding the
service account to them worked fine. Generally there will be 3 groups
(SQLServer/Agent + FullText). If you use the same service account for the
services then just add that to each of the 3 domain groups you create.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JEYAI" <JEYAI@.discussions.microsoft.com> wrote in message
news:79B54E21-BEB4-43E9-9880-7EAFE0FD5F92@.microsoft.com...[vbcol=seagreen]
>i found about BOL directions in "Setup\help\1033" folder like follows
> (
> For each clustered service in the instance of SQL Server that you are
> installing, enter the domain and group name in the format
> <DomainName>\<GroupName>, subject to the following guidelines:
> The domain and group names must already exist. If necessary, ask your
> domain
> administrator for the names of existing domain groups, or to create domain
> groups for your failover cluster.
>
> The account under which SQL Server Setup is running must have privileges
> to
> add accounts to the domain groups.
>
> Each service should use a different domain group.
>
> The SQL Server domain groups should not be shared with any other
> application.
>
> Note that SQL Server accounts will not be removed from the groups if SQL
> Server is uninstalled or if the accounts are changed. A domain
> administrator
> must ensure that all unwanted accounts are removed following removal of
> SQL
> Server.
> )
> So, I made three domain groups and put into builtin Administratos group.
> and then proceed ahead.
> Failed with same error messages...
> help me...!!!
> "JEYAI"? ? ?:
|||Thanks Jasper,
Following your directions,
I made three domain groups named as SQLUsers,AgentUsers,FTUsers
and put them into Built in Administrators group.
and then put the Service Account named as SQLService and administrator
account into three new groups.
But, in the page of Domain Groups For Clustering Service ,
Same Error message occured...
What did i miss ?
"Jasper Smith"?? ??? ??:
> You need to manually add the service accounts you specify during setup into
> the groups before running setup (if you're having this issue - you shouldn't
> really have to do this). I had the exact same issue and manually adding the
> service account to them worked fine. Generally there will be 3 groups
> (SQLServer/Agent + FullText). If you use the same service account for the
> services then just add that to each of the 3 domain groups you create.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "JEYAI" <JEYAI@.discussions.microsoft.com> wrote in message
> news:79B54E21-BEB4-43E9-9880-7EAFE0FD5F92@.microsoft.com...
>
>
|||The readme file describes this.
In section 3.5.15, there are descriptions of Security Groups and Domain
Controllers.
Microsoft SQL Server September 2005 Community Technology Preview
http://download.microsoft.com/downlo...up_issues_238p
Sincerely,
Anthony Thomas
"JEYAI" <JEYAI@.discussions.microsoft.com> wrote in message
news:5B999CCC-1E77-4F3D-B52B-E34DC95752BA@.microsoft.com...[vbcol=seagreen]
> Thanks Jasper,
> Following your directions,
> I made three domain groups named as SQLUsers,AgentUsers,FTUsers
> and put them into Built in Administrators group.
> and then put the Service Account named as SQLService and administrator
> account into three new groups.
> But, in the page of Domain Groups For Clustering Service ,
> Same Error message occured...
> What did i miss ?
> "Jasper Smith"? ? ?:
into[vbcol=seagreen]
shouldn't[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
domain[vbcol=seagreen]
privileges[vbcol=seagreen]
SQL[vbcol=seagreen]
of[vbcol=seagreen]
group.[vbcol=seagreen]
BOL[vbcol=seagreen]
Server[vbcol=seagreen]
SQLServer2005MSSQLUser$InstanceName,SQLServer2005S QLAgentUser$InstanceName[vbcol=seagreen]
messages...[vbcol=seagreen]
Domain group members cannot connect [SQL Server 2k5 Workgroup Ed.]
We have a brand new out-of-the-box SQL Server 2005 Workgroup Edition install
.
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access.
The problem is that when users try to connect to the SQL server, they cannot
connect. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
user is properly a member of group added as a login to SQL Server, and we've
confirmed that there are not conflicting permissions that would deny those
users access via another route.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same users a member of THAT group, and finally then
follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
~JimIs the server that SQL is on joined to the domain?
Jim Kilmer wrote:
> We have a brand new out-of-the-box SQL Server 2005 Workgroup Edition insta
ll.
> We are using Windows Authentication, and have created SQL logins for about
> 40 different groups on our domain. We've given those logins the appropria
te
> permissions on the databases they're supposed to be able to access.
> The problem is that when users try to connect to the SQL server, they cann
ot
> connect. An error 18456 is thrown, and logged in the Application event lo
g
> stating "Login failed for user OURDOMAIN\theuser" (example values). The
> user is properly a member of group added as a login to SQL Server, and we'
ve
> confirmed that there are not conflicting permissions that would deny those
> users access via another route.
> This is only a problem for domain-based groups. If we create a local grou
p
> on the SQL server machine, through Computer Management -> Local Users and
> Groups, then make the same users a member of THAT group, and finally the
n
> follow the same process to add that local group to SQL Server Logins and s
et
> the database privileges, it works!!
> Our group memberships change frequently, and are used for a lot more than
> just SQL server permissions. So, using local groups and maintaining
> membership in both places is not really feasible. Any ideas why a local
> machine group containing domain user accounts would work fine, but a domai
n
> group containing the same accounts would not?
> Thanks in advance.
> ~Jim
.
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access.
The problem is that when users try to connect to the SQL server, they cannot
connect. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
user is properly a member of group added as a login to SQL Server, and we've
confirmed that there are not conflicting permissions that would deny those
users access via another route.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same users a member of THAT group, and finally then
follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
~JimIs the server that SQL is on joined to the domain?
Jim Kilmer wrote:
> We have a brand new out-of-the-box SQL Server 2005 Workgroup Edition insta
ll.
> We are using Windows Authentication, and have created SQL logins for about
> 40 different groups on our domain. We've given those logins the appropria
te
> permissions on the databases they're supposed to be able to access.
> The problem is that when users try to connect to the SQL server, they cann
ot
> connect. An error 18456 is thrown, and logged in the Application event lo
g
> stating "Login failed for user OURDOMAIN\theuser" (example values). The
> user is properly a member of group added as a login to SQL Server, and we'
ve
> confirmed that there are not conflicting permissions that would deny those
> users access via another route.
> This is only a problem for domain-based groups. If we create a local grou
p
> on the SQL server machine, through Computer Management -> Local Users and
> Groups, then make the same users a member of THAT group, and finally the
n
> follow the same process to add that local group to SQL Server Logins and s
et
> the database privileges, it works!!
> Our group memberships change frequently, and are used for a lot more than
> just SQL server permissions. So, using local groups and maintaining
> membership in both places is not really feasible. Any ideas why a local
> machine group containing domain user accounts would work fine, but a domai
n
> group containing the same accounts would not?
> Thanks in advance.
> ~Jim
Domain group logins failing on SQL 2k5 workgroup
This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access.
The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've
confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then
follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
Hi,
see if the default database defined for the users / groups ius available and they are granted access to the database. If not they will be denied access to the server and will get the error message posted by you. Did you try to create a single Windows and login with this user ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||Single user: Yes. Creating individual logins for domain users works fine. It is only logins for domain groups that are not working.
Default database: The users are connecting via ODBC connections, and the default database is set correctly.
It doesn't seem to be related to any database selection issues at all. Within a single database, if we grant access to the individual user account, or a local machine group that the user is a part of, everything works fine. Grant them access via a domain group, and it denies login. This is not something we've encountered before, and is making me wonder if there is some weird, poorly-documented restriction in the Workgroup Edition...|||
Please post the error as it is printed in the errorlog file of SQL Server (the ones under MSSQL\...\LOG\ERRORLOG*). Post both the error messages and the error numbers and states - the states are important.
Thanks
Laurentiu
With group OURDOMAIN\SecGroupA created on the domain controller, and user 'kswain' made a member of the group. We create a SQL Server login for OURDOMAIN\SecGroupA and get:
2006-12-27 10:45:02.50 Logon Error: 18456, Severity: 14, State: 11.
2006-12-27 10:45:02.50 Logon Login failed for user 'OURDOMAIN\kswain'. [CLIENT: xxx.xxx.xxx.xxx]
With local group TestLocalGroup created on the SQL Server machine, and user 'OURDOMAIN\kswain' added as a member: We create a SQL Server login for SERVERMACHINE\TestLocalGroup using the same process as previously, and it works fine. We don't even have to log the end-user account out of the application... it works as soon as we authorize the local group.|||
Hi,
Does this error comes when you access from your Application or via Query Analyzer ? Are you able to login via Query Analyzer?
What application you are running !? A web application ? Ensure IIS Permission is also properly set refer below KB
http://support.microsoft.com/kb/316989/
What about connection string in your application ?
Hemantgiri S. Goswami
|||The login failure occurs both from the application and from Query Analyzer using any non-Administrator account.Our testbed application at the moment is actually just an Access database, using the built-in Windows SQL Server ODBC driver, set up as a Machine DSN. When our main app didn't work, we created the simplest method we could think of to try and connect. We are not using IIS for this at all. We know the DSN itself is set up correctly since it works if the user is explicitly added, or is part of a SQL Server machine-local group.
--
One additional thing we've discovered in the last 24 hours. It still does NOT work if you add a domain group to a local group. So the issue seems to be one of domain group membership resolution. In other words, if we authorize SQLServer\LocalGroupA:
* If OURDOMAIN\userA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => OK
* If OURDOMAIN\userA is a member of OURDOMAIN\DomainGroupA, and OURDOMAIN\DomainGroupA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => FAIL!
Other thoughts we're having that might be somehow relevant, but we can't seem to get around:
1) The domain is mixed Win2000 and Win2003. The SQL Server 2k5 is running on a Win2003 machine that is not a domain controller, but is a domain member.
2) Our AD domain name has a hyphen in it, both in NetBIOS and FQDN (i.e. OUR-DOMAIN and cleveland.our-domain.local)
3) The non-administrative users are accessing the application server via Terminal Services.
None of the above should make a difference (and don't have any problems with SQL Server 2000), but we're really grasping at straws at this point...|||
Can you see if LookupAccountName works for the group name? If you have a small application called name2sid, you could use it to check this. Or you could use something similar to my CLR function from http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.
If this function works ok, then I suggest to open a report on the site indicated in the sticky thread at the top of this forum. You can start the server with the -y18456 parameter, to have it generate a memory dump, and you can attach the dump to the report.
Thanks
Laurentiu
I'm not familiar with the -y18456 parameter. I just restarted the SQL Server service with that flag included in the Startup Parameters, but don't see a dump anywhere, or anything especially instructive in the event log. Can you tell me what I should be looking for after restarting with that flag? Once I can find that, I'll open a report on the Connect site. Thanks!|||Please disregard previous request -- I see that it only outputs dumps when that specific error is thrown. Got it, and attaching it to a Connect bug now. Thanks!|||Just for closure on this thread, this issue has been moved to a Connect feedback/bug report. ID is 248615 and can be found here:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=248615|||
Hi,
Did you find a fix for this? I think we're having the same problem. I talked to a consultant who thought it was something with our domain since we were running windows 2000 and didnt have the windows DNS running as part of our domain. But everything was working except sql server so I should have known better. So we upgraded our domain controller and spent all kinds of money and it still doesn't work!! Please let me know if you figured out how to fix this!! None of our AD groups are working as logins. Only users and groups on the sql server machine.
Bob Coleman
|||No fix or workaround has been identified yet. Nobody at Microsoft has tagged the Connect bug referenced above, if it has even been reviewed yet. I'm trying to be patient, figuring that people were on vacation over the holidays.At the moment, we're just maintaining machine-local accounts with the appropriate domain users. Hopefully we'll get some kind of response shortly!|||
We have received your feedback report. When we'll have an update on this issue, we'll update the report.
I am not familiar with the PsSid tool - could you point me to the link from which you downloaded it?
The -y argument can be used with any error number, to make the server produce a dump whenever the error is raised.
Thanks
Laurentiu
It's part of the SysInternals command-line suite that MS acquired earlier this year. Nifty stuff.
Thanks!
Domain group logins failing on SQL 2k5 workgroup
This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access.
The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've
confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then
follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
Hi,
see if the default database defined for the users / groups ius available and they are granted access to the database. If not they will be denied access to the server and will get the error message posted by you. Did you try to create a single Windows and login with this user ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||Single user: Yes. Creating individual logins for domain users works fine. It is only logins for domain groups that are not working.
Default database: The users are connecting via ODBC connections, and the default database is set correctly.
It doesn't seem to be related to any database selection issues at all. Within a single database, if we grant access to the individual user account, or a local machine group that the user is a part of, everything works fine. Grant them access via a domain group, and it denies login. This is not something we've encountered before, and is making me wonder if there is some weird, poorly-documented restriction in the Workgroup Edition...|||
Please post the error as it is printed in the errorlog file of SQL Server (the ones under MSSQL\...\LOG\ERRORLOG*). Post both the error messages and the error numbers and states - the states are important.
Thanks
Laurentiu
With group OURDOMAIN\SecGroupA created on the domain controller, and user 'kswain' made a member of the group. We create a SQL Server login for OURDOMAIN\SecGroupA and get:
2006-12-27 10:45:02.50 Logon Error: 18456, Severity: 14, State: 11.
2006-12-27 10:45:02.50 Logon Login failed for user 'OURDOMAIN\kswain'. [CLIENT: xxx.xxx.xxx.xxx]
With local group TestLocalGroup created on the SQL Server machine, and user 'OURDOMAIN\kswain' added as a member: We create a SQL Server login for SERVERMACHINE\TestLocalGroup using the same process as previously, and it works fine. We don't even have to log the end-user account out of the application... it works as soon as we authorize the local group.|||
Hi,
Does this error comes when you access from your Application or via Query Analyzer ? Are you able to login via Query Analyzer?
What application you are running !? A web application ? Ensure IIS Permission is also properly set refer below KB
http://support.microsoft.com/kb/316989/
What about connection string in your application ?
Hemantgiri S. Goswami
|||The login failure occurs both from the application and from Query Analyzer using any non-Administrator account.Our testbed application at the moment is actually just an Access database, using the built-in Windows SQL Server ODBC driver, set up as a Machine DSN. When our main app didn't work, we created the simplest method we could think of to try and connect. We are not using IIS for this at all. We know the DSN itself is set up correctly since it works if the user is explicitly added, or is part of a SQL Server machine-local group.
--
One additional thing we've discovered in the last 24 hours. It still does NOT work if you add a domain group to a local group. So the issue seems to be one of domain group membership resolution. In other words, if we authorize SQLServer\LocalGroupA:
* If OURDOMAIN\userA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => OK
* If OURDOMAIN\userA is a member of OURDOMAIN\DomainGroupA, and OURDOMAIN\DomainGroupA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => FAIL!
Other thoughts we're having that might be somehow relevant, but we can't seem to get around:
1) The domain is mixed Win2000 and Win2003. The SQL Server 2k5 is running on a Win2003 machine that is not a domain controller, but is a domain member.
2) Our AD domain name has a hyphen in it, both in NetBIOS and FQDN (i.e. OUR-DOMAIN and cleveland.our-domain.local)
3) The non-administrative users are accessing the application server via Terminal Services.
None of the above should make a difference (and don't have any problems with SQL Server 2000), but we're really grasping at straws at this point...|||
Can you see if LookupAccountName works for the group name? If you have a small application called name2sid, you could use it to check this. Or you could use something similar to my CLR function from http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.
If this function works ok, then I suggest to open a report on the site indicated in the sticky thread at the top of this forum. You can start the server with the -y18456 parameter, to have it generate a memory dump, and you can attach the dump to the report.
Thanks
Laurentiu
I'm not familiar with the -y18456 parameter. I just restarted the SQL Server service with that flag included in the Startup Parameters, but don't see a dump anywhere, or anything especially instructive in the event log. Can you tell me what I should be looking for after restarting with that flag? Once I can find that, I'll open a report on the Connect site. Thanks!|||Please disregard previous request -- I see that it only outputs dumps when that specific error is thrown. Got it, and attaching it to a Connect bug now. Thanks!|||Just for closure on this thread, this issue has been moved to a Connect feedback/bug report. ID is 248615 and can be found here:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=248615|||
Hi,
Did you find a fix for this? I think we're having the same problem. I talked to a consultant who thought it was something with our domain since we were running windows 2000 and didnt have the windows DNS running as part of our domain. But everything was working except sql server so I should have known better. So we upgraded our domain controller and spent all kinds of money and it still doesn't work!! Please let me know if you figured out how to fix this!! None of our AD groups are working as logins. Only users and groups on the sql server machine.
Bob Coleman
|||No fix or workaround has been identified yet. Nobody at Microsoft has tagged the Connect bug referenced above, if it has even been reviewed yet. I'm trying to be patient, figuring that people were on vacation over the holidays.At the moment, we're just maintaining machine-local accounts with the appropriate domain users. Hopefully we'll get some kind of response shortly!|||
We have received your feedback report. When we'll have an update on this issue, we'll update the report.
I am not familiar with the PsSid tool - could you point me to the link from which you downloaded it?
The -y argument can be used with any error number, to make the server produce a dump whenever the error is raised.
Thanks
Laurentiu
It's part of the SysInternals command-line suite that MS acquired earlier this year. Nifty stuff.
Thanks!
Domain group logins failing on SQL 2k5 workgroup
This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access. The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
Hi,
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access. The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
Hi,
see if the default database defined for the users / groups ius available and they are granted access to the database. If not they will be denied access to the server and will get the error message posted by you. Did you try to create a single Windows and login with this user ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Single user: Yes. Creating individual logins for domain users works fine. It is only logins for domain groups that are not working.
Default database: The users are connecting via ODBC connections, and the default database is set correctly.
It doesn't seem to be related to any database selection issues at all. Within a single database, if we grant access to the individual user account, or a local machine group that the user is a part of, everything works fine. Grant them access via a domain group, and it denies login. This is not something we've encountered before, and is making me wonder if there is some weird, poorly-documented restriction in the Workgroup Edition...
|||
Please post the error as it is printed in the errorlog file of SQL Server (the ones under MSSQL\...\LOG\ERRORLOG*). Post both the error messages and the error numbers and states - the states are important.
Thanks
Laurentiu
With group OURDOMAIN\SecGroupA created on the domain controller, and user 'kswain' made a member of the group. We create a SQL Server login for OURDOMAIN\SecGroupA and get:
2006-12-27 10:45:02.50 Logon Error: 18456, Severity: 14, State: 11.
2006-12-27 10:45:02.50 Logon Login failed for user 'OURDOMAIN\kswain'. [CLIENT: xxx.xxx.xxx.xxx]
With local group TestLocalGroup created on the SQL Server machine, and user 'OURDOMAIN\kswain' added as a member: We create a SQL Server login for SERVERMACHINE\TestLocalGroup using the same process as previously, and it works fine. We don't even have to log the end-user account out of the application... it works as soon as we authorize the local group.
|||
Hi,
Does this error comes when you access from your Application or via Query Analyzer ? Are you able to login via Query Analyzer?
What application you are running !? A web application ? Ensure IIS Permission is also properly set refer below KB
http://support.microsoft.com/kb/316989/
What about connection string in your application ?
Hemantgiri S. Goswami
|||The login failure occurs both from the application and from Query Analyzer using any non-Administrator account.Our testbed application at the moment is actually just an Access database, using the built-in Windows SQL Server ODBC driver, set up as a Machine DSN. When our main app didn't work, we created the simplest method we could think of to try and connect. We are not using IIS for this at all. We know the DSN itself is set up correctly since it works if the user is explicitly added, or is part of a SQL Server machine-local group.
--
One additional thing we've discovered in the last 24 hours. It still does NOT work if you add a domain group to a local group. So the issue seems to be one of domain group membership resolution. In other words, if we authorize SQLServer\LocalGroupA:
* If OURDOMAIN\userA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => OK
* If OURDOMAIN\userA is a member of OURDOMAIN\DomainGroupA, and OURDOMAIN\DomainGroupA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => FAIL!
Other thoughts we're having that might be somehow relevant, but we can't seem to get around:
1) The domain is mixed Win2000 and Win2003. The SQL Server 2k5 is running on a Win2003 machine that is not a domain controller, but is a domain member.
2) Our AD domain name has a hyphen in it, both in NetBIOS and FQDN (i.e. OUR-DOMAIN and cleveland.our-domain.local)
3) The non-administrative users are accessing the application server via Terminal Services.
None of the above should make a difference (and don't have any problems with SQL Server 2000), but we're really grasping at straws at this point...
|||
Can you see if LookupAccountName works for the group name? If you have a small application called name2sid, you could use it to check this. Or you could use something similar to my CLR function from http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.
If this function works ok, then I suggest to open a report on the site indicated in the sticky thread at the top of this forum. You can start the server with the -y18456 parameter, to have it generate a memory dump, and you can attach the dump to the report.
Thanks
Laurentiu
I'm not familiar with the -y18456 parameter. I just restarted the SQL Server service with that flag included in the Startup Parameters, but don't see a dump anywhere, or anything especially instructive in the event log. Can you tell me what I should be looking for after restarting with that flag? Once I can find that, I'll open a report on the Connect site. Thanks!
|||Please disregard previous request -- I see that it only outputs dumps when that specific error is thrown. Got it, and attaching it to a Connect bug now. Thanks!
|||Just for closure on this thread, this issue has been moved to a Connect feedback/bug report. ID is 248615 and can be found here:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=248615
|||
Hi,
Did you find a fix for this? I think we're having the same problem. I talked to a consultant who thought it was something with our domain since we were running windows 2000 and didnt have the windows DNS running as part of our domain. But everything was working except sql server so I should have known better. So we upgraded our domain controller and spent all kinds of money and it still doesn't work!! Please let me know if you figured out how to fix this!! None of our AD groups are working as logins. Only users and groups on the sql server machine.
Bob Coleman
|||No fix or workaround has been identified yet. Nobody at Microsoft has tagged the Connect bug referenced above, if it has even been reviewed yet. I'm trying to be patient, figuring that people were on vacation over the holidays.At the moment, we're just maintaining machine-local accounts with the appropriate domain users. Hopefully we'll get some kind of response shortly!
|||
We have received your feedback report. When we'll have an update on this issue, we'll update the report.
I am not familiar with the PsSid tool - could you point me to the link from which you downloaded it?
The -y argument can be used with any error number, to make the server produce a dump whenever the error is raised.
Thanks
Laurentiu
It's part of the SysInternals command-line suite that MS acquired earlier this year. Nifty stuff.
Thanks!
Subscribe to:
Posts (Atom)