Automating the creation of a database

Hi;
We have a program (ASP.NET) that requires a database as it's back end. We
are trying to create an install that requires as little expertise as
possible. In other words, no DBA required.
For creating the database itself we are at that point. We use the registry
to find the location of osql.exe and use that to run the schema that creates
the database. I'ld prefer an API we could call so we can more cleanly handle
errors but this works fine 98% of the time.
The remaining problem is ownership of the created database.
1) Is there a way (in .NET 2.0) to query if the database is mixed mode
authentication.
2) And if it is a way to both get a list of all users
3) And to create a user?
We can already enum all domain users. So with the above we could give them a
list of all users they can choose from as the owner and also let then create
a new one - without the user ever having to run any SqlServer tool or even
have any installed.
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm> The remaining problem is ownership of the created database.
> 1) Is there a way (in .NET 2.0) to query if the database is mixed mode
> authentication.
It is SERVER property not a databases
SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
') AS
[IsIntegratedSecurityOnly]

> 2) And if it is a way to both get a list of all users
EXEC northwind..sp_helpuser

> 3) And to create a user?
Create Database mydb
go
use mydb
go
sp_addlogin 'mydbuser','monitor','mydb'
go
sp_adduser 'mydbuser'
go
sp_Addrolemember 'db_datawriter','mydbuser'
go
sp_Addrolemember 'db_datareader','mydbuser'
go
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:25882AC6-F4EF-422A-8B68-63ABE75AACF3@.microsoft.com...
> Hi;
> We have a program (ASP.NET) that requires a database as it's back end. We
> are trying to create an install that requires as little expertise as
> possible. In other words, no DBA required.
> For creating the database itself we are at that point. We use the registry
> to find the location of osql.exe and use that to run the schema that
> creates
> the database. I'ld prefer an API we could call so we can more cleanly
> handle
> errors but this works fine 98% of the time.
> The remaining problem is ownership of the created database.
> 1) Is there a way (in .NET 2.0) to query if the database is mixed mode
> authentication.
> 2) And if it is a way to both get a list of all users
> 3) And to create a user?
> We can already enum all domain users. So with the above we could give them
> a
> list of all users they can choose from as the owner and also let then
> create
> a new one - without the user ever having to run any SqlServer tool or even
> have any installed.
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
>|||Hi David,
I am afraid that the database may have some synchronous problem now. Our
yesterday's replies cannot be seen from Web and we also cannot see your
replies.
So I post it again from Outlook Express and hope you could see it now. Sorry
for bringing you any inconvenience.
I understand that your application used osql.exe to create the database and
you have three questions on the ownership of the created database now:
1. How to query (in .NET 2.0) if the database is with mixed authentication
mode?
2. How to get a list of all users?
3. How to create a user?
If I have misunderstood, please let me know.
For your three questions and even your creating database function, you can
fully resolve the questions by using the SQL Server SMO component for .NET
2.0.
1. You can just create a Server object like this:
//Server Name
string strConn = "(local)";
//Instantiate SMO Server Object
Server svr = new Server(strConn);
Console.Writeline(svr.Settings.LoginMode.ToString());
2. To get the list of all users, you can use:
Database db = server.Databases["your_db_name"];
UserCollection users = db.Users;
3. To create a user, you can use:
//Instantiate SMO Login object
Login l = new Login(svr, loginName);
//If Login doesn't already exist
if (!svr.Logins.Contains(loginName))
{
//Login should be of type Sql Login
l.LoginType = LoginType.SqlLogin;
//Create the Login on the SQL Server with password: pa$$w0rd
l.Create("pa$$w0rd");
//Add the login to the sysadmin role
l.AddToRole("sysadmin");
}
//Instantiate a new database object
Database db = new Database(svr, "Fizoo2");
//Make SQL Server create the database
db.Create();
//Instantiate a new User object
User u = new User(db, "SQL_Login_user");
//associated it with the login "SQL_Login"
u.Login = loginName;
//Make SQL Server create the user
u.Create();
For more information, you can refer to the following references:
User Privileges View & Create User Tool
http://forums.microsoft.com/MSDN/Sh...840637&SiteID=1
How to: Create a Visual C# SMO Project in Visual Studio .NET
http://msdn2.microsoft.com/it-it/library/ms162129.aspx
How to: Modify SQL Server Settings in Visual Basic .NET
http://msdn2.microsoft.com/en-us/library/ms162131.aspx
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:25882AC6-F4EF-422A-8B68-63ABE75AACF3@.microsoft.com...
> Hi;
> We have a program (ASP.NET) that requires a database as it's back end. We
> are trying to create an install that requires as little expertise as
> possible. In other words, no DBA required.
> For creating the database itself we are at that point. We use the registry
> to find the location of osql.exe and use that to run the schema that
> creates
> the database. I'ld prefer an API we could call so we can more cleanly
> handle
> errors but this works fine 98% of the time.
> The remaining problem is ownership of the created database.
> 1) Is there a way (in .NET 2.0) to query if the database is mixed mode
> authentication.
> 2) And if it is a way to both get a list of all users
> 3) And to create a user?
> We can already enum all domain users. So with the above we could give them
> a
> list of all users they can choose from as the owner and also let then
> create
> a new one - without the user ever having to run any SqlServer tool or even
> have any installed.
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
>|||Hi Dave,
I understand that your application used osql.exe to create the database and
you have three questions on the ownership of the created database now:
1. How to query (in .NET 2.0) if the database is with mixed authentication
mode?
2. How to get a list of all users?
3. How to create a user?
If I have misunderstood, please let me know.
For your three questions and even your creating database function, you can
fully resolve the questions by using the SQL Server SMO component for .NET
2.0.
1. You can just create a Server object like this:
//Server Name
string strConn = "(local)";
//Instantiate SMO Server Object
Server svr = new Server(strConn);
Console.Writeline(svr.Settings.LoginMode.ToString());
2. To get the list of all users, you can use:
Database db = server.Databases["your_db_name"];
UserCollection users = db.Users;
3. To create a user, you can use:
//Instantiate SMO Login object
Login l = new Login(svr, loginName);
//If Login doesn't already exist
if (!svr.Logins.Contains(loginName))
{
//Login should be of type Sql Login
l.LoginType = LoginType.SqlLogin;
//Create the Login on the SQL Server with password: pa$$w0rd
l.Create("pa$$w0rd");
//Add the login to the sysadmin role
l.AddToRole("sysadmin");
}
//Instantiate a new database object
Database db = new Database(svr, "Fizoo2");
//Make SQL Server create the database
db.Create();
//Instantiate a new User object
User u = new User(db, "SQL_Login_user");
//associated it with the login "SQL_Login"
u.Login = loginName;
//Make SQL Server create the user
u.Create();
For more information, you can refer to the following references:
User Privileges View & Create User Tool
http://forums.microsoft.com/MSDN/Sh...840637&SiteID=1
How to: Create a Visual C# SMO Project in Visual Studio .NET
http://msdn2.microsoft.com/it-it/library/ms162129.aspx
How to: Modify SQL Server Settings in Visual Basic .NET
http://msdn2.microsoft.com/en-us/library/ms162131.aspx
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============

Automatic Updates

OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
installed. I tell it to go ahead and install. It says it installed
successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
I reboot just for the heck of it.
After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
This has been going on for two weeks now. Any ideas?
Hi Mike
"Mike C#" wrote:

> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> installed. I tell it to go ahead and install. It says it installed
> successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> I reboot just for the heck of it.
> After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> This has been going on for two weeks now. Any ideas?
>
What version is your SQL Server at? Do you have any other instances?
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
explains the different versions and actions that should be taken including
not allowing Microsoft Update to apply SP2 if you have a hotfix that didn't
make SP2.
You could try applying http://support.microsoft.com/Default.aspx?Kbid=934459
John
|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi Mike
> "Mike C#" wrote:
> What version is your SQL Server at? Do you have any other instances?
> http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> explains the different versions and actions that should be taken including
> not allowing Microsoft Update to apply SP2 if you have a hotfix that
> didn't
> make SP2.
> You could try applying
> http://support.microsoft.com/Default.aspx?Kbid=934459
> John
Hi John,
9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
Mike
|||Hi
"Mike C#" wrote:

> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi John,
> 9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
> Mike
>
If it doesn't work, you can tell windows update not to remind you of a patch
again, when you go through the custom installation, selecting the download
and checking the "Don't remind me again" checkbox.
Johm
|||"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:D6CFE0F8-8E64-4CD3-8004-7274A391A9C6@.microsoft.com...
> If it doesn't work, you can tell windows update not to remind you of a
> patch
> again, when you go through the custom installation, selecting the download
> and checking the "Don't remind me again" checkbox.
> Johm
I considered that, but decided against for now since I want to see if the
manual install actually works. I performed the manual install, and it
appears to have worked, but I want to give it a few more days to be sure.
Thanks
Mike

Automatic Updates

OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
installed. I tell it to go ahead and install. It says it installed
successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
I reboot just for the heck of it.
After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
This has been going on for two weeks now. Any ideas?Hi Mike
"Mike C#" wrote:
> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> installed. I tell it to go ahead and install. It says it installed
> successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> I reboot just for the heck of it.
> After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> This has been going on for two weeks now. Any ideas?
>
What version is your SQL Server at? Do you have any other instances?
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
explains the different versions and actions that should be taken including
not allowing Microsoft Update to apply SP2 if you have a hotfix that didn't
make SP2.
You could try applying http://support.microsoft.com/Default.aspx?Kbid=934459
John|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi Mike
> "Mike C#" wrote:
>> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
>> installed. I tell it to go ahead and install. It says it installed
>> successfully.
>> ...
> What version is your SQL Server at? Do you have any other instances?
> http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> explains the different versions and actions that should be taken including
> not allowing Microsoft Update to apply SP2 if you have a hotfix that
> didn't
> make SP2.
> You could try applying
> http://support.microsoft.com/Default.aspx?Kbid=934459
> John
Hi John,
9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
Mike|||Hi
"Mike C#" wrote:
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> > Hi Mike
> >
> > "Mike C#" wrote:
> >
> >> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> >> installed. I tell it to go ahead and install. It says it installed
> >> successfully.
> >> ...
> > What version is your SQL Server at? Do you have any other instances?
> >
> > http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> > explains the different versions and actions that should be taken including
> > not allowing Microsoft Update to apply SP2 if you have a hotfix that
> > didn't
> > make SP2.
> >
> > You could try applying
> > http://support.microsoft.com/Default.aspx?Kbid=934459
> >
> > John
> Hi John,
> 9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
> Mike
>
If it doesn't work, you can tell windows update not to remind you of a patch
again, when you go through the custom installation, selecting the download
and checking the "Don't remind me again" checkbox.
Johm|||"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:D6CFE0F8-8E64-4CD3-8004-7274A391A9C6@.microsoft.com...
> If it doesn't work, you can tell windows update not to remind you of a
> patch
> again, when you go through the custom installation, selecting the download
> and checking the "Don't remind me again" checkbox.
> Johm
I considered that, but decided against for now since I want to see if the
manual install actually works. I performed the manual install, and it
appears to have worked, but I want to give it a few more days to be sure.
Thanks
Mike

Automatic Updates

OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
installed. I tell it to go ahead and install. It says it installed
successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
Ten minutes later I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
I reboot just for the heck of it.
After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
needs to be installed. I tell it to go ahead and install. It says it
installed successfully.
This has been going on for two weeks now. Any ideas?Hi Mike
"Mike C#" wrote:

> OK, I get a message from Automatic Updates that SQL 2005 SP 2 needs to be
> installed. I tell it to go ahead and install. It says it installed
> successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP
2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> Ten minutes later I get a message from Automatic Updates that SQL 2005 SP
2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> I reboot just for the heck of it.
> After I reboot I get a message from Automatic Updates that SQL 2005 SP 2
> needs to be installed. I tell it to go ahead and install. It says it
> installed successfully.
> This has been going on for two weeks now. Any ideas?
>
What version is your SQL Server at? Do you have any other instances?
http://blogs.msdn.com/psssql/archiv...-explained.aspx
explains the different versions and actions that should be taken including
not allowing Microsoft Update to apply SP2 if you have a hotfix that didn't
make SP2.
You could try applying http://support.microsoft.com/Default.aspx?Kbid=934459
John|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi Mike
> "Mike C#" wrote:
>
> What version is your SQL Server at? Do you have any other instances?
> http://blogs.msdn.com/psssql/archiv...-explained.aspx
> explains the different versions and actions that should be taken including
> not allowing Microsoft Update to apply SP2 if you have a hotfix that
> didn't
> make SP2.
> You could try applying
> http://support.microsoft.com/Default.aspx?Kbid=934459
> John
Hi John,
9.00.3054. I'll check out the post, and let you know if it helps. Thanks!
Mike|||Hi
"Mike C#" wrote:

> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:7A1CB953-70DF-4746-BCC5-11EF82180579@.microsoft.com...
> Hi John,
> 9.00.3054. I'll check out the post, and let you know if it helps. Thanks
!
> Mike
>
If it doesn't work, you can tell windows update not to remind you of a patch
again, when you go through the custom installation, selecting the download
and checking the "Don't remind me again" checkbox.
Johm|||"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:D6CFE0F8-8E64-4CD3-8004-7274A391A9C6@.microsoft.com...
> If it doesn't work, you can tell windows update not to remind you of a
> patch
> again, when you go through the custom installation, selecting the download
> and checking the "Don't remind me again" checkbox.
> Johm
I considered that, but decided against for now since I want to see if the
manual install actually works. I performed the manual install, and it
appears to have worked, but I want to give it a few more days to be sure.
Thanks
Mikesql

Automatic Update Not Working

SQL Server 2000. Windows Small Business Server 2003. Windows automatic
update keeps trying to install the same "critical security" update to SQL
Server Desktop Engine. Apparently it is not installing, as I find two event
s
in the event view each time. The automatic update is attempted almost every
time I log onto the server. Any ideas? The following is the event
information:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 12/5/2005
Time: 9:54:07 AM
User: GNJPM\administrator
Computer: HQSERVER
Description:
Product: Microsoft SQL Server Desktop Engine -- Internal Error 2727.
DatabaseRepl.185C1D8F_1545_4277_BB64_857D2622DB57
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 36 35 36 35 37 43 35 {65657C5
0008: 39 2d 32 33 41 38 2d 34 9-23A8-4
0010: 39 37 34 2d 42 38 45 30 974-B8E0
0018: 2d 42 41 30 34 45 42 44 -BA04EBD
0020: 30 34 45 34 46 7d 04E4F}
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 1023
Date: 12/5/2005
Time: 9:54:07 AM
User: GNJPM\administrator
Computer: HQSERVER
Description:
Product: Microsoft SQL Server Desktop Engine - Update
'{1F506503-186B-4D88-81B3-7113B9457C9D}' could not be installed. Error
code
1603. Additional information is available in the log file C:\WMSDEHotfix.log
.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 36 35 36 35 37 43 35 {65657C5
0008: 39 2d 32 33 41 38 2d 34 9-23A8-4
0010: 39 37 34 2d 42 38 45 30 974-B8E0
0018: 2d 42 41 30 34 45 42 44 -BA04EBD
0020: 30 34 45 34 46 7d 20 7b 04E4F} {
0028: 31 46 35 30 36 35 30 33 1F506503
0030: 2d 31 38 36 42 2d 34 44 -186B-4D
0038: 38 38 2d 38 31 42 33 2d 88-81B3-
0040: 37 31 31 33 42 39 34 35 7113B945
0048: 37 43 39 44 7d 20 31 36 7C9D} 16
0050: 30 33 03
Dr. Doug Pruiett
Good News Jail & Prison Ministry
www.goodnewsjail.orgIt could be a lot of different things. Make sure your disk
space is okay. Make sure your temp directory is cleared out.
You may also want to check the following logs for more clues
as to what the problem is:
C:\WINDOWS\sqlsp.log
C:\WINDOWS\sqlstp.log
-Sue
On Mon, 5 Dec 2005 07:10:03 -0800, "Chaplain Doug"
<ChaplainDoug@.discussions.microsoft.com> wrote:

>SQL Server 2000. Windows Small Business Server 2003. Windows automatic
>update keeps trying to install the same "critical security" update to SQL
>Server Desktop Engine. Apparently it is not installing, as I find two even
ts
>in the event view each time. The automatic update is attempted almost ever
y
>time I log onto the server. Any ideas? The following is the event
>information:
>Event Type: Error
>Event Source: MsiInstaller
>Event Category: None
>Event ID: 10005
>Date: 12/5/2005
>Time: 9:54:07 AM
>User: GNJPM\administrator
>Computer: HQSERVER
>Description:
>Product: Microsoft SQL Server Desktop Engine -- Internal Error 2727.
>DatabaseRepl.185C1D8F_1545_4277_BB64_857D2622DB57
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>Data:
>0000: 7b 36 35 36 35 37 43 35 {65657C5
>0008: 39 2d 32 33 41 38 2d 34 9-23A8-4
>0010: 39 37 34 2d 42 38 45 30 974-B8E0
>0018: 2d 42 41 30 34 45 42 44 -BA04EBD
>0020: 30 34 45 34 46 7d 04E4F}
>Event Type: Error
>Event Source: MsiInstaller
>Event Category: None
>Event ID: 1023
>Date: 12/5/2005
>Time: 9:54:07 AM
>User: GNJPM\administrator
>Computer: HQSERVER
>Description:
>Product: Microsoft SQL Server Desktop Engine - Update
>'{1F506503-186B-4D88-81B3-7113B9457C9D}' could not be installed. Error
code
>1603. Additional information is available in the log file C:\WMSDEHotfix.lo
g.
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>Data:
>0000: 7b 36 35 36 35 37 43 35 {65657C5
>0008: 39 2d 32 33 41 38 2d 34 9-23A8-4
>0010: 39 37 34 2d 42 38 45 30 974-B8E0
>0018: 2d 42 41 30 34 45 42 44 -BA04EBD
>0020: 30 34 45 34 46 7d 20 7b 04E4F} {
>0028: 31 46 35 30 36 35 30 33 1F506503
>0030: 2d 31 38 36 42 2d 34 44 -186B-4D
>0038: 38 38 2d 38 31 42 33 2d 88-81B3-
>0040: 37 31 31 33 42 39 34 35 7113B945
>0048: 37 43 39 44 7d 20 31 36 7C9D} 16
>0050: 30 33 03

Automatic update fails

I'm getting automatic updates to install for SQL Server 2005. I am
technically fairly savvy, but I didn't even know I HAD SQL installed!
The problem is that the automatic update won't install, and it gives me no
reason why... but after it fails it continues to show up as an update waiting
to be installed. (I have set my auto updates to let me decide when to
install.)
"SQL Server 2005 Express Edition Service Pack 2 (KB921896) failed to install."
That's all I get. How do I determine WHY it won't install, and then fix it?
AuthorCancerForTwo (AuthorCancerForTwo@.discussions.microsoft.com) writes:
> I'm getting automatic updates to install for SQL Server 2005. I am
> technically fairly savvy, but I didn't even know I HAD SQL installed!
> The problem is that the automatic update won't install, and it gives me
> no reason why... but after it fails it continues to show up as an update
> waiting to be installed. (I have set my auto updates to let me decide
> when to install.)
> "SQL Server 2005 Express Edition Service Pack 2 (KB921896) failed to
> install."
> That's all I get. How do I determine WHY it won't install, and then fix
> it?
The only suggestion I can give is to download the service pack, and run
the install manually to see what it barfs about.
Hm, well there might be logs in
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix or
corresponding. But since you did not even know that you had SQL Express
installed, that directory may be elsewhere.
You could also check in Services that you actually have an SQL Server
service.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||Thank you, Erland... I went to the place you identified and there were some
logs there - I looked at the most recent log and, sure enough, there was the
reason that it failed... Windows Authorization failed. I can't imagine
why... I never used pirated or unauthorized software. But it did give me the
name of the product that uses SQL and, therefore, probably installed it
unbeknownst to me, so I will try to re-install that software.
I must say that I have had a lot of trouble with that product, and I'm going
to dump it as soon as possible... this situation is just another good reason
to do so.
Thank you for your help!
"Erland Sommarskog" wrote:

> AuthorCancerForTwo (AuthorCancerForTwo@.discussions.microsoft.com) writes:
> The only suggestion I can give is to download the service pack, and run
> the install manually to see what it barfs about.
> Hm, well there might be logs in
> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix or
> corresponding. But since you did not even know that you had SQL Express
> installed, that directory may be elsewhere.
> You could also check in Services that you actually have an SQL Server
> service.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>

automatic change of permission on database after install web site

I have Web Site with ASPNETDB database and own database. I was precompiled this site and I created aplication with Web Setup Project. This setup aplication includes SQL 2005 EXPRESS. When I installed and ran an my web site in Internet explorer, that displayed error "Failed to update database ... because the database is read-only". I know, that is a bug with permisson and the fix a bug is solution for this problem but i have installation package and i need automatic fix in setup application. Thanx for comments.

Vitty,

The main focus of this forum is on connectivty, client odbc/oledb drivers and etc. The expert on your issue might not visit this forum often. So, I suggest you to visite sql setup forum instead.

AutoClose option and Personal and MSDE Edition

Hi there,
As per SQL Server's install information the AutoClose option is set to TRUE
for both the Personal and MSDE edition installations. My problem is that any
new databases created (ie snapshots) have the AutoClose option set to TRUE.
How can I change the way this option was set on installation since it's
obviously not paying attention to the model database which has the AutoClose
option set to FALSE.
Any info would be appreciated
thanksrazmanaz wrote:
> Hi there,
> As per SQL Server's install information the AutoClose option is set
> to TRUE for both the Personal and MSDE edition installations. My
> problem is that any new databases created (ie snapshots) have the
> AutoClose option set to TRUE. How can I change the way this option
> was set on installation since it's obviously not paying attention to
> the model database which has the AutoClose option set to FALSE.
> Any info would be appreciated
> thanks
AutoClose and AutoShrink default to True for both the Desktop and MSDE
editions of SQL Server. I think you need to use sp_dboption after
database creation to turn the options off. THe model database cannot
override the default settings. For MSDE, you may want to leave it on to
prevent SQL Server from using too much memory when the database is
inactive, unless this is causing a real performance issue. One way to
prevent this is to keep at least one connection open to the database at
all times while the application is running.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi David,
Thanks for responding.
However I should have mentioned that the AutoClose has to be set to FALSE
for both Personal and MSDE editions. There is no problem for resources so I
do not need to close the databases to save memory/CPU etc.
Also the sp_dboption script "sp_dboption <database>, autoclose, FALSE" won't
work because the snapshots are continually updated and the script cannot run
continually each time a new snapshot is created. This needs to be changed at
the ground floor.
So another question. If I were to install the Standard edition or higher the
install sets the default to FALSE. I just need to know where the low level
setting is so I can change it so that the changes will take effect any
database that is automatically created.
"David Gugick" wrote:
> razmanaz wrote:
> > Hi there,
> >
> > As per SQL Server's install information the AutoClose option is set
> > to TRUE for both the Personal and MSDE edition installations. My
> > problem is that any new databases created (ie snapshots) have the
> > AutoClose option set to TRUE. How can I change the way this option
> > was set on installation since it's obviously not paying attention to
> > the model database which has the AutoClose option set to FALSE.
> >
> > Any info would be appreciated
> > thanks
> AutoClose and AutoShrink default to True for both the Desktop and MSDE
> editions of SQL Server. I think you need to use sp_dboption after
> database creation to turn the options off. THe model database cannot
> override the default settings. For MSDE, you may want to leave it on to
> prevent SQL Server from using too much memory when the database is
> inactive, unless this is causing a real performance issue. One way to
> prevent this is to keep at least one connection open to the database at
> all times while the application is running.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||razmanaz wrote:
> Hi David,
> Thanks for responding.
> However I should have mentioned that the AutoClose has to be set to
> FALSE for both Personal and MSDE editions. There is no problem for
> resources so I do not need to close the databases to save memory/CPU
> etc.
> Also the sp_dboption script "sp_dboption <database>, autoclose,
> FALSE" won't work because the snapshots are continually updated and
> the script cannot run continually each time a new snapshot is
> created. This needs to be changed at the ground floor.
> So another question. If I were to install the Standard edition or
> higher the install sets the default to FALSE. I just need to know
> where the low level setting is so I can change it so that the changes
> will take effect any database that is automatically created.
>
You can't change the default on a Windows 2000/XP installation since all
you get is the Desktop Edition for those OSes AFAIK.
I'm not clear why sp_dboption won't work. What happens when you execute
the command to change the autoclose option.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi David,
The script to set the AutoClose = FALSE works with no problems when I run
it. It's just that databases in my environment get created all the time. I'm
not sitting there waiting for them and running the script on each and every
database that gets created. That's why I was asking if there was a way to
change the default so that I wouldn't have to do that.
"David Gugick" wrote:
> razmanaz wrote:
> > Hi David,
> >
> > Thanks for responding.
> > However I should have mentioned that the AutoClose has to be set to
> > FALSE for both Personal and MSDE editions. There is no problem for
> > resources so I do not need to close the databases to save memory/CPU
> > etc.
> > Also the sp_dboption script "sp_dboption <database>, autoclose,
> > FALSE" won't work because the snapshots are continually updated and
> > the script cannot run continually each time a new snapshot is
> > created. This needs to be changed at the ground floor.
> > So another question. If I were to install the Standard edition or
> > higher the install sets the default to FALSE. I just need to know
> > where the low level setting is so I can change it so that the changes
> > will take effect any database that is automatically created.
> >
> You can't change the default on a Windows 2000/XP installation since all
> you get is the Desktop Edition for those OSes AFAIK.
> I'm not clear why sp_dboption won't work. What happens when you execute
> the command to change the autoclose option.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||If model doesn't cut it, I suggest you create an Agent job that walk the databases where autoclose
is on and for each such database turn it off. Then schedule this to run every day. I'm a bit
surprised that databases are created all the time, though. Doesn't sound like the typical
environment to me...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"razmanaz" <razmanaz@.discussions.microsoft.com> wrote in message
news:EF1A3B40-5B1D-40F0-8541-5A807631BC65@.microsoft.com...
> Hi David,
> The script to set the AutoClose = FALSE works with no problems when I run
> it. It's just that databases in my environment get created all the time. I'm
> not sitting there waiting for them and running the script on each and every
> database that gets created. That's why I was asking if there was a way to
> change the default so that I wouldn't have to do that.
> "David Gugick" wrote:
>> razmanaz wrote:
>> > Hi David,
>> >
>> > Thanks for responding.
>> > However I should have mentioned that the AutoClose has to be set to
>> > FALSE for both Personal and MSDE editions. There is no problem for
>> > resources so I do not need to close the databases to save memory/CPU
>> > etc.
>> > Also the sp_dboption script "sp_dboption <database>, autoclose,
>> > FALSE" won't work because the snapshots are continually updated and
>> > the script cannot run continually each time a new snapshot is
>> > created. This needs to be changed at the ground floor.
>> > So another question. If I were to install the Standard edition or
>> > higher the install sets the default to FALSE. I just need to know
>> > where the low level setting is so I can change it so that the changes
>> > will take effect any database that is automatically created.
>> >
>> You can't change the default on a Windows 2000/XP installation since all
>> you get is the Desktop Edition for those OSes AFAIK.
>> I'm not clear why sp_dboption won't work. What happens when you execute
>> the command to change the autoclose option.
>>
>> --
>> David Gugick
>> Quest Software
>> www.imceda.com
>> www.quest.com
>>|||razmanaz wrote:
> Hi David,
> The script to set the AutoClose = FALSE works with no problems when I
> run it. It's just that databases in my environment get created all
> the time. I'm not sitting there waiting for them and running the
> script on each and every database that gets created. That's why I was
> asking if there was a way to change the default so that I wouldn't
> have to do that.
Why can't you add the autoclose to the scripts that are used to create
the databases?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com

AutoClose option and Personal and MSDE Edition

Hi there,
As per SQL Server's install information the AutoClose option is set to TRUE
for both the Personal and MSDE edition installations. My problem is that any
new databases created (ie snapshots) have the AutoClose option set to TRUE.
How can I change the way this option was set on installation since it's
obviously not paying attention to the model database which has the AutoClose
option set to FALSE.
Any info would be appreciated
thanks
razmanaz wrote:
> Hi there,
> As per SQL Server's install information the AutoClose option is set
> to TRUE for both the Personal and MSDE edition installations. My
> problem is that any new databases created (ie snapshots) have the
> AutoClose option set to TRUE. How can I change the way this option
> was set on installation since it's obviously not paying attention to
> the model database which has the AutoClose option set to FALSE.
> Any info would be appreciated
> thanks
AutoClose and AutoShrink default to True for both the Desktop and MSDE
editions of SQL Server. I think you need to use sp_dboption after
database creation to turn the options off. THe model database cannot
override the default settings. For MSDE, you may want to leave it on to
prevent SQL Server from using too much memory when the database is
inactive, unless this is causing a real performance issue. One way to
prevent this is to keep at least one connection open to the database at
all times while the application is running.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hi David,
Thanks for responding.
However I should have mentioned that the AutoClose has to be set to FALSE
for both Personal and MSDE editions. There is no problem for resources so I
do not need to close the databases to save memory/CPU etc.
Also the sp_dboption script "sp_dboption <database>, autoclose, FALSE" won't
work because the snapshots are continually updated and the script cannot run
continually each time a new snapshot is created. This needs to be changed at
the ground floor.
So another question. If I were to install the Standard edition or higher the
install sets the default to FALSE. I just need to know where the low level
setting is so I can change it so that the changes will take effect any
database that is automatically created.
"David Gugick" wrote:

> razmanaz wrote:
> AutoClose and AutoShrink default to True for both the Desktop and MSDE
> editions of SQL Server. I think you need to use sp_dboption after
> database creation to turn the options off. THe model database cannot
> override the default settings. For MSDE, you may want to leave it on to
> prevent SQL Server from using too much memory when the database is
> inactive, unless this is causing a real performance issue. One way to
> prevent this is to keep at least one connection open to the database at
> all times while the application is running.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||razmanaz wrote:
> Hi David,
> Thanks for responding.
> However I should have mentioned that the AutoClose has to be set to
> FALSE for both Personal and MSDE editions. There is no problem for
> resources so I do not need to close the databases to save memory/CPU
> etc.
> Also the sp_dboption script "sp_dboption <database>, autoclose,
> FALSE" won't work because the snapshots are continually updated and
> the script cannot run continually each time a new snapshot is
> created. This needs to be changed at the ground floor.
> So another question. If I were to install the Standard edition or
> higher the install sets the default to FALSE. I just need to know
> where the low level setting is so I can change it so that the changes
> will take effect any database that is automatically created.
>
You can't change the default on a Windows 2000/XP installation since all
you get is the Desktop Edition for those OSes AFAIK.
I'm not clear why sp_dboption won't work. What happens when you execute
the command to change the autoclose option.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hi David,
The script to set the AutoClose = FALSE works with no problems when I run
it. It's just that databases in my environment get created all the time. I'm
not sitting there waiting for them and running the script on each and every
database that gets created. That's why I was asking if there was a way to
change the default so that I wouldn't have to do that.
"David Gugick" wrote:

> razmanaz wrote:
> You can't change the default on a Windows 2000/XP installation since all
> you get is the Desktop Edition for those OSes AFAIK.
> I'm not clear why sp_dboption won't work. What happens when you execute
> the command to change the autoclose option.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||If model doesn't cut it, I suggest you create an Agent job that walk the databases where autoclose
is on and for each such database turn it off. Then schedule this to run every day. I'm a bit
surprised that databases are created all the time, though. Doesn't sound like the typical
environment to me...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"razmanaz" <razmanaz@.discussions.microsoft.com> wrote in message
news:EF1A3B40-5B1D-40F0-8541-5A807631BC65@.microsoft.com...[vbcol=seagreen]
> Hi David,
> The script to set the AutoClose = FALSE works with no problems when I run
> it. It's just that databases in my environment get created all the time. I'm
> not sitting there waiting for them and running the script on each and every
> database that gets created. That's why I was asking if there was a way to
> change the default so that I wouldn't have to do that.
> "David Gugick" wrote:
|||razmanaz wrote:
> Hi David,
> The script to set the AutoClose = FALSE works with no problems when I
> run it. It's just that databases in my environment get created all
> the time. I'm not sitting there waiting for them and running the
> script on each and every database that gets created. That's why I was
> asking if there was a way to change the default so that I wouldn't
> have to do that.
Why can't you add the autoclose to the scripts that are used to create
the databases?
David Gugick
Quest Software
www.imceda.com
www.quest.com

AutoClose option and Personal and MSDE Edition

Hi there,
As per SQL Server's install information the AutoClose option is set to TRUE
for both the Personal and MSDE edition installations. My problem is that any
new databases created (ie snapshots) have the AutoClose option set to TRUE.
How can I change the way this option was set on installation since it's
obviously not paying attention to the model database which has the AutoClose
option set to FALSE.
Any info would be appreciated
thanksrazmanaz wrote:
> Hi there,
> As per SQL Server's install information the AutoClose option is set
> to TRUE for both the Personal and MSDE edition installations. My
> problem is that any new databases created (ie snapshots) have the
> AutoClose option set to TRUE. How can I change the way this option
> was set on installation since it's obviously not paying attention to
> the model database which has the AutoClose option set to FALSE.
> Any info would be appreciated
> thanks
AutoClose and AutoShrink default to True for both the Desktop and MSDE
editions of SQL Server. I think you need to use sp_dboption after
database creation to turn the options off. THe model database cannot
override the default settings. For MSDE, you may want to leave it on to
prevent SQL Server from using too much memory when the database is
inactive, unless this is causing a real performance issue. One way to
prevent this is to keep at least one connection open to the database at
all times while the application is running.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi David,
Thanks for responding.
However I should have mentioned that the AutoClose has to be set to FALSE
for both Personal and MSDE editions. There is no problem for resources so I
do not need to close the databases to save memory/CPU etc.
Also the sp_dboption script "sp_dboption <database>, autoclose, FALSE" won't
work because the snapshots are continually updated and the script cannot run
continually each time a new snapshot is created. This needs to be changed at
the ground floor.
So another question. If I were to install the Standard edition or higher the
install sets the default to FALSE. I just need to know where the low level
setting is so I can change it so that the changes will take effect any
database that is automatically created.
"David Gugick" wrote:

> razmanaz wrote:
> AutoClose and AutoShrink default to True for both the Desktop and MSDE
> editions of SQL Server. I think you need to use sp_dboption after
> database creation to turn the options off. THe model database cannot
> override the default settings. For MSDE, you may want to leave it on to
> prevent SQL Server from using too much memory when the database is
> inactive, unless this is causing a real performance issue. One way to
> prevent this is to keep at least one connection open to the database at
> all times while the application is running.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||razmanaz wrote:
> Hi David,
> Thanks for responding.
> However I should have mentioned that the AutoClose has to be set to
> FALSE for both Personal and MSDE editions. There is no problem for
> resources so I do not need to close the databases to save memory/CPU
> etc.
> Also the sp_dboption script "sp_dboption <database>, autoclose,
> FALSE" won't work because the snapshots are continually updated and
> the script cannot run continually each time a new snapshot is
> created. This needs to be changed at the ground floor.
> So another question. If I were to install the Standard edition or
> higher the install sets the default to FALSE. I just need to know
> where the low level setting is so I can change it so that the changes
> will take effect any database that is automatically created.
>
You can't change the default on a Windows 2000/XP installation since all
you get is the Desktop Edition for those OSes AFAIK.
I'm not clear why sp_dboption won't work. What happens when you execute
the command to change the autoclose option.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi David,
The script to set the AutoClose = FALSE works with no problems when I run
it. It's just that databases in my environment get created all the time. I'm
not sitting there waiting for them and running the script on each and every
database that gets created. That's why I was asking if there was a way to
change the default so that I wouldn't have to do that.
"David Gugick" wrote:

> razmanaz wrote:
> You can't change the default on a Windows 2000/XP installation since all
> you get is the Desktop Edition for those OSes AFAIK.
> I'm not clear why sp_dboption won't work. What happens when you execute
> the command to change the autoclose option.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||If model doesn't cut it, I suggest you create an Agent job that walk the dat
abases where autoclose
is on and for each such database turn it off. Then schedule this to run ever
y day. I'm a bit
surprised that databases are created all the time, though. Doesn't sound lik
e the typical
environment to me...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"razmanaz" <razmanaz@.discussions.microsoft.com> wrote in message
news:EF1A3B40-5B1D-40F0-8541-5A807631BC65@.microsoft.com...[vbcol=seagreen]
> Hi David,
> The script to set the AutoClose = FALSE works with no problems when I run
> it. It's just that databases in my environment get created all the time. I
'm
> not sitting there waiting for them and running the script on each and ever
y
> database that gets created. That's why I was asking if there was a way to
> change the default so that I wouldn't have to do that.
> "David Gugick" wrote:
>|||razmanaz wrote:
> Hi David,
> The script to set the AutoClose = FALSE works with no problems when I
> run it. It's just that databases in my environment get created all
> the time. I'm not sitting there waiting for them and running the
> script on each and every database that gets created. That's why I was
> asking if there was a way to change the default so that I wouldn't
> have to do that.
Why can't you add the autoclose to the scripts that are used to create
the databases?
David Gugick
Quest Software
www.imceda.com
www.quest.com