author of package affects login?

This is a very frustrating problem.

Let me break it down for the reader.

I have an agent service account that works fine - the account that jobs run under.

I know it works fine because this is the same account all my SQL Backup jobs run under - without a hitch.

I also have a valid sql server account that I use for connection string logins when building packages -

that account works fine. I know it works fine because I can login to the SQL Server Manager with this account.

So, I build a package with the sql server account and password for the OLE DB connection manager in a package. All the package does is a simple query on a table and outputs to a flat file.

I create a job, with 'sa' as the owner. in step 1 I select SSIS package, run as SQL Agent Service Account, package source is file system and I point to the package. The package itself uses the sql server login account to execute.

If I run the package it works fine. I close the solution, someone else comes along and opens the solution - THEY CHANGE ABSOLUTELY NOTHING ABOUT THE LOGIN OR SQL AGENT SERVICE ACCOUNT, but apparently just the fact that they opened the solution and looked at the package, breaks the login. If they try to run the package, they get a login failure, whereas I did not. After they close it, it breaks for me as well. If they open the solution, open the connection manager, re-enter the sql login's password, the package works fine for them, until I come along and open the solution, then it is broken again.

This makes no sense to me. Why would an 'author' opening a solution impact the connection manager when ABOLUTELY NOTHING ABOUT THE CONNECTION MANAGER WAS CHANGED?!

Seems like a bug to me. Anyone seen something like this?

Thanks in advance.

randy

Read up on the package ProtectionLevel property in this forum and in Books-Online.

I'd bet the package is set to EncryptSensitiveWithUserKey, which would prevent others from being able to run the package. You can try EncryptSensitiveWithPassword, but then all developers would need to know the package's password and would be required to enter it to open the package and be able to use it. Either way, Microsoft did not want to be responsible for package security and made sure that the packages are secure.

You could also try DontSaveSensitive, but then you'd have to use a package configuration file to pass in the passwords to the connection managers. It's a touch cumbersome, but in the end it's worth the extra security.|||

Thanks very much. I'll take a look.

Regards

|||

Randyvol,

What you described in your first post is just the normal behavior of SSIS. SSIS does not save sensitive information like connection manager's passwords unless you use an encrypted protection level in your package. If the protection level of the package is set to DonSaveSensitive; then you have to provide the connection credentials every time you open the package. That is what seems to be happening.

As a good practice you can use package configuration to set the connection string of connection managers at run time; that way the package will always get the connection credential when is executed. That will not change the behavior of the package when editing it.

Authentication query

I have a service broker application which is used to exchange messages between two endpoints.

I am currently using certificates for dialog and transport security.

The transport security certificate has been created in master database.

My understanding is that since service broker endpoint is a instance level object so I have to create the certificate in the master database.

But our production dba has suggested that we do not disturb the master database and create this certificate in some user database.

I don't see how that can be possible. Still I tried that, but endpoint creation script failed as it could not find the certificate.

Here I have two questions-

1. Is it possible to set up transport level security by creation of certificate in some user database and referring the sql server endpoint to this certificate.

2. I read somewhere in this forum that certificate authentication is preferable to Windows authentication for creation of endpoints. Is that correct? Is there any article which substantiates this?

Any help will be appreciated.

Warm regards.

Sudhir.

thanks Remus,

That was really helpful and quiet prompt.

Very glad that I posted my query here.

Thanks a bunch.

Have a nice day

Sudhir

|||

1) No. Endpoint certificates must be deployed in master.

2) Certificates authentication does not depend on the availability of the Active Directory and can cross domains and forests.

HTH,
~ Remus

Authentication problems

I am using form authentication to login into report service. When I execute
a report, the following error is displayed:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'DAISYS'.
(rsErrorOpeningConnection) Get Online Help
Unable to load DLL (oci.dll).
But if I use window authentication, it works fine.
Please help !!!Can someone help me ?
"May Liu" wrote:
> I am using form authentication to login into report service. When I execute
> a report, the following error is displayed:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Cannot create a connection to data source 'DAISYS'.
> (rsErrorOpeningConnection) Get Online Help
> Unable to load DLL (oci.dll).
> But if I use window authentication, it works fine.
> Please help !!!|||This sounds like a file permission issue with the installation of the Oracle
client software. The ASP worker process is unable to load OCI.dll and other
configuration settings which are stored in the Oracle client installation
directory.
For instance, the Oracle 9.2 client is typically installed at:
C:\oracle\ora92. When you use Windows authentication, it seems like the
users executing reports have "Read & Execute" permissions at least on
\oracle\ora92\bin and \oracle\ora92\network\admin directories - and
therefore the ASP.NET work process can access and load the Oracle client
software (dlls and configuration fiiles) from there.
When you use Forms authentication, most likely the ASP.NET worker process
will run under a user account that does *not* have explicit Read & Execute
permissions on the directories of the Oracle client software. Make sure
these rights are explicitly granted to all files (child objects) in those
directories (on Win2003 on the directory security tab you have to click on
the Advanced button and in the new popup window you have to select "Replace
permission entries on all child objects ..." and click OK).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"May Liu" <MayLiu@.discussions.microsoft.com> wrote in message
news:823537DA-85E8-4C71-8F0D-6CFA0EAE4182@.microsoft.com...
> Can someone help me ?
> "May Liu" wrote:
> > I am using form authentication to login into report service. When I
execute
> > a report, the following error is displayed:
> >
> > An error has occurred during report processing. (rsProcessingAborted)
Get
> > Online Help
> > Cannot create a connection to data source 'DAISYS'.
> > (rsErrorOpeningConnection) Get Online Help
> > Unable to load DLL (oci.dll).
> >
> > But if I use window authentication, it works fine.
> > Please help !!!|||It works. Thanks a lot !!!
"Robert Bruckner [MSFT]" wrote:
> This sounds like a file permission issue with the installation of the Oracle
> client software. The ASP worker process is unable to load OCI.dll and other
> configuration settings which are stored in the Oracle client installation
> directory.
> For instance, the Oracle 9.2 client is typically installed at:
> C:\oracle\ora92. When you use Windows authentication, it seems like the
> users executing reports have "Read & Execute" permissions at least on
> \oracle\ora92\bin and \oracle\ora92\network\admin directories - and
> therefore the ASP.NET work process can access and load the Oracle client
> software (dlls and configuration fiiles) from there.
> When you use Forms authentication, most likely the ASP.NET worker process
> will run under a user account that does *not* have explicit Read & Execute
> permissions on the directories of the Oracle client software. Make sure
> these rights are explicitly granted to all files (child objects) in those
> directories (on Win2003 on the directory security tab you have to click on
> the Advanced button and in the new popup window you have to select "Replace
> permission entries on all child objects ..." and click OK).
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "May Liu" <MayLiu@.discussions.microsoft.com> wrote in message
> news:823537DA-85E8-4C71-8F0D-6CFA0EAE4182@.microsoft.com...
> > Can someone help me ?
> >
> > "May Liu" wrote:
> >
> > > I am using form authentication to login into report service. When I
> execute
> > > a report, the following error is displayed:
> > >
> > > An error has occurred during report processing. (rsProcessingAborted)
> Get
> > > Online Help
> > > Cannot create a connection to data source 'DAISYS'.
> > > (rsErrorOpeningConnection) Get Online Help
> > > Unable to load DLL (oci.dll).
> > >
> > > But if I use window authentication, it works fine.
> > > Please help !!!
>
>sql

Authentication mode / configuration issue

I'm having a little issue here with the MSSQLServer service which installs as part of the BlackBerry Enterprise Server. I can connect to it and run queries on it via Query Analyzer, but when I attempt to have a PHP script query against it, I get an error stating that the login failed because the user is not associated with a trusted SQL connection (severity 14). I've seen this before with other servers, and it was always a result of the server not being in mixed authentication mode.

So the question is this: How do I change it? There doesn't appear to be an Enterprise Manager or anything equivalent installed. Digging through the SQL Server folder, the only thing I saw that might have been useful is the SQL Server Network Utility located at Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.EXE. This utility appears to only let me disable/enable protocols however, nothing about authentication.

I checked the Service Manager as well and didn't see anything of use there. Any ideas how I can do this?

It looks like I might have figured this one out. Using a copy of Enterprise Manager that I had installed on my machine, I added the MSSQL server installed on the BlackBerry server and changed its authentication properties that way. It looks like I'll have to tweak with some permissions for the individual databases but I think I've got it now.

Authenticate users, while making Web Service(SOAP) Requests

How can I authorize users to retrieve their own data while making SOAP
Requests?
I don't want to pass usernames as paramaters. I could pass them in
cookies in some encrypted format.
Is there an interface to implement for authentication/authorization
before processing results, in SQLXML 3.0 SP2?
Regards,
Mert SakaryaUnfortunatly no. You could use Integrated Authentication in ISAPI and then
set up the database security to check the user, though I don't think that
would give you row-level security. You'd have to add some logic for that.
Irwin
"Mert Sakarya" <msakarya@.(nospam)e-kolay.com> wrote in message
news:uIA2XPmEFHA.960@.TK2MSFTNGP09.phx.gbl...
> How can I authorize users to retrieve their own data while making SOAP
> Requests?
> I don't want to pass usernames as paramaters. I could pass them in
> cookies in some encrypted format.
> Is there an interface to implement for authentication/authorization
> before processing results, in SQLXML 3.0 SP2?
> Regards,
> Mert Sakarya
>

Authenticate users, while making Web Service(SOAP) Requests

How can I authorize users to retrieve their own data while making SOAP
Requests?
I don't want to pass usernames as paramaters. I could pass them in
cookies in some encrypted format.
Is there an interface to implement for authentication/authorization
before processing results, in SQLXML 3.0 SP2?
Regards,
Mert Sakarya
Unfortunatly no. You could use Integrated Authentication in ISAPI and then
set up the database security to check the user, though I don't think that
would give you row-level security. You'd have to add some logic for that.
Irwin
"Mert Sakarya" <msakarya@.(nospam)e-kolay.com> wrote in message
news:uIA2XPmEFHA.960@.TK2MSFTNGP09.phx.gbl...
> How can I authorize users to retrieve their own data while making SOAP
> Requests?
> I don't want to pass usernames as paramaters. I could pass them in
> cookies in some encrypted format.
> Is there an interface to implement for authentication/authorization
> before processing results, in SQLXML 3.0 SP2?
> Regards,
> Mert Sakarya
>

Authenctication to Report Builder

I m really new to reporting service. I dnt know what I did but once I try to access "http://localhost/reports" it will prompt me for username & password. And whatever I typed in is incorrect...

Help Please~

Thank you,

Elton

By default, the reporting services will use NT authentication. You should be able to use the NT administrator account to login.

|||

Thankumcsenow,

I thought I tried that before but it does not seem work...Acturally, I m currently open Report server directly from IIS and also I applied the integrated auth.

Cheers,

Elton

Auth.

what if we are making the ASP(Application Service provider) model so we have
to go for windows authentication or standard authentication?
Can you be more elaborate on what your question is?
You can use either of the mechanism as authentication models. But what is
your requirement?
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Rogers" <Rogers@.discussions.microsoft.com> wrote in message
news:F11D42D4-EA39-4E22-A390-DB7A933FD91B@.microsoft.com...
> what if we are making the ASP(Application Service provider) model so we
have
> to go for windows authentication or standard authentication?
|||at what point we have to go for windows authentication and at what point we
have to consider to go for standard authentication means through database
user.
"Vinod Kumar" wrote:

> Can you be more elaborate on what your question is?
> You can use either of the mechanism as authentication models. But what is
> your requirement?
> --
> HTH,
> Vinod Kumar
> MCSE, DBA, MCAD, MCSD
> http://www.extremeexperts.com
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinf...2000/books.asp
> "Rogers" <Rogers@.discussions.microsoft.com> wrote in message
> news:F11D42D4-EA39-4E22-A390-DB7A933FD91B@.microsoft.com...
> have
>
>

Audit Level

Hello Group,
when the Audit Level is changed from Everything to Failure, do I have to
stop and restart the SQL Server Windows Service?
RichYes you need to restart.
-Sue
On Fri, 17 Feb 2006 08:03:29 -0800, "Rich"
<Rich@.discussions.microsoft.com> wrote:
>Hello Group,
>when the Audit Level is changed from Everything to Failure, do I have to
>stop and restart the SQL Server Windows Service?
>Rich

Attempts to made backup on the network drive are failed

MS SQL Server 2000 Enterprise Edition Service Pack 3
on MS Windows Advanced Server Service Pack 4
Attempts to made backup on the network drive are failed.
There are two databases with this feature. One has 1400Mb data and 100Mb
log. Another has 4410Mb data and 1000Mb log.
First database has about 80% successful attempts. Second - only 10%. However
there are a lot of databases about 300-500Mb that are backed up successfully
always and one that has 4100Mb data and 1000Mb log, that is backed up
successfully always.
Backups on the local drives are always successful.
Copying entire catalog \data (about 20Gb mdf and ldf files) on the same
network drive is always successful.
Symptoms:
After issuing this statement:
backup database LargeDB to
disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
we have result:
1 percent backed up.
2 percent backed up.
3 percent backed up.
................
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 563608 pages for database 'LargeDB', file 'LargeDBData' on file 1.
100 percent backed up.
Processed 1 pages for database 'LargeDB', file 'LargeDBlog' on file 1.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL Server log contains two records:
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
64(error not found).
BACKUP failed to complete the command backup database LargeDB to
disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
Application event log contains two records:
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
64(error not found).
3041 :
BACKUP failed to complete the command backup database LargeDB to
disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
System event log has no records
Events logs from file server has no records.
Attempt to restore from the "unsuccessful" backup file always is successful.
What should I do?|
| MS SQL Server 2000 Enterprise Edition Service Pack 3
| on MS Windows Advanced Server Service Pack 4
|
| Attempts to made backup on the network drive are failed.
| There are two databases with this feature. One has 1400Mb data and 100Mb
| log. Another has 4410Mb data and 1000Mb log.
| First database has about 80% successful attempts. Second - only 10%.
However
| there are a lot of databases about 300-500Mb that are backed up
successfully
| always and one that has 4100Mb data and 1000Mb log, that is backed up
| successfully always.
| Backups on the local drives are always successful.
| Copying entire catalog \data (about 20Gb mdf and ldf files) on the same
| network drive is always successful.
|
| Symptoms:
| After issuing this statement:
| backup database LargeDB to
| disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
| we have result:
| 1 percent backed up.
| 2 percent backed up.
| 3 percent backed up.
| ................
| 97 percent backed up.
| 98 percent backed up.
| 99 percent backed up.
| Processed 563608 pages for database 'LargeDB', file 'LargeDBData' on file
1.
| 100 percent backed up.
| Processed 1 pages for database 'LargeDB', file 'LargeDBlog' on file 1.
| Server: Msg 3013, Level 16, State 1, Line 1
| BACKUP DATABASE is terminating abnormally.
|
| SQL Server log contains two records:
| BackupDiskFile::RequestDurableMedia: failure on backup device
| '\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
| 64(error not found).
| BACKUP failed to complete the command backup database LargeDB to
| disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
|
| Application event log contains two records:
| 18210 :
| BackupDiskFile::RequestDurableMedia: failure on backup device
| '\\server001\backup2\mssql\LargeDB_20031209.bak'. Operating system error
| 64(error not found).
| 3041 :
| BACKUP failed to complete the command backup database LargeDB to
| disk='\\server001\backup2\mssql\LargeDB_20031209.bak' with stats=1
| System event log has no records
|
| Events logs from file server has no records.
|
| Attempt to restore from the "unsuccessful" backup file always is
successful.
|
| What should I do?
--
Go to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
eters\SessTimeout
Increase this value to 600 (10 minutes) and see how you go.
Hope this helps,
--
Eric Cárdenas
SQL Server support

Attaching a database, but missing a file

The situation is this:
1. I use an off-site service to backup my SQL database.
2. I did a restore of a database to a different directory.
3. I attempted to attach to this database only to discover that one of the
log files was not getting backed up. (there were three different log files)
4. I was not permitted to attach.
YIKES!
Had this been a REAL EMERGENCY, would I have lost everything just because of
one log file missing? Or is there some way to force the attachment, ignoring
the missing file?
--Zorpie
In some cases, you can attach without the log file and SQL Server will create a log file for you. It
requires some things in place:
Db has only one log file
Cleanly detached
Probably some other stuff (see documentation for sp_attach_single_file_db).
IF the database doesn't attach, your option is to call MS Support and see if they have any emergency
rescue options. It will probably lead to a possibly both logically and physically inconsistent
database. So this is not something you want to do. Probably to dig up your most recent backup
instead.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of the
> log files was not getting backed up. (there were three different log files)
> 4. I was not permitted to attach.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because of
> one log file missing? Or is there some way to force the attachment, ignoring
> the missing file?
> --Zorpie
|||I would go with Tibor's suggestions but you may be interested in this as
well:
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
Andrew J. Kelly SQL MVP
"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of
> the
> log files was not getting backed up. (there were three different log
> files)
> 4. I was not permitted to attach.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
> of
> one log file missing? Or is there some way to force the attachment,
> ignoring
> the missing file?
> --Zorpie
|||"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of
the
> log files was not getting backed up. (there were three different log
files)
> 4. I was not permitted to attach.
If a log file is missing, it sounds like they're not using native SQL Server
backup commands. Do you know if there's a particular reason for this?
Generally using the native SQL Server backup commands are the best way to do
it. They will insure all logs are backed up and insure DB integrity.

> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
of
> one log file missing? Or is there some way to force the attachment,
ignoring
> the missing file?
> --Zorpie

Attaching a database, but missing a file

The situation is this:
1. I use an off-site service to backup my SQL database.
2. I did a restore of a database to a different directory.
3. I attempted to attach to this database only to discover that one of the
log files was not getting backed up. (there were three different log files)
4. I was not permitted to attach.
YIKES!
Had this been a REAL EMERGENCY, would I have lost everything just because of
one log file missing? Or is there some way to force the attachment, ignorin
g
the missing file?
--ZorpieIn some cases, you can attach without the log file and SQL Server will creat
e a log file for you. It
requires some things in place:
Db has only one log file
Cleanly detached
Probably some other stuff (see documentation for sp_attach_single_file_db).
IF the database doesn't attach, your option is to call MS Support and see if
they have any emergency
rescue options. It will probably lead to a possibly both logically and physi
cally inconsistent
database. So this is not something you want to do. Probably to dig up your m
ost recent backup
instead.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of th
e
> log files was not getting backed up. (there were three different log file
s)
> 4. I was not permitted to attach.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
of
> one log file missing? Or is there some way to force the attachment, ignor
ing
> the missing file?
> --Zorpie|||I would go with Tibor's suggestions but you may be interested in this as
well:
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
Andrew J. Kelly SQL MVP
"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of
> the
> log files was not getting backed up. (there were three different log
> files)
> 4. I was not permitted to attach.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
> of
> one log file missing? Or is there some way to force the attachment,
> ignoring
> the missing file?
> --Zorpie|||"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of
the
> log files was not getting backed up. (there were three different log
files)
> 4. I was not permitted to attach.
If a log file is missing, it sounds like they're not using native SQL Server
backup commands. Do you know if there's a particular reason for this?
Generally using the native SQL Server backup commands are the best way to do
it. They will insure all logs are backed up and insure DB integrity.

> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
of
> one log file missing? Or is there some way to force the attachment,
ignoring
> the missing file?
> --Zorpie

Attaching a database, but missing a file

The situation is this:
1. I use an off-site service to backup my SQL database.
2. I did a restore of a database to a different directory.
3. I attempted to attach to this database only to discover that one of the
log files was not getting backed up. (there were three different log files)
4. I was not permitted to attach.
YIKES!
Had this been a REAL EMERGENCY, would I have lost everything just because of
one log file missing? Or is there some way to force the attachment, ignoring
the missing file?
--ZorpieIn some cases, you can attach without the log file and SQL Server will create a log file for you. It
requires some things in place:
Db has only one log file
Cleanly detached
Probably some other stuff (see documentation for sp_attach_single_file_db).
IF the database doesn't attach, your option is to call MS Support and see if they have any emergency
rescue options. It will probably lead to a possibly both logically and physically inconsistent
database. So this is not something you want to do. Probably to dig up your most recent backup
instead.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of the
> log files was not getting backed up. (there were three different log files)
> 4. I was not permitted to attach.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because of
> one log file missing? Or is there some way to force the attachment, ignoring
> the missing file?
> --Zorpie|||I would go with Tibor's suggestions but you may be interested in this as
well:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
--
Andrew J. Kelly SQL MVP
"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of
> the
> log files was not getting backed up. (there were three different log
> files)
> 4. I was not permitted to attach.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
> of
> one log file missing? Or is there some way to force the attachment,
> ignoring
> the missing file?
> --Zorpie|||"Zorpiedoman" <nowheremane@.beatles.com> wrote in message
news:EE169C40-B180-4470-9572-B0272838A045@.microsoft.com...
> The situation is this:
> 1. I use an off-site service to backup my SQL database.
> 2. I did a restore of a database to a different directory.
> 3. I attempted to attach to this database only to discover that one of
the
> log files was not getting backed up. (there were three different log
files)
> 4. I was not permitted to attach.
If a log file is missing, it sounds like they're not using native SQL Server
backup commands. Do you know if there's a particular reason for this?
Generally using the native SQL Server backup commands are the best way to do
it. They will insure all logs are backed up and insure DB integrity.
> YIKES!
> Had this been a REAL EMERGENCY, would I have lost everything just because
of
> one log file missing? Or is there some way to force the attachment,
ignoring
> the missing file?
> --Zorpie