Showing posts with label mssql. Show all posts
Showing posts with label mssql. Show all posts

Wednesday, March 28, 2012

Long query block insert?

Hi,
Have a question, I have a select query that I used for bcp out one of my MS
SQL 2000 DB table ( about 30 million of records) and it take more than 3 hrs
to finish(about 13 million record). It happen that when this bcp process is
running no record can be inserted to this table.
Isn't that the select will release lock after it read pass the data?
Thanks!
KH TanHi,
Generally for BCP OUT the table will not be locked and user can insert data.
Can you try using BCP OUT with -b (Batch size) option and see what happens.
Thanks
Hari
SQL Server MVP
"KH TAN" <KH TAN@.discussions.microsoft.com> wrote in message
news:A4F01220-E1A3-4329-B059-6807D824A7B4@.microsoft.com...
> Hi,
> Have a question, I have a select query that I used for bcp out one of my
> MS
> SQL 2000 DB table ( about 30 million of records) and it take more than 3
> hrs
> to finish(about 13 million record). It happen that when this bcp process
> is
> running no record can be inserted to this table.
> Isn't that the select will release lock after it read pass the data?
> Thanks!
> KH Tan|||Thanks!
I notice that not only the BCP Out having the problem, some other long
running query (select statement) also do the same. I do a dbcc dbreindex on
the table and rerun the query, everything seem comming back to normal..weird
!
Regards,
KH Tan.
"Hari Prasad" wrote:

> Hi,
> Generally for BCP OUT the table will not be locked and user can insert dat
a.
> Can you try using BCP OUT with -b (Batch size) option and see what happens
.
> Thanks
> Hari
> SQL Server MVP
> "KH TAN" <KH TAN@.discussions.microsoft.com> wrote in message
> news:A4F01220-E1A3-4329-B059-6807D824A7B4@.microsoft.com...
>
>|||Have you used sp_lock or select from sysprocesses to see where the blocking
might be?
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"KH TAN" <KHTAN@.discussions.microsoft.com> wrote in message
news:78B09111-07E0-4380-A8A8-45FA56FD93CC@.microsoft.com...
> Thanks!
> I notice that not only the BCP Out having the problem, some other long
> running query (select statement) also do the same. I do a dbcc dbreindex
on
> the table and rerun the query, everything seem comming back to
normal..weird![vbcol=seagreen]
> Regards,
> KH Tan.
>
> "Hari Prasad" wrote:
>
data.[vbcol=seagreen]
happens.[vbcol=seagreen]
my[vbcol=seagreen]
3[vbcol=seagreen]
process[vbcol=seagreen]

Long query block insert?

Hi,
Have a question, I have a select query that I used for bcp out one of my MS
SQL 2000 DB table ( about 30 million of records) and it take more than 3 hrs
to finish(about 13 million record). It happen that when this bcp process is
running no record can be inserted to this table.
Isn't that the select will release lock after it read pass the data?
Thanks!
KH Tan
Hi,
Generally for BCP OUT the table will not be locked and user can insert data.
Can you try using BCP OUT with -b (Batch size) option and see what happens.
Thanks
Hari
SQL Server MVP
"KH TAN" <KH TAN@.discussions.microsoft.com> wrote in message
news:A4F01220-E1A3-4329-B059-6807D824A7B4@.microsoft.com...
> Hi,
> Have a question, I have a select query that I used for bcp out one of my
> MS
> SQL 2000 DB table ( about 30 million of records) and it take more than 3
> hrs
> to finish(about 13 million record). It happen that when this bcp process
> is
> running no record can be inserted to this table.
> Isn't that the select will release lock after it read pass the data?
> Thanks!
> KH Tan
|||Thanks!
I notice that not only the BCP Out having the problem, some other long
running query (select statement) also do the same. I do a dbcc dbreindex on
the table and rerun the query, everything seem comming back to normal..weird!
Regards,
KH Tan.
"Hari Prasad" wrote:

> Hi,
> Generally for BCP OUT the table will not be locked and user can insert data.
> Can you try using BCP OUT with -b (Batch size) option and see what happens.
> Thanks
> Hari
> SQL Server MVP
> "KH TAN" <KH TAN@.discussions.microsoft.com> wrote in message
> news:A4F01220-E1A3-4329-B059-6807D824A7B4@.microsoft.com...
>
>
|||Have you used sp_lock or select from sysprocesses to see where the blocking
might be?
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"KH TAN" <KHTAN@.discussions.microsoft.com> wrote in message
news:78B09111-07E0-4380-A8A8-45FA56FD93CC@.microsoft.com...
> Thanks!
> I notice that not only the BCP Out having the problem, some other long
> running query (select statement) also do the same. I do a dbcc dbreindex
on
> the table and rerun the query, everything seem comming back to
normal..weird![vbcol=seagreen]
> Regards,
> KH Tan.
>
> "Hari Prasad" wrote:
data.[vbcol=seagreen]
happens.[vbcol=seagreen]
my[vbcol=seagreen]
3[vbcol=seagreen]
process[vbcol=seagreen]
sql

Friday, March 23, 2012

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls advice
Are you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>
|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...
|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...
|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>
|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>
|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft]&
#91;ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp
4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empt
y
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanis
m
to ensure that data is completely written and also there are no power failur
e
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>

Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:
> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql
> sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
>|||"bijupg@.hotmail.com" schrieb:
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:
> "bijupg@.hotmail.com" schrieb:
> > Hi Guys,
> > I am facing following problem with MSSQL Server 2000.
> > I am using Microsoft sql server Log Shipping feature to have a standby
> > server for disaster recovery purposes.
> > in the logshipping Destination server while restoring the transaction log
> > the restore process is failling with following error.
> >
> > "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> > transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> > Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> > PrevPageLSN: (8122:7374:3)."
> >
> > Both servers, source and destination were running with SQL SERVER
> > ENTERPRISE EDITION SP3 .
> > after this failure i rebuilded the logshipping process but same error
> > happened again so after one week updated the destination server with sql sp4
> > and rebuilded the logshipping process . but the same error happened again.
> > During this error SQL Server is creating a dump file and text file
> >
> > pls advice
> Did you do transaction log backups in between? Don't forget that they empty
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>> Hi Guys,
>> I am facing following problem with MSSQL Server 2000.
>> I am using Microsoft sql server Log Shipping feature to have a standby
>> server for disaster recovery purposes.
>> in the logshipping Destination server while restoring the transaction log
>> the restore process is failling with following error.
>> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
>> SQL
>> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
>> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
>> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
>> PrevPageLSN: (8122:7374:3)."
>> Both servers, source and destination were running with SQL SERVER
>> ENTERPRISE EDITION SP3 .
>> after this failure i rebuilded the logshipping process but same error
>> happened again so after one week updated the destination server with sql
>> sp4
>> and rebuilded the logshipping process . but the same error happened
>> again.
>> During this error SQL Server is creating a dump file and text file
>> pls advice
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanism
to ensure that data is completely written and also there are no power failure
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:
> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you can
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> > The type of error you are seeing is most likely being caused by corruption
> > in your transaction logs. Review system event logs on both servers for ANY
> > hardware-related warnings and errors. Update all your firmware and
> > drivers.
> >
> > Adrian
> >
> >
> > "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> > message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> >> Hi Guys,
> >> I am facing following problem with MSSQL Server 2000.
> >> I am using Microsoft sql server Log Shipping feature to have a standby
> >> server for disaster recovery purposes.
> >> in the logshipping Destination server while restoring the transaction log
> >> the restore process is failling with following error.
> >>
> >> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC
> >> SQL
> >> Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
> >> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> >> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> >> PrevPageLSN: (8122:7374:3)."
> >>
> >> Both servers, source and destination were running with SQL SERVER
> >> ENTERPRISE EDITION SP3 .
> >> after this failure i rebuilded the logshipping process but same error
> >> happened again so after one week updated the destination server with sql
> >> sp4
> >> and rebuilded the logshipping process . but the same error happened
> >> again.
> >> During this error SQL Server is creating a dump file and text file
> >>
> >> pls advice
> >
> >
>
>sql

Wednesday, March 21, 2012

logs of creating and deleteing jobs

Hello
Does anybody know where/if MSSQL (especially 2005) keeps logs of
creating and deleteing jobs?

Thanks in advance
BartoloNo, it does not. Jobs are simple entries in the MSDB database, if you
want to keep track of that you will either have to tweak the appropiate
procedure that access these tables or write a trigger on the tables if
you are not sure if someone directly manipulates the tables.

HTH, Jens Suessmeyer.

--
http://www.sqlserver2005.de
--|||Thanks Jens,
I wrote that because, I realized that one of my db haven't got backup
job since few days. Job had been written before and I dont know who
could do that or why it disappeard.

Regards,
Bartolosql

Logreader access violation

Hi everyone,
I am setting up Transaction Replication on a MSSQL 2000 8.0.194. Everything
was going fine until the log reader stopped with a "An access violation
occurred" error.
I tried setting up a publication on another test database on the same server
to make sure the problem was not with the database it self and encountered
the same error.
In the ReplExceptLogRdr.log I am getting the following error:
Microsoft SQL Server Replication: Exception Stack Dump
************************************************** *****
Computer type is AT/AT COMPATIBLE.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 A10Current local time is Fri Apr 13
15:16:41 2007
4 Intel x86 level 15, 2392 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
MemoryLoad 62%TotalPhys 2047 MB
AvailPhys 1481 MBTotalPageFile 4095 MB
************************************************** *****
An exception was caught
in LOGREAD.EXE
* Exception Address = 00000001
* Exception Code = c0000005
*
************************************************** *****
Module NameReturn AddressLocation
[No Module Info]003678f000000001
[No Module Info]0040abd5003678f0
logread0040dec90040abd5
logread0040aa5c0040dec9
logread77e4f38c0040aa5c
kernel3200000000TerminateThread + 113
I have tested setting up replication using the same database on the users
reporting server and everything went fine. I have tried giving the folder
that contains the Distributor database and logfile access to "Everyone".
The Event Viewer show the following error and information:
[SQLSERVERAgent Error]
Microsoft SQL Server Replication : The LOGREAD.EXE executable is terminating
abnormally because it hit an exception. Exception Code c0000005. Check file
ReplExceptLogRdr.log for details.
[Information]
SubSystem Message - Job 'CL-SQL-CLUAT-1'
(0x7A865965F727AB4CA60CC19D5A5EEEA8), step 2 - An access violation occurred.
I tried changing the Logreaders agents verbose level to 3, but nothing extra
appeared in the sqlserver log.
Before I set up replication I had to change the logon the sqlserver agent
was running from the system account to a windows user with Admin rights. The
user also has sql server admin rights.
I am kind of stuck now as I don't know what else I can do to further
investigate the problem.
Any help would really be appreciated.
Thanks,
SQLNewbie
Hi Hillary,
Thanks for your time on this. I did post the contents of the
ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
referring to? I am not sure what you mean by (IIRC).
I wasn't sure if this was a bug so I haven't applied any patches.
Is this a user rights problem? That is the user running the SQL Server agent
has insufficient rights, because the user I created has Admin rights for
Windows and System Admin rights for SQL Server.
Thanks,
SQLNEwbie
"Hilary Cotter" wrote:

> I get these from time to time. Did you check ReplExceptLogRdr.log IIRC it
> will be found in windows\system32
> Also does this apply?
> http://support.microsoft.com/kb/872843/EN-US/
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "sqlnewbie" <sqlnewbie@.discussions.microsoft.com> wrote in message
> news:C5CCC218-2858-42BD-97BE-6C0B3AB1054E@.microsoft.com...
>
>
|||Hi,
Just a quick update on this problem. I applied SP4 and that has resolved the
problem.
Thanks
"sqlnewbie" wrote:
[vbcol=seagreen]
> Hi Hillary,
> Thanks for your time on this. I did post the contents of the
> ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
> Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
> referring to? I am not sure what you mean by (IIRC).
> I wasn't sure if this was a bug so I haven't applied any patches.
> Is this a user rights problem? That is the user running the SQL Server agent
> has insufficient rights, because the user I created has Admin rights for
> Windows and System Admin rights for SQL Server.
> Thanks,
> SQLNEwbie
> "Hilary Cotter" wrote:

Wednesday, March 7, 2012

Login Triggers?

Quick question about SQL 2000. Are there ways to have a trigger fire when
someone (anyone) logs in to a MSSQL SQL 2000 instance? I had thought MSSQL
came with login triggers but I haven't been able to find any info.
TIA,
JDNo, sorry.
If you want to track logins, you can log all login attempts. Or you can run
a SQL Trace that captures that information. However, if you wanted to do
some additional work for the user, there is no trigger for that.
RLF
"Joe D" <jkdriscoll@.qg.com> wrote in message
news:dvph8d$2k91$1@.sxnews1.qg.com...
> Quick question about SQL 2000. Are there ways to have a trigger fire when
> someone (anyone) logs in to a MSSQL SQL 2000 instance? I had thought MSSQL
> came with login triggers but I haven't been able to find any info.
> TIA,
> JD
>|||thanks for the feed back Russell.
Do you if SQL 2005 will offer it?
Thanks again.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:O5cm9uRTGHA.4900@.TK2MSFTNGP12.phx.gbl...
> No, sorry.
> If you want to track logins, you can log all login attempts. Or you can
> run a SQL Trace that captures that information. However, if you wanted to
> do some additional work for the user, there is no trigger for that.
> RLF
> "Joe D" <jkdriscoll@.qg.com> wrote in message
> news:dvph8d$2k91$1@.sxnews1.qg.com...
>|||Hello Joe,

> Do you if SQL 2005 will offer it?
Thats an interesting question. The answer is yes, but you'll have to be a
bit more creative than you might like.
In 2005 you can do an CREATE EVENT NOTIFICATION on SERVER FOR AUDIT_LOGIN|AU
DIT_LOGIN_FAILED|AUDIT_LOGOUT
etc and send that payload to a service broker queue for processing. The spro
c
that processes queued messages could then do what you neeed more than likely
.
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Interesting.
Thanks Kent.
"Kent Tegels" <ktegels@.develop.com> wrote in message
news:b87ad741c12a8c81b0a6c56b8f0@.news.microsoft.com...
> Hello Joe,
>
> Thats an interesting question. The answer is yes, but you'll have to be a
> bit more creative than you might like.
> In 2005 you can do an CREATE EVENT NOTIFICATION on SERVER FOR
> AUDIT_LOGIN|AUDIT_LOGIN_FAILED|AUDIT_LOG
OUT etc and send that payload to a
> service broker queue for processing. The sproc that processes queued
> messages could then do what you neeed more than likely.
> Thank you,
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>|||>> Thats an interesting question. The answer is yes, but you'll have to[vbcol=seagreen]
Closing the loop on this: http://www.sqljunkies.com/WebLog/kt...ifications.aspx
Enjoy!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

Login to Reports Manager?

Hi,
I am trying to login to Report Manager (MSSQL 2005) on my server
https://www.[mydomain].com/Reports with administrator user & Pass but login
failed with error: "The request failed with HTTP status 401: Unauthorized."
Any help will be much appreciated.
Regards,
AsafHi Asaf,
Thank you for posting.
Regarding on the 401 login failed issue you mentioned in SSRS report
manager application, based on my research, there does existing some issue
related to IIS and windows server name setting. The following msdn
document has mentioned two conditions that has the similiar error
behavior:
#How to: Configure Reporting Services to Use a Non-Default Web Site
(Reporting Services Configuration)
http://msdn2.microsoft.com/en-US/library/ms155921(SQL.90).aspx
You can have a look to see whether this helps resolve the problem.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hello Steven,
I have reinstalled SQL Reporting Services and now it working fine.
Thanks for your support.
Regards,
Asaf
"Steven Cheng[MSFT]" wrote:
> Hi Asaf,
> Thank you for posting.
> Regarding on the 401 login failed issue you mentioned in SSRS report
> manager application, based on my research, there does existing some issue
> related to IIS and windows server name setting. The following msdn
> document has mentioned two conditions that has the similiar error
> behavior:
> #How to: Configure Reporting Services to Use a Non-Default Web Site
> (Reporting Services Configuration)
> http://msdn2.microsoft.com/en-US/library/ms155921(SQL.90).aspx
> You can have a look to see whether this helps resolve the problem.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>|||That's fine Asaf,
Glad that you've got it working now.
Good luck!
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

login statistics

I am wondering if there is an sp in mssql server that is
equivalent to the sybase sp_reportstats.
This sp prints out the current accounting totals for all
logins, as well as each login's individual statistics and
percentage of the overall statistics.
eg
loginname, cpu, percent of cpu, I/O percent I/OHi,
Have a look into the procedure SP_WHO2 and the master..sysprocesses system
table.
Thanks
Hari
MCDBA
"Bola" <anonymous@.discussions.microsoft.com> wrote in message
news:18e0701c41bc5$9da48a50$a401280a@.phx
.gbl...
> I am wondering if there is an sp in mssql server that is
> equivalent to the sybase sp_reportstats.
> This sp prints out the current accounting totals for all
> logins, as well as each login's individual statistics and
> percentage of the overall statistics.
> eg
> loginname, cpu, percent of cpu, I/O percent I/O

Login setting by IP range?

Hello,
In MySQL we can set to allow a user to login and access certain
table from certain host, is there anything close to that in MSSQL 2000/2005?
Actually, we just need to control certain users unable to use the
Domain Creditial to access certain databases/tables except in the company's
IP, while we need to make sure for certain databases/tables, the client can
be accessed anywhere.
If not, is there any kind of database connection proxies that we can
use to control the connections, or this there any tutorial on how to relay
database datas so we can write a program to do access check?
Looking forward for reply.
Regards,
Lau Lei Cheong
Lau
How do they (users) access the database? Did you divide them into Groups?
You can DENY access on table for the user .
In addition , you can specify a hostname in connection string.
"Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hello,
> In MySQL we can set to allow a user to login and access certain
> table from certain host, is there anything close to that in MSSQL
> 2000/2005?
> Actually, we just need to control certain users unable to use the
> Domain Creditial to access certain databases/tables except in the
> company's IP, while we need to make sure for certain databases/tables, the
> client can be accessed anywhere.
> If not, is there any kind of database connection proxies that we
> can use to control the connections, or this there any tutorial on how to
> relay database datas so we can write a program to do access check?
> Looking forward for reply.
> Regards,
> Lau Lei Cheong
>
|||Yes, I know I can divide users into groups but that's not the problem.
The problem is, as the subject line suggested, I can't find way to limit
certain user's access to certain database/table from certain IP.
"Uri Dimant" <urid@.iscar.co.il> glsD:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx. gbl...
> Lau
> How do they (users) access the database? Did you divide them into Groups?
> You can DENY access on table for the user .
> In addition , you can specify a hostname in connection string.
>
> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
> news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
>
|||Well, have a look at APPLICATION ROLE in the BOL
"Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
news:O2MjaNHMGHA.3960@.TK2MSFTNGP09.phx.gbl...
> Yes, I know I can divide users into groups but that's not the problem.
> The problem is, as the subject line suggested, I can't find way to limit
> certain user's access to certain database/table from certain IP.
> "Uri Dimant" <urid@.iscar.co.il>
> glsD:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx. gbl...
>
|||Sorry, I've reviewed application role, but it don't help in this case
because:
1) I need to control access by IP, not by application
2) Some users under the control are application developers who can write
their own application.
But your information is really useful on other area, thanks.
"Uri Dimant" <urid@.iscar.co.il> glsD:%23TPXYYHMGHA.2696@.TK2MSFTNGP14.phx .gbl...
> Well, have a look at APPLICATION ROLE in the BOL
> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
> news:O2MjaNHMGHA.3960@.TK2MSFTNGP09.phx.gbl...
>

Login setting by IP range?

Hello,
In mysql we can set to allow a user to login and access certain
table from certain host, is there anything close to that in MSSQL 2000/2005?
Actually, we just need to control certain users unable to use the
Domain Creditial to access certain databases/tables except in the company's
IP, while we need to make sure for certain databases/tables, the client can
be accessed anywhere.
If not, is there any kind of database connection proxies that we can
use to control the connections, or this there any tutorial on how to relay
database datas so we can write a program to do access check?
Looking forward for reply.
Regards,
Lau Lei CheongLau
How do they (users) access the database? Did you divide them into Groups?
You can DENY access on table for the user .
In addition , you can specify a hostname in connection string.
"Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hello,
> In mysql we can set to allow a user to login and access certain
> table from certain host, is there anything close to that in MSSQL
> 2000/2005?
> Actually, we just need to control certain users unable to use the
> Domain Creditial to access certain databases/tables except in the
> company's IP, while we need to make sure for certain databases/tables, the
> client can be accessed anywhere.
> If not, is there any kind of database connection proxies that we
> can use to control the connections, or this there any tutorial on how to
> relay database datas so we can write a program to do access check?
> Looking forward for reply.
> Regards,
> Lau Lei Cheong
>|||Yes, I know I can divide users into groups but that's not the problem.
The problem is, as the subject line suggested, I can't find way to limit
certain user's access to certain database/table from certain IP.
"Uri Dimant" <urid@.iscar.co.il> glsD:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx.gbl...[vbc
ol=seagreen]
> Lau
> How do they (users) access the database? Did you divide them into Groups?
> You can DENY access on table for the user .
> In addition , you can specify a hostname in connection string.
>
> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
> news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
>[/vbcol]|||Well, have a look at APPLICATION ROLE in the BOL
"Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
news:O2MjaNHMGHA.3960@.TK2MSFTNGP09.phx.gbl...
> Yes, I know I can divide users into groups but that's not the problem.
> The problem is, as the subject line suggested, I can't find way to limit
> certain user's access to certain database/table from certain IP.
> "Uri Dimant" <urid@.iscar.co.il>
> glsD:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx.gbl...
>|||Sorry, I've reviewed application role, but it don't help in this case
because:
1) I need to control access by IP, not by application
2) Some users under the control are application developers who can write
their own application.
But your information is really useful on other area, thanks.
"Uri Dimant" <urid@.iscar.co.il> glsD:%23TPXYYHMGHA.2696@.TK2MSFTNGP14.phx.gbl...[vb
col=seagreen]
> Well, have a look at APPLICATION ROLE in the BOL
> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
> news:O2MjaNHMGHA.3960@.TK2MSFTNGP09.phx.gbl...
>[/vbcol]

Login setting by IP range?

Hello,
In MySQL we can set to allow a user to login and access certain
table from certain host, is there anything close to that in MSSQL 2000/2005?
Actually, we just need to control certain users unable to use the
Domain Creditial to access certain databases/tables except in the company's
IP, while we need to make sure for certain databases/tables, the client can
be accessed anywhere.
If not, is there any kind of database connection proxies that we can
use to control the connections, or this there any tutorial on how to relay
database datas so we can write a program to do access check?
Looking forward for reply.
Regards,
Lau Lei CheongLau
How do they (users) access the database? Did you divide them into Groups?
You can DENY access on table for the user .
In addition , you can specify a hostname in connection string.
"Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hello,
> In MySQL we can set to allow a user to login and access certain
> table from certain host, is there anything close to that in MSSQL
> 2000/2005?
> Actually, we just need to control certain users unable to use the
> Domain Creditial to access certain databases/tables except in the
> company's IP, while we need to make sure for certain databases/tables, the
> client can be accessed anywhere.
> If not, is there any kind of database connection proxies that we
> can use to control the connections, or this there any tutorial on how to
> relay database datas so we can write a program to do access check?
> Looking forward for reply.
> Regards,
> Lau Lei Cheong
>|||Yes, I know I can divide users into groups but that's not the problem.
The problem is, as the subject line suggested, I can't find way to limit
certain user's access to certain database/table from certain IP.
"Uri Dimant" <urid@.iscar.co.il> ¼¶¼g©ó¶l¥ó·s»D:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx.gbl...
> Lau
> How do they (users) access the database? Did you divide them into Groups?
> You can DENY access on table for the user .
> In addition , you can specify a hostname in connection string.
>
> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
> news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
>> Hello,
>> In MySQL we can set to allow a user to login and access certain
>> table from certain host, is there anything close to that in MSSQL
>> 2000/2005?
>> Actually, we just need to control certain users unable to use the
>> Domain Creditial to access certain databases/tables except in the
>> company's IP, while we need to make sure for certain databases/tables,
>> the client can be accessed anywhere.
>> If not, is there any kind of database connection proxies that we
>> can use to control the connections, or this there any tutorial on how to
>> relay database datas so we can write a program to do access check?
>> Looking forward for reply.
>> Regards,
>> Lau Lei Cheong
>>
>|||Well, have a look at APPLICATION ROLE in the BOL
"Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
news:O2MjaNHMGHA.3960@.TK2MSFTNGP09.phx.gbl...
> Yes, I know I can divide users into groups but that's not the problem.
> The problem is, as the subject line suggested, I can't find way to limit
> certain user's access to certain database/table from certain IP.
> "Uri Dimant" <urid@.iscar.co.il>
> ¼¶¼g©ó¶l¥ó·s»D:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx.gbl...
>> Lau
>> How do they (users) access the database? Did you divide them into Groups?
>> You can DENY access on table for the user .
>> In addition , you can specify a hostname in connection string.
>>
>> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
>> news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
>> Hello,
>> In MySQL we can set to allow a user to login and access certain
>> table from certain host, is there anything close to that in MSSQL
>> 2000/2005?
>> Actually, we just need to control certain users unable to use the
>> Domain Creditial to access certain databases/tables except in the
>> company's IP, while we need to make sure for certain databases/tables,
>> the client can be accessed anywhere.
>> If not, is there any kind of database connection proxies that we
>> can use to control the connections, or this there any tutorial on how to
>> relay database datas so we can write a program to do access check?
>> Looking forward for reply.
>> Regards,
>> Lau Lei Cheong
>>
>>
>|||Sorry, I've reviewed application role, but it don't help in this case
because:
1) I need to control access by IP, not by application
2) Some users under the control are application developers who can write
their own application.
But your information is really useful on other area, thanks. :)
"Uri Dimant" <urid@.iscar.co.il> ¼¶¼g©ó¶l¥ó·s»D:%23TPXYYHMGHA.2696@.TK2MSFTNGP14.phx.gbl...
> Well, have a look at APPLICATION ROLE in the BOL
> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
> news:O2MjaNHMGHA.3960@.TK2MSFTNGP09.phx.gbl...
>> Yes, I know I can divide users into groups but that's not the problem.
>> The problem is, as the subject line suggested, I can't find way to limit
>> certain user's access to certain database/table from certain IP.
>> "Uri Dimant" <urid@.iscar.co.il> ¼¶¼g©ó¶l¥ó·s»D:%23aeJm7GMGHA.500@.TK2MSFTNGP15.phx.gbl...
>> Lau
>> How do they (users) access the database? Did you divide them into
>> Groups?
>> You can DENY access on table for the user .
>> In addition , you can specify a hostname in connection string.
>>
>> "Lau Lei Cheong" <leu_lc@.yehoo.com.hk> wrote in message
>> news:uXz12iGMGHA.3856@.TK2MSFTNGP12.phx.gbl...
>> Hello,
>> In MySQL we can set to allow a user to login and access certain
>> table from certain host, is there anything close to that in MSSQL
>> 2000/2005?
>> Actually, we just need to control certain users unable to use
>> the Domain Creditial to access certain databases/tables except in the
>> company's IP, while we need to make sure for certain databases/tables,
>> the client can be accessed anywhere.
>> If not, is there any kind of database connection proxies that we
>> can use to control the connections, or this there any tutorial on how
>> to relay database datas so we can write a program to do access check?
>> Looking forward for reply.
>> Regards,
>> Lau Lei Cheong
>>
>>
>>
>

Monday, February 20, 2012

login options

Thanks, Amy.
I have tried this, but my path does not lead as written, and no paths lead to \login.
I don't have MSSQL.1
At that point in the path I have \80. this will lead to \Replication\DatabaseReconciler\MSSQLServer or
\Replication\MergeReplicationProvide\MSSQLServer
each of these paths contain only a file named "default"
no paths lead to \login
I would prefer to learn to do this in a way that does not involve reinstalling since I have already learned how to do that, and Registry Editor is new to me, so I want to learn about it.
I have been able to connect using NT Authentication now. The DB Manager was just set to SQL login. Still, it has done the login automatically without me adding myself as a user. Is this because the computer already has me set as the administrator with my
windows login? I have never been asked for a password. Is that because I am already logged into windows?
From what I have read, it seems that NT Authentication is preferred for security, and I can still add users by adding their windows user name. Is this correct? Is it more difficult or less precise than using mixed mode with SQL logins?
THanks tons to anyone who replies.
andrew.
-- Amy Yuan [MS] wrote: --
If you don't want to re-install MSDE, you can change the registry key to
enable mixed auth and reset the sa password.
1. use regedit to change HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL Server\MSSQL.1\MSSQLServer\LoginMode to 2 (mixed authentication) and 2.
execute following query: EXEC sp_password NULL, 'yourpassword', 'sa'
Amy
| From: "Greg Low \(MVP\)" <greglow@.lowell.com.au>
| References: <E7B59B91-D84D-4E52-8192-96473E52C339@.microsoft.com>
| Subject: Re: Connecting
| Date: Thu, 8 Apr 2004 00:16:44 +1000
| Lines: 36
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <ew4j2rKHEHA.688@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.msde
| NNTP-Posting-Host: 66.17.222.193
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.msde:13478
| X-Tomcat-NG: microsoft.public.sqlserver.msde
|
| Hi Andrew,
|
| This is because you have not enabled mixed mode authenticaton. As an
| installation option, enter SECURITYMODE=SQL to enable this.
|
| HTH,
|
| --
| Greg Low (MVP)
| MSDE Manager SQL Tools
| www.whitebearconsulting.com
|
| "andrewnichols" <anonymous@.discussions.microsoft.com> wrote in message
| news:E7B59B91-D84D-4E52-8192-96473E52C339@.microsoft.com...
| > Hello All:
| >
| > I have installed MSDE, using Windows Authentication. I can connect to it
| from a Query GUI tool I downloaded, which has an automatic option of NT
| Authentication. It does not ask me for a user, and has the password (too
| long to be my password) already written in. I cannot connect using
anything
| else, including Andrea Montanori's DbaMgr2k. I get a msg:
| >
| > Login failed for user 'sa' Reason: not associated with a trusted SQL
| Server Connection.
| >
| > I am running this on Win XP.
| >
| > I know I can add users for specific databases, but I think I should be
| able to log in with 'sa' and the password. Am i getting my own password
| wrong?
| >
| > Thanks.
| >
| > andrew.
|
|
|
Hi Andrew,
Try edit this key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\LoginMode to
2. I gave you the wrong path last time.
As for your authentication question, you are using Windows Authentication
mode (default). Once you are logged in, it will use your Windows credential
to connect to the database server. Windows auth works the same as SQL
auth. To use SQL auth, you need to have SQL auth enabled and then you can
login as sa (system administrator) or new user. You can add a new SQL auth
user by executing sp_addlogin. SQL auth users are not Windows users. They
can only connect to the databases that they have permission to and do
database operations.
Hope this helps.
Amy
| Thread-Topic: login options
| thread-index: AcQddiDBjvDdBleuQZGSNAVW1yfSkA==
| X-Tomcat-NG: microsoft.public.sqlserver.msde
| From: "=?Utf-8?B?YW5kcmV3bmljaG9scw==?="
<anonymous@.discussions.microsoft.com>
| References: <E7B59B91-D84D-4E52-8192-96473E52C339@.microsoft.com>
<ew4j2rKHEHA.688@.tk2msftngp13.phx.gbl>
<318sKtOHEHA.3704@.cpmsftngxa06.phx.gbl>
| Subject: login options
| Date: Thu, 8 Apr 2004 07:31:06 -0700
| Lines: 92
| Message-ID: <B16333BA-1C45-4885-BB8C-C37F42DC86CD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.msde
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.msde:13508
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.msde
|
| Thanks, Amy.
I have tried this, but my path does not lead as written, and no paths lead
to \login.
I don't have MSSQL.1
At that point in the path I have \80. this will lead to
\Replication\DatabaseReconciler\MSSQLServer or
\Replication\MergeReplicationProvide\MSSQLServer
each of these paths contain only a file named "default"
no paths lead to \login
I would prefer to learn to do this in a way that does not involve
reinstalling since I have already learned how to do that, and Registry
Editor is new to me, so I want to learn about it.
I have been able to connect using NT Authentication now. The DB Manager was
just set to SQL login. Still, it has done the login automatically without
me adding myself as a user. Is this because the computer already has me set
as the administrator with my windows login? I have never been asked for a
password. Is that because I am already logged into windows?
From what I have read, it seems that NT Authentication is preferred for
security, and I can still add users by adding their windows user name. Is
this correct? Is it more difficult or less precise than using mixed mode
with SQL logins?
THanks tons to anyone who replies.
andrew.
-- Amy Yuan [MS] wrote: --
If you don't want to re-install MSDE, you can change the registry key
to
enable mixed auth and reset the sa password.
1. use regedit to change
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL Server\MSSQL.1\MSSQLServer\LoginMode to 2 (mixed authentication)
and 2.
execute following query: EXEC sp_password NULL, 'yourpassword', 'sa'
Amy
| From: "Greg Low \(MVP\)" <greglow@.lowell.com.au>
| References: <E7B59B91-D84D-4E52-8192-96473E52C339@.microsoft.com>
| Subject: Re: Connecting
| Date: Thu, 8 Apr 2004 00:16:44 +1000
| Lines: 36
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <ew4j2rKHEHA.688@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.msde
| NNTP-Posting-Host: 66.17.222.193
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.msde:13478
| X-Tomcat-NG: microsoft.public.sqlserver.msde
|
| Hi Andrew,
|
| This is because you have not enabled mixed mode authenticaton. As an
| installation option, enter SECURITYMODE=SQL to enable this.
|
| HTH,
|
| --
| Greg Low (MVP)
| MSDE Manager SQL Tools
| www.whitebearconsulting.com
|
| "andrewnichols" <anonymous@.discussions.microsoft.com> wrote in
message
| news:E7B59B91-D84D-4E52-8192-96473E52C339@.microsoft.com...
| > Hello All:
| >
| > I have installed MSDE, using Windows Authentication. I can connect
to it
| from a Query GUI tool I downloaded, which has an automatic option of
NT
| Authentication. It does not ask me for a user, and has the password
(too
| long to be my password) already written in. I cannot connect using
anything
| else, including Andrea Montanori's DbaMgr2k. I get a msg:
| >
| > Login failed for user 'sa' Reason: not associated with a trusted
SQL
| Server Connection.
| >
| > I am running this on Win XP.
| >
| > I know I can add users for specific databases, but I think I
should be
| able to log in with 'sa' and the password. Am i getting my own
password
| wrong?
| >
| > Thanks.
| >
| > andrew.
|
|
|
|