Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts

Thursday, March 22, 2012

\Backup directories - remove safely?

I've successfully applied SP4 to an MSDE 2000 installation on a
Windows 2000 Professional system. Now I've notived several \Backup
subdirectories in the "Microsoft SLQ Server" directory. Since I don't
want to go back to any previous version, these subdirectories appear
to be no longer required. May I safely remove them?
Heinz Wehner
(Karlsruhe, Germany)
Hi,
No problems. You can delete that directory.
Thanks
Hari
SQL Server MVP
"Heinz Wehner" <hwehner@.hotmail.com> wrote in message
news:c215e1ppe9k9vqim24ckphf0eukkgr6n5a@.4ax.com...
> I've successfully applied SP4 to an MSDE 2000 installation on a
> Windows 2000 Professional system. Now I've notived several \Backup
> subdirectories in the "Microsoft SLQ Server" directory. Since I don't
> want to go back to any previous version, these subdirectories appear
> to be no longer required. May I safely remove them?
> Heinz Wehner
> (Karlsruhe, Germany)
|||Thanks Hari.

> On Sun, 24 Jul 2005 19:32:03 +0530,
> Hari Prasad <hari_prasad_k@.hotmail.com> wrote:
> Hi,
> No problems. You can delete that directory.
> Thanks
> Hari
> SQL Server MVP
>
> Heinz Wehner <hwehner@.hotmail.com>
> wrote in message news:c215e1ppe9k9vqim24ckphf0eukkgr6n5a@.4ax.com...
> I've successfully applied SP4 to an MSDE 2000 installation on a
> Windows 2000 Professional system. Now I've notived several \Backup
> subdirectories in the "Microsoft SLQ Server" directory. Since I don't
> want to go back to any previous version, these subdirectories appear
> to be no longer required. May I safely remove them?
> Heinz Wehner
> (Karlsruhe, Germany)
sql

Sunday, March 11, 2012

[Shared Memory] ConnectionRead (recv()) ... error

Hi I've got error below when i ran a stored procedure:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionRead (recv())
General network error.
The same error occured in different places in each run.
The SP was running locally in Query Analyzer and there is
no network connection.
Anyone came across this before?
Cheers
Frank
What operating system are you running?
Vikram
"frk" <frk_wang@.hotmail.com> wrote in message
news:1a80001c44e83$e5ea8210$a101280a@.phx.gbl...
> Hi I've got error below when i ran a stored procedure:
> ----
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionRead (recv())
> General network error.
> ----
> The same error occured in different places in each run.
> The SP was running locally in Query Analyzer and there is
> no network connection.
> Anyone came across this before?
> Cheers
> Frank
>
|||A couple of ideas.
1. Check the version of MDAC that you're running. Make sure it's patched
as well.
2. Disable Shared Memory using the SQL Client Network Utility. Then retest.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

[Repost]Login setting by IP range

Hello,
This is a repost. I've posted this last week and haven't got a
workable solution to the problem, given there's no other answering post in a
week, I'd like to try asking again. Sorry for any annoyance made by this.
quote:

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?


The suggestion I've got in my last post includes "APPLICATION ROLE",
but since I need to control the acess BOTH by login name and "IP", and also
some of the user under "access control" are developers who have source code
access to the program we use, the suggestion doesn't solve my problem.
Looking forward for reply.
Regards,
Lau Lei Cheong
The answer is no, SQL Server cannot authorise acces based on IP address.
The OS can allow only access from certain IP addresses using IPSec, you
could then allow access through a SQL login. Effectively, but not
explicitly, granting access to an IP range.
The real question is why? Security based on IP address alone is no security
at all.
"Lau Lei Cheong" wrote:

> Hello,
> This is a repost. I've posted this last week and haven't got a
> workable solution to the problem, given there's no other answering post in a
> week, I'd like to try asking again. Sorry for any annoyance made by this.
>
quote:

> 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?
>

> The suggestion I've got in my last post includes "APPLICATION ROLE",
> but since I need to control the acess BOTH by login name and "IP", and also
> some of the user under "access control" are developers who have source code
> access to the program we use, the suggestion doesn't solve my problem.
> Looking forward for reply.
> Regards,
> Lau Lei Cheong
>
>
|||The reason is that it'd been reported that some company thief have sold
part/all of our customer database to competitor companies, so out boss
decided to restrict full database access within private IP range only.
However, some users/developers do need to access other parts of the
database. So I need to set the access control on "login name + IP" basis
(better with access logging on sensitive data).
It doesn't really matter if someone can tell me I can write a event handler
for SQL2005 that allow me to check the IP when login and set the access
dynamically.
Since I'm the only one except the boss with sa + local admin + domain admin
password, so I can be confident that if this will do, no other people will
be able to break it.
"mulhall" <mulhall@.discussions.microsoft.com> glsD:1FB17D2C-95FD-4719-A22C-FAE26F1D3AF7@.microsoft.com...[vbcol=seagreen]
> The answer is no, SQL Server cannot authorise acces based on IP address.
> The OS can allow only access from certain IP addresses using IPSec, you
> could then allow access through a SQL login. Effectively, but not
> explicitly, granting access to an IP range.
> The real question is why? Security based on IP address alone is no
> security
> at all.
>
> "Lau Lei Cheong" wrote:

Thursday, March 8, 2012

[PRB SQL 2k SP4] SqlMail: fatal exception c0000005

Hello,
on one server that I build to test the SP4, I've got constantly a fatal
exception c0000005 EXCEPTION_ACCESS_VIOLATION, which is due to SqlMail (when
it notifies after a job, linked to a maintenance plan).
I did install this server following the rpocedure for our production server,
which does not experiment this error at all.
I've been unable to locate relevant information even after extensive search.
Any thought about it? Any similar experience somebody?
Thanks,
Emmanuel
PS: the beginning of the crash dump text file is as follows (edited):
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.2039
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is Phoenix ROM BIOS PLUS Version 1.10 A11
Current time is 00:52:46 08/12/05.
1 Intel x86 level 6, 3 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 70%
Total Physical = 1023 MB
Available Physical = 304 MB
Total Page File = 2463 MB
Available Page File = 1424 MB
Total Virtual = 2047 MB
Available Virtual = 931 MB
*Stack Dump being sent to e:\Program Files\Microsoft SQL
Server\MSSQL\log\SQLDu
mp0014.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 08/12/05 00:52:46 spid 59
*
* Exception Address = 77F8206B (RtlEnterCriticalSection + 0000000B Line
0+000
00000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 0864FF90
* Input Buffer 1178 bytes -
* DECLARE @.msg varchar(255) SELECT @.msg = 'The attached report is a summ
* ary of the automated maintenance carried out for plan ' + datename(dw
* , getdate()) + ' ' + convert(varchar, datepart(dd, getdate())) + ' '
* + datename(mm, getdate()) + ' ' + convert(varchar, datepart(yy, ge
* tdate())) + ':' + CHAR(13) EXEC xp_sendmail @.recipients = 'emmanue
* l@.mycompany.com', @.subject = 'SQL Server DB Maintenance Report
* - SQL-SP4\User Databases (Success)', @.message = @.msg, @.attachments
* = 'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\User Databases4_2005
* 08120045.txt'
*
AV normally means a bug in sqlserver. You might want to contact PSS. This
call should not be charged.
http://support.microsoft.com/oas/def...92&gprid=36498
-oj
"Emmanuel" <Emmanuel@.discussions.microsoft.com> wrote in message
news:291AF677-3E24-49C7-8354-D3675363A55E@.microsoft.com...
> Hello,
> on one server that I build to test the SP4, I've got constantly a fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION, which is due to SqlMail
> (when
> it notifies after a job, linked to a maintenance plan).
> I did install this server following the rpocedure for our production
> server,
> which does not experiment this error at all.
> I've been unable to locate relevant information even after extensive
> search.
> Any thought about it? Any similar experience somebody?
> Thanks,
> Emmanuel
> PS: the beginning of the crash dump text file is as follows (edited):
> ================================================== ===================
> BugCheck Dump
> ================================================== ===================
>
> This file is generated by Microsoft SQL Server 8.00.2039
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
>
> Computer type is AT/AT COMPATIBLE.
> Bios Version is Phoenix ROM BIOS PLUS Version 1.10 A11
> Current time is 00:52:46 08/12/05.
> 1 Intel x86 level 6, 3 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> MemoryLoad = 70%
> Total Physical = 1023 MB
> Available Physical = 304 MB
> Total Page File = 2463 MB
> Available Page File = 1424 MB
> Total Virtual = 2047 MB
> Available Virtual = 931 MB
> *Stack Dump being sent to e:\Program Files\Microsoft SQL
> Server\MSSQL\log\SQLDu
> mp0014.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 08/12/05 00:52:46 spid 59
> *
> * Exception Address = 77F8206B (RtlEnterCriticalSection + 0000000B Line
> 0+000
> 00000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 0864FF90
> * Input Buffer 1178 bytes -
> * DECLARE @.msg varchar(255) SELECT @.msg = 'The attached report is a
> summ
> * ary of the automated maintenance carried out for plan ' +
> datename(dw
> * , getdate()) + ' ' + convert(varchar, datepart(dd, getdate())) + ' '
> * + datename(mm, getdate()) + ' ' + convert(varchar, datepart(yy,
> ge
> * tdate())) + ':' + CHAR(13) EXEC xp_sendmail @.recipients =
> 'emmanue
> * l@.mycompany.com', @.subject = 'SQL Server DB Maintenance Report
> * - SQL-SP4\User Databases (Success)', @.message = @.msg,
> @.attachments
> * = 'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\User
> Databases4_2005
> * 08120045.txt'
> *
>

Sunday, February 19, 2012

[DBNETLIB]ConnectionWrite (send()) error

I've searched trying to find help for "[Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send())", but couldn't find any solutions
(and precious few leads). I think I've figured out the problem, and wanted
to post it in case anyone else was looking also.
My enabled protocols in the SQL Server Client Network Utility, Named Pipes
and TCP/IP, were set to where TCP/IP was first in the list. I changed it to
where Named Pipes was at the top of the list, and my query (from my
workstation to the server) now runs instead of getting the error message
shown above.
Does anyone have anything else to add to this that might further clairfy the
issue?
Thanks,
Mike
TCP protocol is failing to connect...is the SQL Server listening on that
protocol? Look in the current SQL Server ERRORLOG for a line similar to:
SQL Server listening on TCP, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@.discussions.microsoft.com> wrote in message
news:BDB8E5F9-D615-41BE-B07A-4F71F4AD053F@.microsoft.com...
> I've searched trying to find help for "[Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (send())", but couldn't find any
> solutions
> (and precious few leads). I think I've figured out the problem, and
> wanted
> to post it in case anyone else was looking also.
> My enabled protocols in the SQL Server Client Network Utility, Named Pipes
> and TCP/IP, were set to where TCP/IP was first in the list. I changed it
> to
> where Named Pipes was at the top of the list, and my query (from my
> workstation to the server) now runs instead of getting the error message
> shown above.
> Does anyone have anything else to add to this that might further clairfy
> the
> issue?
> Thanks,
> Mike
|||Two lines:
SQL server listening on n.n.n.n: 14yy.
SQL server listening on x.x.x.x: 14yy.
Replaced the actual numbers with n's, x's and y's, of course.
Mike
|||Sorry, I missed a line:
SQL server listening on TCP, Shared Memory, Named Pipes.
It's after the other two lines I mentioned earlier.
Mike
|||At least we know that its trying to listen
From your client machine, assuming you have Query Analyzer, try to make a
new connection. In the servername box, instead of SERVERNAME use
tcp:SERVERNAME, 1433
if that fails, try:
tcp:x.x.x.x, 14yy (replace x with your external ip, and 14yy with the
correct port)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@.discussions.microsoft.com> wrote in message
news:9D5AC8FF-7CF9-4BC0-9B12-13206F8CE225@.microsoft.com...
> Sorry, I missed a line:
> SQL server listening on TCP, Shared Memory, Named Pipes.
> It's after the other two lines I mentioned earlier.
> Mike
>

Monday, February 13, 2012

[*-)]how to delete all columns except one column for the corresponding column name......?

hi friends,

i've a table with (columns) username, content,data,......... i need to delete all column names(i.e.,content,data,......) except username for the specified username. eg: consider username=mahendran. i've to delete the values in the content,data,............for the username=mahendran. but username should exist.

how to do that?pls help me.....Confused

Use the following

DataTable.Columns.Remove takes the column name or column reference as argument.

To remove column using it's index, you can use DataTable.Columns.RemoveAt method.

|||

hi farooq,

i need the SQL query for delete command. i wrote

delete [contact],[title] from <table_name> where userid=<user_id>

but it is not working.what is the correct format?

|||

If you want to change your table structure, you useAlter Table along withDrop Column instead of Delete which is for your records. Here is a sample:

ALTERTABLE yourTable

DROPCOLUMN col2, col3

You can find more information about SQL DML(SQL Data Manipulation Language) and DDL(SQL Data Definition Language) if you are interested about the topic.