Auto Failover Issues

I have been looking over the forum, and also other sites for information about my problem but cant seem to find what im looking for so I have decided to make a quick post.

Presently, I have 3 computers setup for mirroring. One is the principal, another the mirror and the third is the witness.

Im using SQL 2005 Enterprise Edition on all three, and creation of the mirror using SQL Studio works without problems. Manual failover (using the button in SQL Studio) also works fine.

When I start the "Mirror Monitor" application, and connect to the two DB servers the status is all green, they are connected to each other and the witness server can be contacted.

Now here is my issue; when its time for an automatic failover situation (pulling the plug from the current principal for example) it detects the fault and changes the status of the mirror to "principal" BUT keeps the other status to "Disconnected" (Principal, Disconnected) so no active connections to the failed over database will work.

When running the mirror monitor during the failed fail-over attempt the still online database reports that the connection to the witness is still present but the mirror is offline.

There are a few error notices in the logs, but from what I can tell they are normal for whats happening. But the codes would be 1479 (cant talk to the database; this would be the one we took offline) and 1474 (network name is no longer available; once again as it was taken offline). Note that these errors are also in the witness server logs, as I believe one should expect.

Any help or assistance with this problem would be appreciated.

Thanks,

Sean

Do you see any network related issues or warnings between the principal and mirror servers?|||Hate to state the obvious, but you don't mention that you re-connect server 1 in your scenario. What you are describing is exactly what I would expect to happen.sql

Authentication failure - can't find domain accounts

We're getting an error where we can't add a login with the full dns name of a user - domain.xyz\user, for example. Get an error 15401, "Windows NT user or group domain.xyz\user' not found". The domain has a different Netbios name and DNS domain names, so we can add the user when we use the form "netbiosname\user". So far so good.

Unfortunately, we have another application - Office Share Point Server whose shared services provider won't run, giving errors in the event log every 60 seconds that "Windows NT user or group 'domain.xyz\user' not found".

It looks as if SQL insists upon listing users in the form netbiosdomainname\user, and applications that look for domain.xyz\user simply fail to authenticate.

Suggestions?

jnfranc at yahoo period com

SQL Server only understands NetBIOS names for Windows principals (i.e. when creating a login), but authentication via SSPI should work normally.

Please let us know if you still require help on this issue, if so, we will need more details regarding the failure, if possible the SQL Server error number/message.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

Audit tables ?

I cant find feature to audit executin of statements on table level (I read somewhere that is one of new feature of SQL 2008). For an exemple to now who is make an UPDATE, INSERT or DELETE statements.

In Katmai we have the cdc(Change data Capture).Change data capture(CDC) is designed to capture insert, update, and delete activity applied to SQL Server tables, and to make the details of the changes available in an easily consumed relational format. The change tables used by change data capture contain columns that mirror the column structure of a tracked source table, along with the metadata needed to understand the changes that have occurred.

For more details go to books online and write "change data capture"....

.

|||We do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 June CTP. Expect to see it in a future CTP.|||

Sara Tahir [MSFT] wrote:

We do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 June CTP. Expect to see it in a future CTP.

I just tested cdc and it works fine in the june ctp.

|||

Yes, CDC works just fine. There is couple of steps to make ti work...but it's cool feature.

Example:

--to activate cdc

EXEC sys.sp_cdc_enable_db_change_data_capture

--checking

SELECT is_cdc_enabled FROM sys.databases WHERE name = 'databaseName'

--enabling chanage data capture on specific table

USE test;

GO

EXECUTE sys.sp_cdc_enable_table_change_data_capture
@.source_schema = N'dbo'
, @.source_name = N'Imena'
, @.role_name = N'cdc_Admin';

GO

-- INSERT, DELETE, UPDATE some staff in table

-- look at change history

SELECT * FROM cdc.dbo_tableName_CT

Also you can trakc DDL statments in ddl_history table

It would be nice to have user name in cdc.dbo_tableName_CT

|||

What is the performance impact of CDC?

Can you write the data to audit detail to another database?

-John

|||

Hi all,

I have also worked a little on the CDC. You can find my notes at http://www.kodyaz.com/articles/change-data-capture.aspx

As far as I see, there is not any information about who did the change kept on the CDC tables, on mirror of the original tracked table. Or am I missing something since I did not check more on the underlying tables.

CDC is a common topic all of us dealing with. I guess you have followed the topic "Data Auditing vs CDC" at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1730222&SiteID=1 also topic "CDC" at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1752141&SiteID=1

In those forms, CDC is said to be designed for ETL and also data is extracted from transaction logs. Additional disk activity is the major topic that may affect the performance. But it should be handled in each databases own conditions.

I do not think it is possible to configure the CDC tables to be created on an other database.

|||

eralper wrote:

As far as I see, there is not any information about who did the change kept on the CDC tables, on mirror of the original tracked table. Or am I missing something since I did not check more on the underlying tables.

A lot of DBA and programmers will use CDC to kept record of changaed data, but withou who part, its a little bit poor feature.

|||

Since I only have Katmai running on a MacBook Pro running Vista in Parallels Desktop, and on a lowly server in our data center, I have not had the luxury of doing extensive performance tests just yet. Simon Sabin raised an issue on connect about the expense of turning a bulk update into a set of 1000's of insert statements (to the tune of 2 * the number of rows affected), which I can understand would take over certain systems.

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283761

As for writing the data to another database, you don't have any control over the destination CDC objects, but sure, you can create a trigger against them. I coded up a very basic example which (thouh it stored the data in the same DB, it doesn't have to) augmented the data collection with username and date/time, which CDC doesn't collect:

http://sqlblog.com/blogs/aaron_bertrand/archive/2007/06/21/playing-with-cdc-in-katmai.aspx

I asked for more options here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283707

Note that there are currently a couple of bugs, for example, modifying the base table in SSMS will eradicate the CDC objects on it without warning, and modifying the table using ALTER TABLE does not change the set of columns that are captured. If you drop a column, it stays in the capture table but all values become NULL; if you add a column, it does not appear in the capture table unloess you drop the CDC config and re-create it. I did not test what happens when you rename a column or change its datatype.

These are documented here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283765

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283442

Hope this information is helpful.

--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006

|||Sorry, this was in response to:

>>

What is the performance impact of CDC?

Can you write the data to audit detail to another database?
>>

These forums don't handle threading very well, do they?

|||

CDC will have performance impact. a form of replication's logreader agent will scan the transaction log of the database ( can consume CPU as well as disk activity) and will write to the change tables. So for every ins/upd/del you want caputred will incur an additional write to disk. Since disk can be a bottleneck there are a couple ways to alleviate this - the capture scan job can be scheduled to run at off peak hours, and you can also place the capture tables on a different db filegroup, but it has to be the same filegroup as the db.

|||

One more note - as mentioned above, CDC was not designed for auditing, so it most likely won't meet your auditing needs.

|||

As Greg has already mentioned, CDC is not designed for auditing (as traditionally defined) puposes. If it meets your needs, then that is great. As I've already posted earlier in this thread, we do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 July CTP. I'd highly recommend trying out the auditing functionality when it becomes available in a future CTP.

For more on CDC vs. Auditing, take a look at the following thread on this forum: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1730222&SiteID=1

Audit tables ?

I cant find feature to audit executin of statements on table level (I read somewhere that is one of new feature of SQL 2008). For an exemple to now who is make an UPDATE, INSERT or DELETE statements.

In Katmai we have the cdc(Change data Capture).Change data capture(CDC) is designed to capture insert, update, and delete activity applied to SQL Server tables, and to make the details of the changes available in an easily consumed relational format. The change tables used by change data capture contain columns that mirror the column structure of a tracked source table, along with the metadata needed to understand the changes that have occurred.

For more details go to books online and write "change data capture"....

.

|||We do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 June CTP. Expect to see it in a future CTP.|||

Sara Tahir [MSFT] wrote:

We do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 June CTP. Expect to see it in a future CTP.

I just tested cdc and it works fine in the june ctp.

|||

Yes, CDC works just fine. There is couple of steps to make ti work...but it's cool feature.

Example:

--to activate cdc

EXEC sys.sp_cdc_enable_db_change_data_capture

--checking

SELECT is_cdc_enabled FROM sys.databases WHERE name = 'databaseName'

--enabling chanage data capture on specific table

USE test;

GO

EXECUTE sys.sp_cdc_enable_table_change_data_capture
@.source_schema = N'dbo'
, @.source_name = N'Imena'
, @.role_name = N'cdc_Admin';

GO

-- INSERT, DELETE, UPDATE some staff in table

-- look at change history

SELECT * FROM cdc.dbo_tableName_CT

Also you can trakc DDL statments in ddl_history table

It would be nice to have user name in cdc.dbo_tableName_CT

|||

What is the performance impact of CDC?

Can you write the data to audit detail to another database?

-John

|||

Hi all,

I have also worked a little on the CDC. You can find my notes at http://www.kodyaz.com/articles/change-data-capture.aspx

As far as I see, there is not any information about who did the change kept on the CDC tables, on mirror of the original tracked table. Or am I missing something since I did not check more on the underlying tables.

CDC is a common topic all of us dealing with. I guess you have followed the topic "Data Auditing vs CDC" at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1730222&SiteID=1 also topic "CDC" at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1752141&SiteID=1

In those forms, CDC is said to be designed for ETL and also data is extracted from transaction logs. Additional disk activity is the major topic that may affect the performance. But it should be handled in each databases own conditions.

I do not think it is possible to configure the CDC tables to be created on an other database.

|||

eralper wrote:

As far as I see, there is not any information about who did the change kept on the CDC tables, on mirror of the original tracked table. Or am I missing something since I did not check more on the underlying tables.

A lot of DBA and programmers will use CDC to kept record of changaed data, but withou who part, its a little bit poor feature.

|||

Since I only have Katmai running on a MacBook Pro running Vista in Parallels Desktop, and on a lowly server in our data center, I have not had the luxury of doing extensive performance tests just yet. Simon Sabin raised an issue on connect about the expense of turning a bulk update into a set of 1000's of insert statements (to the tune of 2 * the number of rows affected), which I can understand would take over certain systems.

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283761

As for writing the data to another database, you don't have any control over the destination CDC objects, but sure, you can create a trigger against them. I coded up a very basic example which (thouh it stored the data in the same DB, it doesn't have to) augmented the data collection with username and date/time, which CDC doesn't collect:

http://sqlblog.com/blogs/aaron_bertrand/archive/2007/06/21/playing-with-cdc-in-katmai.aspx

I asked for more options here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283707

Note that there are currently a couple of bugs, for example, modifying the base table in SSMS will eradicate the CDC objects on it without warning, and modifying the table using ALTER TABLE does not change the set of columns that are captured. If you drop a column, it stays in the capture table but all values become NULL; if you add a column, it does not appear in the capture table unloess you drop the CDC config and re-create it. I did not test what happens when you rename a column or change its datatype.

These are documented here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283765

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283442

Hope this information is helpful.

--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006

|||Sorry, this was in response to:

>>

What is the performance impact of CDC?

Can you write the data to audit detail to another database?
>>

These forums don't handle threading very well, do they?

|||

CDC will have performance impact. a form of replication's logreader agent will scan the transaction log of the database ( can consume CPU as well as disk activity) and will write to the change tables. So for every ins/upd/del you want caputred will incur an additional write to disk. Since disk can be a bottleneck there are a couple ways to alleviate this - the capture scan job can be scheduled to run at off peak hours, and you can also place the capture tables on a different db filegroup, but it has to be the same filegroup as the db.

|||

One more note - as mentioned above, CDC was not designed for auditing, so it most likely won't meet your auditing needs.

|||

As Greg has already mentioned, CDC is not designed for auditing (as traditionally defined) puposes. If it meets your needs, then that is great. As I've already posted earlier in this thread, we do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 July CTP. I'd highly recommend trying out the auditing functionality when it becomes available in a future CTP.

For more on CDC vs. Auditing, take a look at the following thread on this forum: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1730222&SiteID=1

Audit tables ?

I cant find feature to audit executin of statements on table level (I read somewhere that is one of new feature of SQL 2008). For an exemple to now who is make an UPDATE, INSERT or DELETE statements.

In Katmai we have the cdc(Change data Capture).Change data capture(CDC) is designed to capture insert, update, and delete activity applied to SQL Server tables, and to make the details of the changes available in an easily consumed relational format. The change tables used by change data capture contain columns that mirror the column structure of a tracked source table, along with the metadata needed to understand the changes that have occurred.

For more details go to books online and write "change data capture"....

.

|||We do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 June CTP. Expect to see it in a future CTP.|||

Sara Tahir [MSFT] wrote:

We do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 June CTP. Expect to see it in a future CTP.

I just tested cdc and it works fine in the june ctp.

|||

Yes, CDC works just fine. There is couple of steps to make ti work...but it's cool feature.

Example:

--to activate cdc

EXEC sys.sp_cdc_enable_db_change_data_capture

--checking

SELECT is_cdc_enabled FROM sys.databases WHERE name = 'databaseName'

--enabling chanage data capture on specific table

USE test;

GO

EXECUTE sys.sp_cdc_enable_table_change_data_capture
@.source_schema = N'dbo'
, @.source_name = N'Imena'
, @.role_name = N'cdc_Admin';

GO

-- INSERT, DELETE, UPDATE some staff in table

-- look at change history

SELECT * FROM cdc.dbo_tableName_CT

Also you can trakc DDL statments in ddl_history table

It would be nice to have user name in cdc.dbo_tableName_CT

|||

What is the performance impact of CDC?

Can you write the data to audit detail to another database?

-John

|||

Hi all,

I have also worked a little on the CDC. You can find my notes at http://www.kodyaz.com/articles/change-data-capture.aspx

As far as I see, there is not any information about who did the change kept on the CDC tables, on mirror of the original tracked table. Or am I missing something since I did not check more on the underlying tables.

CDC is a common topic all of us dealing with. I guess you have followed the topic "Data Auditing vs CDC" at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1730222&SiteID=1 also topic "CDC" at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1752141&SiteID=1

In those forms, CDC is said to be designed for ETL and also data is extracted from transaction logs. Additional disk activity is the major topic that may affect the performance. But it should be handled in each databases own conditions.

I do not think it is possible to configure the CDC tables to be created on an other database.

|||

eralper wrote:

As far as I see, there is not any information about who did the change kept on the CDC tables, on mirror of the original tracked table. Or am I missing something since I did not check more on the underlying tables.

A lot of DBA and programmers will use CDC to kept record of changaed data, but withou who part, its a little bit poor feature.

|||

Since I only have Katmai running on a MacBook Pro running Vista in Parallels Desktop, and on a lowly server in our data center, I have not had the luxury of doing extensive performance tests just yet. Simon Sabin raised an issue on connect about the expense of turning a bulk update into a set of 1000's of insert statements (to the tune of 2 * the number of rows affected), which I can understand would take over certain systems.

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283761

As for writing the data to another database, you don't have any control over the destination CDC objects, but sure, you can create a trigger against them. I coded up a very basic example which (thouh it stored the data in the same DB, it doesn't have to) augmented the data collection with username and date/time, which CDC doesn't collect:

http://sqlblog.com/blogs/aaron_bertrand/archive/2007/06/21/playing-with-cdc-in-katmai.aspx

I asked for more options here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283707

Note that there are currently a couple of bugs, for example, modifying the base table in SSMS will eradicate the CDC objects on it without warning, and modifying the table using ALTER TABLE does not change the set of columns that are captured. If you drop a column, it stays in the capture table but all values become NULL; if you add a column, it does not appear in the capture table unloess you drop the CDC config and re-create it. I did not test what happens when you rename a column or change its datatype.

These are documented here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283765

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=283442

Hope this information is helpful.

--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006

|||Sorry, this was in response to:

>>

What is the performance impact of CDC?

Can you write the data to audit detail to another database?
>>

These forums don't handle threading very well, do they?

|||

CDC will have performance impact. a form of replication's logreader agent will scan the transaction log of the database ( can consume CPU as well as disk activity) and will write to the change tables. So for every ins/upd/del you want caputred will incur an additional write to disk. Since disk can be a bottleneck there are a couple ways to alleviate this - the capture scan job can be scheduled to run at off peak hours, and you can also place the capture tables on a different db filegroup, but it has to be the same filegroup as the db.

|||

One more note - as mentioned above, CDC was not designed for auditing, so it most likely won't meet your auditing needs.

|||

As Greg has already mentioned, CDC is not designed for auditing (as traditionally defined) puposes. If it meets your needs, then that is great. As I've already posted earlier in this thread, we do plan to provide auditing support in SQL Server 2008. However, the feature is not available in SQL Server 2008 July CTP. I'd highly recommend trying out the auditing functionality when it becomes available in a future CTP.

For more on CDC vs. Auditing, take a look at the following thread on this forum: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1730222&SiteID=1

Attaching database to SQL Server 2005 failed!

Hi, all masters here, please help me for attaching database to the SQL Server 2005 then. I cant attach any database to my SQL Server 2005! Error as below always happened!

could not find row in sysindexes for database ID 21, object ID 1, index ID 1, Run DBCC CHECKTABLE on sysindexes

So what is indeed the problem tho? please help me then. Thanks a lot.

Hi,

seems that your data is corrupt in any way, did you try to attach the database via

sp_attach_single_file_db, this normally ignores some checks but could leave your database inconsistent (maybe), so better use a copy to try that.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||

Hi,Jens,

Thanks a lot. I tried to attach the database files with sql scripts then but only those database files which are created on the SQL Server could be attached. Those database files created outside of my local computer wont work tho (even the sample databases installed from SQL Server CD!). The error occured as I posted above. So what is exactly the problem tho? What can I try to fix it? Really need help and thanks a lot.

Kind regards,

attaching a ms access project file to SQL Server 2005 Express

I have some sample files from the Access Inside OUt 2003 book I want to
attach to my server. I can't figure out how to be able to connect to them
from the Server?
I can't connect to them from the SQL Server at all So I am trying to attach
them with this batch script.
I run this from the document window in SQL Server Management Studio :
sp_attach_db "ContactsSQL",
"C:\Microsoft Press\Access 2003 Inside Out\SQL\ContactsSQL.mdf",
"C:\Microsoft Press\Access 2003 Inside Out\SQL\ContactsSQL.ldf"
and I get this error message:
sg 5120, Level 16, State 101, Line 1
Unable to open the physical file "C:\Microsoft Press\Access 2003 Inside
Out\SQL\ContactsSQL.ldf". Operating system error 5: "5(Access is denied.)".
I changed the user account control to on so how can I read this access
project file from the SQL Server?
thanks
Hi
Have you checked that there is not a typing mistake in the batch file and
that you have the correct name for the log file? Check the file permissions
on each of these files. Alternatively you can rename the log file you have
and try sp_attach_single_file_db
John
"Janis" wrote:

> I have some sample files from the Access Inside OUt 2003 book I want to
> attach to my server. I can't figure out how to be able to connect to them
> from the Server?
> I can't connect to them from the SQL Server at all So I am trying to attach
> them with this batch script.
> I run this from the document window in SQL Server Management Studio :
> sp_attach_db "ContactsSQL",
> "C:\Microsoft Press\Access 2003 Inside Out\SQL\ContactsSQL.mdf",
> "C:\Microsoft Press\Access 2003 Inside Out\SQL\ContactsSQL.ldf"
> and I get this error message:
> sg 5120, Level 16, State 101, Line 1
> Unable to open the physical file "C:\Microsoft Press\Access 2003 Inside
> Out\SQL\ContactsSQL.ldf". Operating system error 5: "5(Access is denied.)".
> I changed the user account control to on so how can I read this access
> project file from the SQL Server?
> thanks
|||Thanks for your answer. I tried some connections and then I ran the batch
and I get another response.
Msg 1801, Level 16, State 3, Line 1
Database 'ContactsSQL' already exists. Choose a different database name.
I don't understand what is going on here. So I have the contactsSQL
database supposed connected. I don't see any contact tables listed in the
database engine. I registered the connection. I have the Contacts access
project file open and the connection tested okay. I don't understand how
they are connected because there are no dbo.tables in the Access objects. I
am using Access 2008 and Vista.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked that there is not a typing mistake in the batch file and
> that you have the correct name for the log file? Check the file permissions
> on each of these files. Alternatively you can rename the log file you have
> and try sp_attach_single_file_db
> John
> "Janis" wrote:
|||One possibility:
Since you copied the *.mdf/*.ldf file from CD coming with the book, the
files are read-only. You need to clear the "Read ONly" bit first
(rigth-click the files and select "Properties").
"Janis" <Janis@.discussions.microsoft.com> wrote in message
news:5FA5913E-2B03-4756-88CB-FFC8AC8F27AB@.microsoft.com...
>I have some sample files from the Access Inside OUt 2003 book I want to
> attach to my server. I can't figure out how to be able to connect to them
> from the Server?
> I can't connect to them from the SQL Server at all So I am trying to
> attach
> them with this batch script.
> I run this from the document window in SQL Server Management Studio :
> sp_attach_db "ContactsSQL",
> "C:\Microsoft Press\Access 2003 Inside Out\SQL\ContactsSQL.mdf",
> "C:\Microsoft Press\Access 2003 Inside Out\SQL\ContactsSQL.ldf"
> and I get this error message:
> sg 5120, Level 16, State 101, Line 1
> Unable to open the physical file "C:\Microsoft Press\Access 2003 Inside
> Out\SQL\ContactsSQL.ldf". Operating system error 5: "5(Access is
> denied.)".
> I changed the user account control to on so how can I read this access
> project file from the SQL Server?
> thanks
|||When I try to Use the database then I get this message:
Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'contacts'. No entry
found with that name. Make sure that the name is entered correctly.
So it appears I haven't really connected to the database even though it
passed the connection test.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked that there is not a typing mistake in the batch file and
> that you have the correct name for the log file? Check the file permissions
> on each of these files. Alternatively you can rename the log file you have
> and try sp_attach_single_file_db
> John
> "Janis" wrote:
|||Hi Janis
In one post you call the database contacts and the other contactsSQL.
John
"Janis" wrote:
[vbcol=seagreen]
> When I try to Use the database then I get this message:
> Msg 911, Level 16, State 1, Line 1
> Could not locate entry in sysdatabases for database 'contacts'. No entry
> found with that name. Make sure that the name is entered correctly.
> So it appears I haven't really connected to the database even though it
> passed the connection test.
> "John Bell" wrote:
|||You are right again. thanks, I thought they were all access files. I just
looked at the extensions and it is a SQL Server file which I attached to. I
still haven't gotten connected to the adp file yet but I thought I did.
Thanks for noticing it.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Janis
> In one post you call the database contacts and the other contactsSQL.
> John
> "Janis" wrote: