2005/2005Express SQLOLEDB Provider problem

When creating a connection string in ADO (using Delphi7), I insert the provider like this:

Provider=SQLOLEDB;Data Source=.;Initial Catalog=master;Integrated Security=SSPI;User ID=sa;Password=masterkey

Now, when I try to run this on a SQL Server 2005 or SQL2005 Express database, it won't create the connection
unless I use the SQLNCLI provider.

Is there a way to force them to use the OLEDB provider?
I have MDAC2.8-SP1 installed.Try explicitly adding the server name

Provider=SQLOLEDB;Data Source=<Server Name>;Initial Catalog=master;Integrated Security=SSPI;User ID=sa;Password=masterkey

2005 Installation location

The initial installation of 2005 was to the C drive of the server. I want to
uninstall and reinstalling on the D drive. What is the best way of doing this
and still retain all the information already setup in the database? Example,
user security and scheduled jobs?
Thanks,
Emma
Hi Emma
You can backup the databases and restore them onto the new instance see:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms190749.aspx
http://msdn2.microsoft.com/en-us/library/ms190255.aspx
If you are not changing the location of the user database files, restoring
master should recover them. If you then want to move them elsewhere they can
be detached/attached in the new location.
Make sure that you have the same build for the new version as the old one.
You may also want to check for orphaned users in each database
http://support.microsoft.com/kb/274188
John
"Emma" wrote:

> The initial installation of 2005 was to the C drive of the server. I want to
> uninstall and reinstalling on the D drive. What is the best way of doing this
> and still retain all the information already setup in the database? Example,
> user security and scheduled jobs?
> Thanks,
> Emma
>

2005 Installation location

The initial installation of 2005 was to the C drive of the server. I want to
uninstall and reinstalling on the D drive. What is the best way of doing thi
s
and still retain all the information already setup in the database? Example,
user security and scheduled jobs?
Thanks,
EmmaHi Emma
You can backup the databases and restore them onto the new instance see:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms190749.aspx
http://msdn2.microsoft.com/en-us/library/ms190255.aspx
If you are not changing the location of the user database files, restoring
master should recover them. If you then want to move them elsewhere they can
be detached/attached in the new location.
Make sure that you have the same build for the new version as the old one.
You may also want to check for orphaned users in each database
http://support.microsoft.com/kb/274188
John
"Emma" wrote:

> The initial installation of 2005 was to the C drive of the server. I want
to
> uninstall and reinstalling on the D drive. What is the best way of doing t
his
> and still retain all the information already setup in the database? Exampl
e,
> user security and scheduled jobs?
> Thanks,
> Emma
>

2005 Installation location

The initial installation of 2005 was to the C drive of the server. I want to
uninstall and reinstalling on the D drive. What is the best way of doing this
and still retain all the information already setup in the database? Example,
user security and scheduled jobs?
Thanks,
EmmaHi Emma
You can backup the databases and restore them onto the new instance see:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms190749.aspx
http://msdn2.microsoft.com/en-us/library/ms190255.aspx
If you are not changing the location of the user database files, restoring
master should recover them. If you then want to move them elsewhere they can
be detached/attached in the new location.
Make sure that you have the same build for the new version as the old one.
You may also want to check for orphaned users in each database
http://support.microsoft.com/kb/274188
John
"Emma" wrote:
> The initial installation of 2005 was to the C drive of the server. I want to
> uninstall and reinstalling on the D drive. What is the best way of doing this
> and still retain all the information already setup in the database? Example,
> user security and scheduled jobs?
> Thanks,
> Emma
>

2005 - Need to Shrink Log File

Is there a way to shrink the log file below it's Initial Size?
Somehow the initial size for a log file was accidentally set to 25 Gig. This
extra large log file is keeping the backups from working (no disk space).
I've tried Shrinking the log file, but I'm not allowed to shrink it below
it's Intial Size.
I've tried changing it's Initial Size through it's properties, but that
doesn't seem to work either. No message, no indication that it failed.
Is there some way to perhaps replicate the database to another database with
a smaller initial log file setting and then copy it back or something?
Is there some way that I can get the Initial Size back down to a more
manageable size?
Thanks for any help you can offer.
Terry
Thank you, Tibor, for your quick reply.
DBCC SHRINKFILE didn't work. I received the message: "Cannot shrink log file
2 (PAIR_log) because all logical log files are in use."
When I use the SMS to select the Shrink Files option, I can see that the log
file is 99% empty.
I will need to read over your suggested website more carefully to see if
that will help.
Terry
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%233MNF0qWHHA.1180@.TK2MSFTNGP05.phx.gbl...
> Did you try DBCC SHRINKFILE? That command should be able to get it below
> initial size. Also, see
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp for general tips
> when shrink don't seem to work.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
|||Thanks again, Tibor.
Following your suggestions on your website:
I only had to do the Backup Log once and that freed the last page that had
the status of 2. Now everything is back to being a much more manageable
size!
Thanks again!
Terry

> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%233MNF0qWHHA.1180@.TK2MSFTNGP05.phx.gbl...
>

2005 - Need to Shrink Log File

Is there a way to shrink the log file below it's Initial Size?
Somehow the initial size for a log file was accidentally set to 25 Gig. This
extra large log file is keeping the backups from working (no disk space).
I've tried Shrinking the log file, but I'm not allowed to shrink it below
it's Intial Size.
I've tried changing it's Initial Size through it's properties, but that
doesn't seem to work either. No message, no indication that it failed.
Is there some way to perhaps replicate the database to another database with
a smaller initial log file setting and then copy it back or something?
Is there some way that I can get the Initial Size back down to a more
manageable size?
Thanks for any help you can offer.
TerryDid you try DBCC SHRINKFILE? That command should be able to get it below initial size. Also, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for general tips when shrink don't seem to
work.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Terry Carnes" <wbcarnes3@.yahoo.com> wrote in message news:uKxilsqWHHA.4624@.TK2MSFTNGP03.phx.gbl...
> Is there a way to shrink the log file below it's Initial Size?
> Somehow the initial size for a log file was accidentally set to 25 Gig. This extra large log file
> is keeping the backups from working (no disk space).
> I've tried Shrinking the log file, but I'm not allowed to shrink it below it's Intial Size.
> I've tried changing it's Initial Size through it's properties, but that doesn't seem to work
> either. No message, no indication that it failed.
> Is there some way to perhaps replicate the database to another database with a smaller initial log
> file setting and then copy it back or something?
> Is there some way that I can get the Initial Size back down to a more manageable size?
> Thanks for any help you can offer.
> Terry
>|||Thank you, Tibor, for your quick reply.
DBCC SHRINKFILE didn't work. I received the message: "Cannot shrink log file
2 (PAIR_log) because all logical log files are in use."
When I use the SMS to select the Shrink Files option, I can see that the log
file is 99% empty.
I will need to read over your suggested website more carefully to see if
that will help.
Terry
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%233MNF0qWHHA.1180@.TK2MSFTNGP05.phx.gbl...
> Did you try DBCC SHRINKFILE? That command should be able to get it below
> initial size. Also, see
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp for general tips
> when shrink don't seem to work.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi|||Thanks again, Tibor.
Following your suggestions on your website:
I only had to do the Backup Log once and that freed the last page that had
the status of 2. Now everything is back to being a much more manageable
size!
Thanks again!
Terry
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%233MNF0qWHHA.1180@.TK2MSFTNGP05.phx.gbl...
>> Did you try DBCC SHRINKFILE? That command should be able to get it below
>> initial size. Also, see
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp for general tips
>> when shrink don't seem to work.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>

2005 - Need to Shrink Log File

Is there a way to shrink the log file below it's Initial Size?
Somehow the initial size for a log file was accidentally set to 25 Gig. This
extra large log file is keeping the backups from working (no disk space).
I've tried Shrinking the log file, but I'm not allowed to shrink it below
it's Intial Size.
I've tried changing it's Initial Size through it's properties, but that
doesn't seem to work either. No message, no indication that it failed.
Is there some way to perhaps replicate the database to another database with
a smaller initial log file setting and then copy it back or something?
Is there some way that I can get the Initial Size back down to a more
manageable size?
Thanks for any help you can offer.
TerryDid you try DBCC SHRINKFILE? That command should be able to get it below ini
tial size. Also, see
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for general tips when
shrink don't seem to
work.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Terry Carnes" <wbcarnes3@.yahoo.com> wrote in message news:uKxilsqWHHA.4624@.TK2MSFTNGP03.phx
.gbl...
> Is there a way to shrink the log file below it's Initial Size?
> Somehow the initial size for a log file was accidentally set to 25 Gig. Th
is extra large log file
> is keeping the backups from working (no disk space).
> I've tried Shrinking the log file, but I'm not allowed to shrink it below
it's Intial Size.
> I've tried changing it's Initial Size through it's properties, but that do
esn't seem to work
> either. No message, no indication that it failed.
> Is there some way to perhaps replicate the database to another database wi
th a smaller initial log
> file setting and then copy it back or something?
> Is there some way that I can get the Initial Size back down to a more mana
geable size?
> Thanks for any help you can offer.
> Terry
>|||Thank you, Tibor, for your quick reply.
DBCC SHRINKFILE didn't work. I received the message: "Cannot shrink log file
2 (PAIR_log) because all logical log files are in use."
When I use the SMS to select the Shrink Files option, I can see that the log
file is 99% empty.
I will need to read over your suggested website more carefully to see if
that will help.
Terry
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%233MNF0qWHHA.1180@.TK2MSFTNGP05.phx.gbl...
> Did you try DBCC SHRINKFILE? That command should be able to get it below
> initial size. Also, see
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp for general tips
> when shrink don't seem to work.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi|||Thanks again, Tibor.
Following your suggestions on your website:
I only had to do the Backup Log once and that freed the last page that had
the status of 2. Now everything is back to being a much more manageable
size!
Thanks again!
Terry

> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%233MNF0qWHHA.1180@.TK2MSFTNGP05.phx.gbl...
>