Monday, March 26, 2012
NOP in sysprocesses (cmd column)
(SQL2K) noticed this when a stored procedure was running . .. I could not
find anything about this cmd (relating to SQL) on the internet . . .however
there were some references to NOP in c# and .NET programming
Thanks for your help
Olu Adedeji
Baysignia Systems
In other areas NOP means "No Operation", but I do not know if that is true
here..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:ACD1A5E9-503C-41D7-9F6D-9C8D2ABA7EFD@.microsoft.com...
> Can somebody please tell me what 'NOP' is in the cmd column of
sysprocesses
> (SQL2K) noticed this when a stored procedure was running . .. I could not
> find anything about this cmd (relating to SQL) on the internet . .
..however
> there were some references to NOP in c# and .NET programming
> Thanks for your help
>
> Olu Adedeji
> Baysignia Systems
|||Thanks Wayne
"Wayne Snyder" wrote:
> In other areas NOP means "No Operation", but I do not know if that is true
> here..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
> news:ACD1A5E9-503C-41D7-9F6D-9C8D2ABA7EFD@.microsoft.com...
> sysprocesses
> ..however
>
>
NOP in sysprocesses (cmd column)
(SQL2K) noticed this when a stored procedure was running . .. I could not
find anything about this cmd (relating to SQL) on the internet . . .however
there were some references to NOP in c# and .NET programming
Thanks for your help
Olu Adedeji
Baysignia SystemsIn other areas NOP means "No Operation", but I do not know if that is true
here..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:ACD1A5E9-503C-41D7-9F6D-9C8D2ABA7EFD@.microsoft.com...
> Can somebody please tell me what 'NOP' is in the cmd column of
sysprocesses
> (SQL2K) noticed this when a stored procedure was running . .. I could not
> find anything about this cmd (relating to SQL) on the internet . .
.however
> there were some references to NOP in c# and .NET programming
> Thanks for your help
>
> Olu Adedeji
> Baysignia Systems|||Thanks Wayne
"Wayne Snyder" wrote:
> In other areas NOP means "No Operation", but I do not know if that is true
> here..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
> news:ACD1A5E9-503C-41D7-9F6D-9C8D2ABA7EFD@.microsoft.com...
> sysprocesses
> ..however
>
>
NOP in sysprocesses (cmd column)
(SQL2K) noticed this when a stored procedure was running . .. I could not
find anything about this cmd (relating to SQL) on the internet . . .however
there were some references to NOP in c# and .NET programming
Thanks for your help
Olu Adedeji
Baysignia SystemsIn other areas NOP means "No Operation", but I do not know if that is true
here..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:ACD1A5E9-503C-41D7-9F6D-9C8D2ABA7EFD@.microsoft.com...
> Can somebody please tell me what 'NOP' is in the cmd column of
sysprocesses
> (SQL2K) noticed this when a stored procedure was running . .. I could not
> find anything about this cmd (relating to SQL) on the internet . .
.however
> there were some references to NOP in c# and .NET programming
> Thanks for your help
>
> Olu Adedeji
> Baysignia Systems|||Thanks Wayne
"Wayne Snyder" wrote:
> In other areas NOP means "No Operation", but I do not know if that is true
> here..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
> news:ACD1A5E9-503C-41D7-9F6D-9C8D2ABA7EFD@.microsoft.com...
> > Can somebody please tell me what 'NOP' is in the cmd column of
> sysprocesses
> > (SQL2K) noticed this when a stored procedure was running . .. I could not
> > find anything about this cmd (relating to SQL) on the internet . .
> ..however
> > there were some references to NOP in c# and .NET programming
> >
> > Thanks for your help
> >
> >
> > Olu Adedeji
> > Baysignia Systems
>
>sql
Noob to VWD 2005 - Insert from textbox into SQL DB
I have followed all the tutorials and I think I have a pretty good grasp on how to get info from the SQL database running on my machine in the App Data directory. My question is simple and probably the answer is nested in the 148 pages of this very informative forum.
How do I take the 15 textbox fields worth of data and insert them into the SQL db? I am pretty familiar with general sql concepts (mysql, mssql, postgresql), but I have only been in this IDE for about a week now and I need to get my project up and running quickly. I am just unfamiliar with VB in general, but I do understand the object.method concept.
I gathered that I need to make the insert statement part of the button click "event". I cannot find any good "starter" documentation on getting this process to work. I understand the grid and form and detail view really well and have tested my 2nd app with success, but it requires the db to be populated by a web front end. I have read a few MSDN links but they are not helping much, they just keep linking me back to grid and detal and form views.
Help? Please? Pretty Please?
- Chris
roninuta:
I have followed all the tutorials and I think I have a pretty good grasp on how to get info from the SQL database running on my machine in the App Data directory. My question is simple and probably the answer is nested in the 148 pages of this very informative forum.
How do I take the 15 textbox fields worth of data and insert them into the SQL db? I am pretty familiar with general sql concepts (mysql, mssql, postgresql), but I have only been in this IDE for about a week now and I need to get my project up and running quickly. I am just unfamiliar with VB in general, but I do understand the object.method concept.
I gathered that I need to make the insert statement part of the button click "event". I cannot find any good "starter" documentation on getting this process to work. I understand the grid and form and detail view really well and have tested my 2nd app with success, but it requires the db to be populated by a web front end. I have read a few MSDN links but they are not helping much, they just keep linking me back to grid and detal and form views.
Help? Please? Pretty Please?
- Chris
This link...
http://www.WebLogicArts.com/DemoSqlServerDatabase01.aspx
...is a working sample with source code that shows one simple way to CreateOne/ UpdateOne/ DeleteOne/ RetrieveOne/ RetrieveAll using ASP.NET and SQL Sever 2000.
HTH.
Thank you.
-- Mark Kamoski
|||
Ok, there are two very simple ways you can do this.
1) Using the SQLDataSource object and after creating the connection using the GUI. You can find the SqlDataSource control in the toolbox. Although easy to use I don't like it too much, prefer writing SLQ statements on my own allows for more flexibility. However, to use the SqlDataSource object you are forced to create an SQL statement using the GUI, but this can be countermanded. So what I do is use the SQLDataSource object's SelectCommand and use its SelectCommand method to write my own SQL statement. Basically SQLDataSource1.SelectCommand = "Select * from whatever". To include textboxes, like in a search your SQL statement should look like this
"Select * from Table WHERE Table.Column = '" & textbox1.text & "'"
You can extrapolate to Insert and Update.
2) Another way of using SQL in VWD2005E is to call ADODB objects. I find this the best method to do inserts and such. First you have to make a reference to the DLL, to do this you go to Website->Add Reference click on the COM tab and find Microsoft ActiveX Data Objects, pick one and click OK. To use ADODB you first declare it then set the connection string (I usually copy it from the SQLDataSource Object), and execute your sql command.
Dim Conn as ADODB.Connection
Conn.ConnectionString = "Provider..."
Conn.Execute(InsertCommand)
Holler at me for any clarifications
|||I forgot, for 2 after Dim Conn as ADODB.Connection you have to put Conn = new ADODB.Connection|||You can try this one at your button submit click event using text1 as your control.
Dim datasourceAsNew SqlDataSource()
datasource.ConnectionString = ConfigurationManager.ConnectionStrings("YourConnectionString").ToString()
datasource.InsertCommandType = SqlDataSourceCommandType.Text
datasource.InsertCommand ="INSERT INTO YourTable (YourTableField) VALUES (@.YourTableField)"
datasource.InsertParameters.Add(
"YourTableField", Text1.Text)
|||You can try this one at your button submit click event using text1 as your control.
Dim datasourceAsNew SqlDataSource()
datasource.ConnectionString = ConfigurationManager.ConnectionStrings("YourConnectionString").ToString()
datasource.InsertCommandType = SqlDataSourceCommandType.Text
datasource.InsertCommand ="INSERT INTO YourTable (YourTableField) VALUES (@.YourTableField)"
datasource.InsertParameters.Add(
"YourTableField", Text1.Text)
|||
this last example was awesome. It was implistic and really helped. I understand much more now. I new that I was going to have to use the parameters.add functionality. I think I am messing up on my connection string though and it is probably just not set correctly. I get an unhandled exception here is the error message:
System.NullReferenceException was unhandled by user code
Message="Object reference not set to an instance of an object."
Source="App_Web_1cnoj4u7"
StackTrace:
at _Default.SendForm_Click(Object sender, EventArgs e) in D:\Documents and Settings\ronin\My Documents\Visual Studio 2005\WebSites\ADRequest\Default.aspx.vb:line 20
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Here is line 20 - the connection string:
datasource.ConnectionString = ConfigurationManager.ConnectionStrings("Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\adrequest.mdf;Integrated Security=True;User Instance=True").ToString()
I am using a built in SQLDB file that comes with VWD2005E, and the file is called adrequest.mdf, what am I missing here.
TIA,
Chris
|||
You are wrong with declaring with your connection string. Your connection string name must be like in my part:
phiwugdatasource.ConnectionString = ConfigurationManager.ConnectionStrings("phiwugConnectionString1").ToString()
To find the name of your connection string, try to do this, add a blank web form on your project, go to database explorer and go to the table of your database, click the table and drag and drop this to the blank web form. You will see that it will create a table on your blank web form and a control name SqlDataSource - SqlDataSource1. Click it then click the arrow next to it and you will see Configure Data Source and click it. Next a wizard will appear. The connection string name that will appear on the drop down list box is the connection string name you will write on it.
Be sure to mark as answer on the post you think that answers your question so that the poster will have credit for it. Don't hesitate to inquire.
Best regards,
|||
This may be a silly question but given this code:
Dim datasource As New SqlDataSource()
datasource.ConnectionString = ConfigurationManager.ConnectionStrings("connection2").ToString()
datasource.InsertCommandType = SqlDataSourceCommandType.Text
datasource.InsertCommand = "INSERT INTO ticket (sr) VALUES (@.srnum)"
datasource.InsertParameters.Add("srnum", TextBoxSRNum.Text)
is the data actually being posted to the DB or is the insert statement just being setup? Do I need to actually execute the statement through another line?
TIA - Chris
Nevermind
I just added datasurce.Insert() to the end of the event - that fixed it - thanks everyone for helping out!
- Chris
|||You can even add this one and put your datasource.insert() on a structured error handling procedure:
Dim
rowsaffectedAsIntegerTryrowsaffected = datasource.Insert()
Catch exAs Exception'TODO: Probably write a windows error log
Server.Transfer(
"error.aspx") <--create a web form for error messages/siteFinallydatasource =
NothingEndTry
If rowsaffected <> 1Then
Server.Transfer(
"error.aspx") <--create a web form for error messages/siteElseServer.Transfer(
"success.aspx") <--create a web form for success messages/siteEndIf
noob to SSIS package configure and deploy
I am fairly new to SSIS, I got my package running fine in my development environment with the connection managers (connecting to 3 databases on the same server, with username and password, not Integrated security) and all.
The problem comes in when i want to deploy my package or execute it outside of the development environment.
When I execute the .dtsx file in my project it brings up the Execute Package Utility and I just click Execute, thinking it should work, but not, any ideas?
So I read some of the forums and got looking into the configuration file, suppose that it does not carry the connection manager settings thru, but dam that still doesn't work for me?
The whole idea is that I will be executing the package from my C# code, so does my package have to be just on the server in a folder or does it have to be installed in the db? which is best?
Hope anyone can help me!!
Thanks
Jamie
If the error you are getting is a failure to connect to the database, the problem is in the password not being stored in the package. If you search the forum for connection strings and configurations, you'll see a number of different solutions to this.
If that's not the problem, please include the error message that you are receiving.
Friday, March 23, 2012
Noob Question: How to get Reporting Services
I'm evaluating using SQL for running the back end of a medium sized business. We're looking at using reporting services to cull information from several dbs, some of which are owned by partner companies who may or may not be running SQL 2005.
What I'm trying to figure out is; can I just go online and download reporting services somewhere for pre 2005 sql installations? Does it cost anything? Browsing the MS download pages has given me no results thus far.
Thanks much
I found my own answer - I can get the functionality I need through the redistributable here: http://www.microsoft.com/downloads/details.aspx?familyid=8A166CAC-758D-45C8-B637-DD7726E61367&displaylang=en#Overview
Thanks
Non-Sysadmins Running xp_cmdshell
non-sysadmins and I am already taking those issues into
account. I have a question about a problem I am having
letting users run this extended stored procedure.
I have created an Active Directory group and added it to
our SQL Server as a login and made it a user on the master
database. The only thing this user has authority to do is
execute xp_cmdshell. I made one of our users a member of
this AD group and had him execute a stored procedure that
executes the xp_cmdshell procedure. (We are sure he has
execute permissions on the stored procedure that executes
xp_cmdshell.)
When he runs the stored procedure he gets an error that
access is denied.
Next I removed him from the AD group and added a login for
him, with Windows authentication, and added him as a user
to the master database, then I granted execute permissions
on xp_cmdshell. When he runs the stored procedure now, it
executes the xp_cmdshell procedure properly.
Is there some rule about how permissions can be granted to
xp_cmdshell? The only difference between my two scenarios
is in one case he is executing with a connection directly
based on his personal AD account and in the other case,
the permissions are set via an AD group.
Thanks for any help.Hi Jason,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
From you description, in your system, you have a login account in a group.
In the SQL Server, you set it to Windows authentication and you grant the
execute permission of 'xp_cmdshell' to the user, but it failed with an
error message 'access is denied', while when you grant the execute
permission of the 'xp_cmdshell' to the group the user is belong in, no
message with it. You wonder if there is any rules for these, right? If I
misunderstood you, pleae feel free to let me know.
Well, I create a user 'test1' and 'test2' on my system belongs to 'testing
group', in my SQL Server Enterprise Manager, I grant the permission of
execute 'xp_cmdshell' to 'test1' and 'testing group'. Then I login with
account 'test1' and 'test2', both could execute " xp_cmdshell 'dir c:' ".
So, you could grant the permissions to either user or group. Well, as we
always emphasize, it strongly recommend that it should be run by limited,
system administrator account for security concern.
Could you tell me which statement you are running in the xp_cmdshell? When
this user login in you system(not sql server), could he run the same
statements in command prompt? I am looking forward to your information.
Thanks!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Two things. One, your understanding is backwards. When I
granted rights to individuals it worked. When I granted
rights to the group it did not work.
More importantly, however, IT STARTED WORKING TODAY! The
setup is still exactly as it was when I started having
this problem. I did make some changes about removing
permissions and re-adding permissions trying to make it
work but it ultimately went back to how it was in the
beginning.
Anyway, thanks for the responses.
quote:
>--Original Message--
>Hi Jason,
>Thank you for using MSDN Newsgroup! It's my pleasure to
assist you with
quote:
>your issue.
>From you description, in your system, you have a login
account in a group.
quote:
>In the SQL Server, you set it to Windows authentication
and you grant the
quote:
>execute permission of 'xp_cmdshell' to the user, but it
failed with an
quote:
>error message 'access is denied', while when you grant
the execute
quote:
>permission of the 'xp_cmdshell' to the group the user is
belong in, no
quote:
>message with it. You wonder if there is any rules for
these, right? If I
quote:
>misunderstood you, pleae feel free to let me know.
>Well, I create a user 'test1' and 'test2' on my system
belongs to 'testing
quote:
>group', in my SQL Server Enterprise Manager, I grant the
permission of
quote:
>execute 'xp_cmdshell' to 'test1' and 'testing group'.
Then I login with
quote:
>account 'test1' and 'test2', both could execute "
xp_cmdshell 'dir c:' ".
quote:
>So, you could grant the permissions to either user or
group. Well, as we
quote:
>always emphasize, it strongly recommend that it should be
run by limited,
quote:
>system administrator account for security concern.
>Could you tell me which statement you are running in the
xp_cmdshell? When
quote:
>this user login in you system(not sql server), could he
run the same
quote:
>statements in command prompt? I am looking forward to
your information.
quote:
>Thanks!
>Best regards
>Baisong Wei
>Microsoft Online Support
>----
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
quote:|||Hi Jason,
>Please reply to newsgroups only. Thanks.
>.
>
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
Sorry for the misunderstanding for the first time. It is good to here that
you have solved the problem. Here I just want to add some information about
the logins and users in the SQL Server 2000. Windows accounts (users or
groups) must be granted permissions to connect to an instance of Microsoft
SQL Server? before they can access a database. You could grant the
permissions to connect the SQL Server by expand a server group, and then
expand a server, then expand Security, right-click Logins, and then click
New Login. In the Name box, enter the Windows account (in the form
DOMAIN\User) to be granted access to SQL Server. Under Authentication,
click Windows Authentication. Then, in a database, you add them as database
user or add in a database roles. Then you could grant, deny and revoke the
permissions to operations such as select, insert, update, execute a stored
procedure on the database objects to the database users or apply this on a
specified role.
Again, glad to hear that you solved your problem and if you have any
questions about SQL server, please feel free to post message here and I am
ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Non-Sysadmins Running xp_cmdshell
non-sysadmins and I am already taking those issues into
account. I have a question about a problem I am having
letting users run this extended stored procedure.
I have created an Active Directory group and added it to
our SQL Server as a login and made it a user on the master
database. The only thing this user has authority to do is
execute xp_cmdshell. I made one of our users a member of
this AD group and had him execute a stored procedure that
executes the xp_cmdshell procedure. (We are sure he has
execute permissions on the stored procedure that executes
xp_cmdshell.)
When he runs the stored procedure he gets an error that
access is denied.
Next I removed him from the AD group and added a login for
him, with Windows authentication, and added him as a user
to the master database, then I granted execute permissions
on xp_cmdshell. When he runs the stored procedure now, it
executes the xp_cmdshell procedure properly.
Is there some rule about how permissions can be granted to
xp_cmdshell? The only difference between my two scenarios
is in one case he is executing with a connection directly
based on his personal AD account and in the other case,
the permissions are set via an AD group.
Thanks for any help.In EM RClick SQL Server Agent/ props/ job system/ uncheck
only users with Sysadmin bla bla. Put in a valid Adimn
Login and Password. You never want to grant direct access
to xp_cmdshell. Users can do lots more than your intended
proc if you do this.
>--Original Message--
>I know about the security risks of running xp_cmdshell by
>non-sysadmins and I am already taking those issues into
>account. I have a question about a problem I am having
>letting users run this extended stored procedure.
>I have created an Active Directory group and added it to
>our SQL Server as a login and made it a user on the
master
>database. The only thing this user has authority to do
is
>execute xp_cmdshell. I made one of our users a member of
>this AD group and had him execute a stored procedure that
>executes the xp_cmdshell procedure. (We are sure he has
>execute permissions on the stored procedure that executes
>xp_cmdshell.)
>When he runs the stored procedure he gets an error that
>access is denied.
>Next I removed him from the AD group and added a login
for
>him, with Windows authentication, and added him as a user
>to the master database, then I granted execute
permissions
>on xp_cmdshell. When he runs the stored procedure now,
it
>executes the xp_cmdshell procedure properly.
>Is there some rule about how permissions can be granted
to
>xp_cmdshell? The only difference between my two
scenarios
>is in one case he is executing with a connection directly
>based on his personal AD account and in the other case,
>the permissions are set via an AD group.
>Thanks for any help.
>.
>|||Hi Jason,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
From you description, in your system, you have a login account in a group.
In the SQL Server, you set it to Windows authentication and you grant the
execute permission of 'xp_cmdshell' to the user, but it failed with an
error message 'access is denied', while when you grant the execute
permission of the 'xp_cmdshell' to the group the user is belong in, no
message with it. You wonder if there is any rules for these, right? If I
misunderstood you, pleae feel free to let me know.
Well, I create a user 'test1' and 'test2' on my system belongs to 'testing
group', in my SQL Server Enterprise Manager, I grant the permission of
execute 'xp_cmdshell' to 'test1' and 'testing group'. Then I login with
account 'test1' and 'test2', both could execute " xp_cmdshell 'dir c:\' ".
So, you could grant the permissions to either user or group. Well, as we
always emphasize, it strongly recommend that it should be run by limited,
system administrator account for security concern.
Could you tell me which statement you are running in the xp_cmdshell? When
this user login in you system(not sql server), could he run the same
statements in command prompt? I am looking forward to your information.
Thanks!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Two things. One, your understanding is backwards. When I
granted rights to individuals it worked. When I granted
rights to the group it did not work.
More importantly, however, IT STARTED WORKING TODAY! The
setup is still exactly as it was when I started having
this problem. I did make some changes about removing
permissions and re-adding permissions trying to make it
work but it ultimately went back to how it was in the
beginning.
Anyway, thanks for the responses.
>--Original Message--
>Hi Jason,
>Thank you for using MSDN Newsgroup! It's my pleasure to
assist you with
>your issue.
>From you description, in your system, you have a login
account in a group.
>In the SQL Server, you set it to Windows authentication
and you grant the
>execute permission of 'xp_cmdshell' to the user, but it
failed with an
>error message 'access is denied', while when you grant
the execute
>permission of the 'xp_cmdshell' to the group the user is
belong in, no
>message with it. You wonder if there is any rules for
these, right? If I
>misunderstood you, pleae feel free to let me know.
>Well, I create a user 'test1' and 'test2' on my system
belongs to 'testing
>group', in my SQL Server Enterprise Manager, I grant the
permission of
>execute 'xp_cmdshell' to 'test1' and 'testing group'.
Then I login with
>account 'test1' and 'test2', both could execute "
xp_cmdshell 'dir c:\' ".
>So, you could grant the permissions to either user or
group. Well, as we
>always emphasize, it strongly recommend that it should be
run by limited,
>system administrator account for security concern.
>Could you tell me which statement you are running in the
xp_cmdshell? When
>this user login in you system(not sql server), could he
run the same
>statements in command prompt? I am looking forward to
your information.
>Thanks!
>Best regards
>Baisong Wei
>Microsoft Online Support
>----
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
>Please reply to newsgroups only. Thanks.
>.
>|||Hi Jason,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
Sorry for the misunderstanding for the first time. It is good to here that
you have solved the problem. Here I just want to add some information about
the logins and users in the SQL Server 2000. Windows accounts (users or
groups) must be granted permissions to connect to an instance of Microsoft
SQL Server? before they can access a database. You could grant the
permissions to connect the SQL Server by expand a server group, and then
expand a server, then expand Security, right-click Logins, and then click
New Login. In the Name box, enter the Windows account (in the form
DOMAIN\User) to be granted access to SQL Server. Under Authentication,
click Windows Authentication. Then, in a database, you add them as database
user or add in a database roles. Then you could grant, deny and revoke the
permissions to operations such as select, insert, update, execute a stored
procedure on the database objects to the database users or apply this on a
specified role.
Again, glad to hear that you solved your problem and if you have any
questions about SQL server, please feel free to post message here and I am
ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Nonstop datasource connection
Try the data access forum
https://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1
-Jamie
Monday, March 12, 2012
Non-admin Citrix users cannot connect to SQL Server
several Citrix servers. Recently users started getting a message from the
application that there was a catastrophic failure when connecting to SQL
server. This was only happening if the user was not an administrator on the
Citrix server.
I tried connecting to SQL server from Enterprise Manager and Query Analyzer.
If I was logged on as an admin it worked, but if not, it did not work. In
Query Analyzer if I tried to log on to SQL server using a bad password, I got
back a message about bad user or password. When I put in the correct
password (or if using integrated security) the screen briefly acts like it is
connecting but then the entire isqlw program shuts down. Enterprise manager
shuts down when I try to connect to a server. As a non-admin user I am able
to connect using ISQL.exe.
We've checked on rights to the SQL files and everything looks OK. Is there
anything else to check?
Thanks
LehrSJ
Hello there,
I would like to suggest you applied the SQL 2000 SP4 first.
And please let me know the error log in the SQL Server.
This issue may related with some permission of folder. If you use the SQL
Authentication to connect the SQL server, did this issue occur?
Sincerely,
Wei Lu
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.
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
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.
Non sa running jobs?
got sa permission?
Thanks
AlexAlex,
Yes if the user is a member of the SYSADMIN fixed server role. Note however
that membership of this role should be limited as the role enables a user to
do pretty much anything in SQL Server.
HTH
Jerry
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> Is there a way for a user to manage ( run, delete, add ) a job if he has
> not
> got sa permission?
> Thanks
> Alex|||Thanks for this. But the problem we have is SOX compliance !. Us dba's have
been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
The side effect of this is that there are loads of admin tasks we cannot now
do.
Alex
"Jerry Spivey" wrote:
> Alex,
> Yes if the user is a member of the SYSADMIN fixed server role. Note howev
er
> that membership of this role should be limited as the role enables a user
to
> do pretty much anything in SQL Server.
> HTH
> Jerry
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>
>|||Hmmm...that doesn't sound right. You're a DBA but you're not a member of
the SYSADMIN fixed server role? How can you do your job?
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...[vbcol=seagreen]
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>|||Since we don't want SA running jobs (or being in the Sysadmin group), I set
up a login with win authent, sysadmin to run jobs. No one needs the passwor
d
to use; just set this user up as the proxy account (under agent properties,
job system), and if any job owner is not a sysadmin, it defaults to this guy
.
HTH, mary
"Alex" wrote:
[vbcol=seagreen]
> Thanks for this. But the problem we have is SOX compliance !. Us dba's hav
e
> been stripped off sa/SYSADMIN fixed role permission so we can't modify dat
a.
> The side effect of this is that there are loads of admin tasks we cannot n
ow
> do.
> Alex
>
> "Jerry Spivey" wrote:
>|||Yes, try telling this to the auditors!
We are very frustrated. If we need to add a job we will need to apply for
permission to log in as sa, after going through multilevel of sign off from
the senior management - all for running a SQL Profile, or creating
maintenance plan !!
and then all actions will be be logged as well.
Alex
"Jerry Spivey" wrote:
> Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> the SYSADMIN fixed server role? How can you do your job?
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
>
>|||Curious, if the is a reason to suddenly restore a db in the middle of the da
y
so production activities can resume, is the same process to log in as SA
required?
ChrisR
"Alex" wrote:
[vbcol=seagreen]
> Yes, try telling this to the auditors!
> We are very frustrated. If we need to add a job we will need to apply for
> permission to log in as sa, after going through multilevel of sign off fro
m
> the senior management - all for running a SQL Profile, or creating
> maintenance plan !!
> and then all actions will be be logged as well.
> Alex
> "Jerry Spivey" wrote:
>|||I don't recall anything in SOX that states that a DBA can not have sa
rights. Someone is taking the wording way beyond it's intent. SQL2005 will
have roles specifically for this but in 2000 it is not that easy.
Andrew J. Kelly SQL MVP
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...[vbcol=seagreen]
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>|||Thanks Mary. This could be the escape route we have been looking for!
Alex
"Mary" wrote:
[vbcol=seagreen]
> Since we don't want SA running jobs (or being in the Sysadmin group), I se
t
> up a login with win authent, sysadmin to run jobs. No one needs the passw
ord
> to use; just set this user up as the proxy account (under agent properties
,
> job system), and if any job owner is not a sysadmin, it defaults to this g
uy.
> HTH, mary
> "Alex" wrote:
>|||Andrew
We can run sa tasks, but we need authorisation every time we need to. its
like working with one of your hands tied.
Alex
"Andrew J. Kelly" wrote:
> I don't recall anything in SOX that states that a DBA can not have sa
> rights. Someone is taking the wording way beyond it's intent. SQL2005 wi
ll
> have roles specifically for this but in 2000 it is not that easy.
> --
> Andrew J. Kelly SQL MVP
>
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
>
>
Non sa running jobs?
got sa permission?
Thanks
AlexAlex,
Yes if the user is a member of the SYSADMIN fixed server role. Note however
that membership of this role should be limited as the role enables a user to
do pretty much anything in SQL Server.
HTH
Jerry
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> Is there a way for a user to manage ( run, delete, add ) a job if he has
> not
> got sa permission?
> Thanks
> Alex|||Thanks for this. But the problem we have is SOX compliance !. Us dba's have
been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
The side effect of this is that there are loads of admin tasks we cannot now
do.
Alex
"Jerry Spivey" wrote:
> Alex,
> Yes if the user is a member of the SYSADMIN fixed server role. Note however
> that membership of this role should be limited as the role enables a user to
> do pretty much anything in SQL Server.
> HTH
> Jerry
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > not
> > got sa permission?
> >
> > Thanks
> >
> > Alex
>
>|||Hmmm...that doesn't sound right. You're a DBA but you're not a member of
the SYSADMIN fixed server role? How can you do your job?
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>> Alex,
>> Yes if the user is a member of the SYSADMIN fixed server role. Note
>> however
>> that membership of this role should be limited as the role enables a user
>> to
>> do pretty much anything in SQL Server.
>> HTH
>> Jerry
>> "Alex" <Alex@.discussions.microsoft.com> wrote in message
>> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>> > Is there a way for a user to manage ( run, delete, add ) a job if he
>> > has
>> > not
>> > got sa permission?
>> >
>> > Thanks
>> >
>> > Alex
>>|||Since we don't want SA running jobs (or being in the Sysadmin group), I set
up a login with win authent, sysadmin to run jobs. No one needs the password
to use; just set this user up as the proxy account (under agent properties,
job system), and if any job owner is not a sysadmin, it defaults to this guy.
HTH, mary
"Alex" wrote:
> Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> The side effect of this is that there are loads of admin tasks we cannot now
> do.
> Alex
>
> "Jerry Spivey" wrote:
> > Alex,
> >
> > Yes if the user is a member of the SYSADMIN fixed server role. Note however
> > that membership of this role should be limited as the role enables a user to
> > do pretty much anything in SQL Server.
> >
> > HTH
> >
> > Jerry
> > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > > not
> > > got sa permission?
> > >
> > > Thanks
> > >
> > > Alex
> >
> >
> >|||Yes, try telling this to the auditors!
We are very frustrated. If we need to add a job we will need to apply for
permission to log in as sa, after going through multilevel of sign off from
the senior management - all for running a SQL Profile, or creating
maintenance plan !!
and then all actions will be be logged as well.
Alex
"Jerry Spivey" wrote:
> Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> the SYSADMIN fixed server role? How can you do your job?
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > data.
> > The side effect of this is that there are loads of admin tasks we cannot
> > now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Alex,
> >>
> >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> >> however
> >> that membership of this role should be limited as the role enables a user
> >> to
> >> do pretty much anything in SQL Server.
> >>
> >> HTH
> >>
> >> Jerry
> >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> >> > has
> >> > not
> >> > got sa permission?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >>
> >>
> >>
>
>|||Curious, if the is a reason to suddenly restore a db in the middle of the day
so production activities can resume, is the same process to log in as SA
required?
--
ChrisR
"Alex" wrote:
> Yes, try telling this to the auditors!
> We are very frustrated. If we need to add a job we will need to apply for
> permission to log in as sa, after going through multilevel of sign off from
> the senior management - all for running a SQL Profile, or creating
> maintenance plan !!
> and then all actions will be be logged as well.
> Alex
> "Jerry Spivey" wrote:
> > Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> > the SYSADMIN fixed server role? How can you do your job?
> > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > > have
> > > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > > data.
> > > The side effect of this is that there are loads of admin tasks we cannot
> > > now
> > > do.
> > >
> > > Alex
> > >
> > >
> > > "Jerry Spivey" wrote:
> > >
> > >> Alex,
> > >>
> > >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> > >> however
> > >> that membership of this role should be limited as the role enables a user
> > >> to
> > >> do pretty much anything in SQL Server.
> > >>
> > >> HTH
> > >>
> > >> Jerry
> > >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> > >> > has
> > >> > not
> > >> > got sa permission?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Alex
> > >>
> > >>
> > >>
> >
> >
> >|||I don't recall anything in SOX that states that a DBA can not have sa
rights. Someone is taking the wording way beyond it's intent. SQL2005 will
have roles specifically for this but in 2000 it is not that easy.
--
Andrew J. Kelly SQL MVP
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>> Alex,
>> Yes if the user is a member of the SYSADMIN fixed server role. Note
>> however
>> that membership of this role should be limited as the role enables a user
>> to
>> do pretty much anything in SQL Server.
>> HTH
>> Jerry
>> "Alex" <Alex@.discussions.microsoft.com> wrote in message
>> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>> > Is there a way for a user to manage ( run, delete, add ) a job if he
>> > has
>> > not
>> > got sa permission?
>> >
>> > Thanks
>> >
>> > Alex
>>|||Thanks Mary. This could be the escape route we have been looking for!
Alex
"Mary" wrote:
> Since we don't want SA running jobs (or being in the Sysadmin group), I set
> up a login with win authent, sysadmin to run jobs. No one needs the password
> to use; just set this user up as the proxy account (under agent properties,
> job system), and if any job owner is not a sysadmin, it defaults to this guy.
> HTH, mary
> "Alex" wrote:
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> > The side effect of this is that there are loads of admin tasks we cannot now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> > > Alex,
> > >
> > > Yes if the user is a member of the SYSADMIN fixed server role. Note however
> > > that membership of this role should be limited as the role enables a user to
> > > do pretty much anything in SQL Server.
> > >
> > > HTH
> > >
> > > Jerry
> > > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > > news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > > > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > > > not
> > > > got sa permission?
> > > >
> > > > Thanks
> > > >
> > > > Alex
> > >
> > >
> > >|||Andrew
We can run sa tasks, but we need authorisation every time we need to. its
like working with one of your hands tied.
Alex
"Andrew J. Kelly" wrote:
> I don't recall anything in SOX that states that a DBA can not have sa
> rights. Someone is taking the wording way beyond it's intent. SQL2005 will
> have roles specifically for this but in 2000 it is not that easy.
> --
> Andrew J. Kelly SQL MVP
>
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > data.
> > The side effect of this is that there are loads of admin tasks we cannot
> > now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Alex,
> >>
> >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> >> however
> >> that membership of this role should be limited as the role enables a user
> >> to
> >> do pretty much anything in SQL Server.
> >>
> >> HTH
> >>
> >> Jerry
> >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> >> > has
> >> > not
> >> > got sa permission?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >>
> >>
> >>
>
>
Non sa running jobs?
got sa permission?
Thanks
Alex
Alex,
Yes if the user is a member of the SYSADMIN fixed server role. Note however
that membership of this role should be limited as the role enables a user to
do pretty much anything in SQL Server.
HTH
Jerry
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> Is there a way for a user to manage ( run, delete, add ) a job if he has
> not
> got sa permission?
> Thanks
> Alex
|||Thanks for this. But the problem we have is SOX compliance !. Us dba's have
been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
The side effect of this is that there are loads of admin tasks we cannot now
do.
Alex
"Jerry Spivey" wrote:
> Alex,
> Yes if the user is a member of the SYSADMIN fixed server role. Note however
> that membership of this role should be limited as the role enables a user to
> do pretty much anything in SQL Server.
> HTH
> Jerry
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>
>
|||Hmmm...that doesn't sound right. You're a DBA but you're not a member of
the SYSADMIN fixed server role? How can you do your job?
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...[vbcol=seagreen]
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
|||Since we don't want SA running jobs (or being in the Sysadmin group), I set
up a login with win authent, sysadmin to run jobs. No one needs the password
to use; just set this user up as the proxy account (under agent properties,
job system), and if any job owner is not a sysadmin, it defaults to this guy.
HTH, mary
"Alex" wrote:
[vbcol=seagreen]
> Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> The side effect of this is that there are loads of admin tasks we cannot now
> do.
> Alex
>
> "Jerry Spivey" wrote:
|||Yes, try telling this to the auditors!
We are very frustrated. If we need to add a job we will need to apply for
permission to log in as sa, after going through multilevel of sign off from
the senior management - all for running a SQL Profile, or creating
maintenance plan !!
and then all actions will be be logged as well.
Alex
"Jerry Spivey" wrote:
> Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> the SYSADMIN fixed server role? How can you do your job?
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
>
>
|||Curious, if the is a reason to suddenly restore a db in the middle of the day
so production activities can resume, is the same process to log in as SA
required?
ChrisR
"Alex" wrote:
[vbcol=seagreen]
> Yes, try telling this to the auditors!
> We are very frustrated. If we need to add a job we will need to apply for
> permission to log in as sa, after going through multilevel of sign off from
> the senior management - all for running a SQL Profile, or creating
> maintenance plan !!
> and then all actions will be be logged as well.
> Alex
> "Jerry Spivey" wrote:
|||I don't recall anything in SOX that states that a DBA can not have sa
rights. Someone is taking the wording way beyond it's intent. SQL2005 will
have roles specifically for this but in 2000 it is not that easy.
Andrew J. Kelly SQL MVP
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...[vbcol=seagreen]
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
|||Thanks Mary. This could be the escape route we have been looking for!
Alex
"Mary" wrote:
[vbcol=seagreen]
> Since we don't want SA running jobs (or being in the Sysadmin group), I set
> up a login with win authent, sysadmin to run jobs. No one needs the password
> to use; just set this user up as the proxy account (under agent properties,
> job system), and if any job owner is not a sysadmin, it defaults to this guy.
> HTH, mary
> "Alex" wrote:
|||Andrew
We can run sa tasks, but we need authorisation every time we need to. its
like working with one of your hands tied.
Alex
"Andrew J. Kelly" wrote:
> I don't recall anything in SOX that states that a DBA can not have sa
> rights. Someone is taking the wording way beyond it's intent. SQL2005 will
> have roles specifically for this but in 2000 it is not that easy.
> --
> Andrew J. Kelly SQL MVP
>
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
>
>
Friday, March 9, 2012
Non administrators running perfmon have no remote SQL counters
affect SQL they are probably not specifically limited to this. This could
probably be posted in Windows 2000 security area as well.
Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
and fully patched, SQL Server 2000 and fully patched.
Database administration team wish to run system monitor / perfmon against
the server to baseline and monitor performance but segregation of duties
ensure that these can't be made local server administrators (I don't make the
rules I only try to work within them)
As an admin if I run perfmon locally on the server itself I can see all the
SQL performance objects. If I select counters from the computer remotely all
SQL counters are displayed - on this basis I know it is not a problem with
the performance counters themselves.
I have followed KB300702 to grant the non admin users access to perfmon
remotely and this works a treat except when the user fires up perfom and
lists the performance objects all of the SQL entries are missing. Even
though I have applied the access to the SQL service performance counters as
specified in the KB this still doesn't work.
I need to get this working without granting these users full administrator
rights or any of the other built in Windows groups OR without running the SQL
services with a different user ID /password and providing this to the
database team.
Any help that anyone can provide I will accept with extreme gratitude
Hi
Windows 2000 is not listed as one of the platforms in this KB?
http://support.microsoft.com/default...b;en-us;152513
in particular permissions on
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es
John
"Brian" wrote:
> Not sure if i am posting this in the right area as although my symptoms
> affect SQL they are probably not specifically limited to this. This could
> probably be posted in Windows 2000 security area as well.
> Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
> and fully patched, SQL Server 2000 and fully patched.
> Database administration team wish to run system monitor / perfmon against
> the server to baseline and monitor performance but segregation of duties
> ensure that these can't be made local server administrators (I don't make the
> rules I only try to work within them)
> As an admin if I run perfmon locally on the server itself I can see all the
> SQL performance objects. If I select counters from the computer remotely all
> SQL counters are displayed - on this basis I know it is not a problem with
> the performance counters themselves.
> I have followed KB300702 to grant the non admin users access to perfmon
> remotely and this works a treat except when the user fires up perfom and
> lists the performance objects all of the SQL entries are missing. Even
> though I have applied the access to the SQL service performance counters as
> specified in the KB this still doesn't work.
> I need to get this working without granting these users full administrator
> rights or any of the other built in Windows groups OR without running the SQL
> services with a different user ID /password and providing this to the
> database team.
> Any help that anyone can provide I will accept with extreme gratitude
|||John
Thanks for the response - you are correct in that the KB isn't listed as a
solution for Windows 2000 but a degree of commonality does exist - e.g. the
read permission required to the perflib area of the registry and the need for
full control on the performance key for each service.
The interesting bits (as I read it) seem to be that the remote counters are
running as a thread on the winlogon process and the idea that an issue with
an extensible DLL may be the problem - I will play around with this on my
test box and let you know how I get on.
Thanks again for your help
Brian
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Windows 2000 is not listed as one of the platforms in this KB?
> http://support.microsoft.com/default...b;en-us;152513
> in particular permissions on
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es
> John
> "Brian" wrote:
|||Hi
There is also http://support.microsoft.com/?id=812915 which may not be your
problem but implies it could be worth apply the hotfix/service pack if you
have not already done so.
John
"Brian" wrote:
[vbcol=seagreen]
> John
> Thanks for the response - you are correct in that the KB isn't listed as a
> solution for Windows 2000 but a degree of commonality does exist - e.g. the
> read permission required to the perflib area of the registry and the need for
> full control on the performance key for each service.
> The interesting bits (as I read it) seem to be that the remote counters are
> running as a thread on the winlogon process and the idea that an issue with
> an extensible DLL may be the problem - I will play around with this on my
> test box and let you know how I get on.
> Thanks again for your help
> Brian
>
> "John Bell" wrote:
Non administrators running perfmon have no remote SQL counters
affect SQL they are probably not specifically limited to this. This could
probably be posted in Windows 2000 security area as well.
Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
and fully patched, SQL Server 2000 and fully patched.
Database administration team wish to run system monitor / perfmon against
the server to baseline and monitor performance but segregation of duties
ensure that these can't be made local server administrators (I don't make th
e
rules I only try to work within them)
As an admin if I run perfmon locally on the server itself I can see all the
SQL performance objects. If I select counters from the computer remotely all
SQL counters are displayed - on this basis I know it is not a problem with
the performance counters themselves.
I have followed KB300702 to grant the non admin users access to perfmon
remotely and this works a treat except when the user fires up perfom and
lists the performance objects all of the SQL entries are missing. Even
though I have applied the access to the SQL service performance counters as
specified in the KB this still doesn't work.
I need to get this working without granting these users full administrator
rights or any of the other built in Windows groups OR without running the SQ
L
services with a different user ID /password and providing this to the
database team.
Any help that anyone can provide I will accept with extreme gratitudeHi
Windows 2000 is not listed as one of the platforms in this KB'
http://support.microsoft.com/defaul...kb;en-us;152513
in particular permissions on
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services
John
"Brian" wrote:
> Not sure if i am posting this in the right area as although my symptoms
> affect SQL they are probably not specifically limited to this. This could
> probably be posted in Windows 2000 security area as well.
> Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
> and fully patched, SQL Server 2000 and fully patched.
> Database administration team wish to run system monitor / perfmon against
> the server to baseline and monitor performance but segregation of duties
> ensure that these can't be made local server administrators (I don't make
the
> rules I only try to work within them)
> As an admin if I run perfmon locally on the server itself I can see all th
e
> SQL performance objects. If I select counters from the computer remotely a
ll
> SQL counters are displayed - on this basis I know it is not a problem with
> the performance counters themselves.
> I have followed KB300702 to grant the non admin users access to perfmon
> remotely and this works a treat except when the user fires up perfom and
> lists the performance objects all of the SQL entries are missing. Even
> though I have applied the access to the SQL service performance counters a
s
> specified in the KB this still doesn't work.
> I need to get this working without granting these users full administrator
> rights or any of the other built in Windows groups OR without running the
SQL
> services with a different user ID /password and providing this to the
> database team.
> Any help that anyone can provide I will accept with extreme gratitude|||John
Thanks for the response - you are correct in that the KB isn't listed as a
solution for Windows 2000 but a degree of commonality does exist - e.g. the
read permission required to the perflib area of the registry and the need fo
r
full control on the performance key for each service.
The interesting bits (as I read it) seem to be that the remote counters are
running as a thread on the winlogon process and the idea that an issue with
an extensible DLL may be the problem - I will play around with this on my
test box and let you know how I get on.
Thanks again for your help
Brian
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Windows 2000 is not listed as one of the platforms in this KB'
> http://support.microsoft.com/defaul...kb;en-us;152513
> in particular permissions on
> HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services
> John
> "Brian" wrote:
>|||Hi
There is also http://support.microsoft.com/?id=812915 which may not be your
problem but implies it could be worth apply the hotfix/service pack if you
have not already done so.
John
"Brian" wrote:
[vbcol=seagreen]
> John
> Thanks for the response - you are correct in that the KB isn't listed as a
> solution for Windows 2000 but a degree of commonality does exist - e.g. th
e
> read permission required to the perflib area of the registry and the need
for
> full control on the performance key for each service.
> The interesting bits (as I read it) seem to be that the remote counters ar
e
> running as a thread on the winlogon process and the idea that an issue wit
h
> an extensible DLL may be the problem - I will play around with this on my
> test box and let you know how I get on.
> Thanks again for your help
> Brian
>
> "John Bell" wrote:
>
Non administrators running perfmon have no remote SQL counters
affect SQL they are probably not specifically limited to this. This could
probably be posted in Windows 2000 security area as well.
Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
and fully patched, SQL Server 2000 and fully patched.
Database administration team wish to run system monitor / perfmon against
the server to baseline and monitor performance but segregation of duties
ensure that these can't be made local server administrators (I don't make the
rules I only try to work within them)
As an admin if I run perfmon locally on the server itself I can see all the
SQL performance objects. If I select counters from the computer remotely all
SQL counters are displayed - on this basis I know it is not a problem with
the performance counters themselves.
I have followed KB300702 to grant the non admin users access to perfmon
remotely and this works a treat except when the user fires up perfom and
lists the performance objects all of the SQL entries are missing. Even
though I have applied the access to the SQL service performance counters as
specified in the KB this still doesn't work.
I need to get this working without granting these users full administrator
rights or any of the other built in Windows groups OR without running the SQL
services with a different user ID /password and providing this to the
database team.
Any help that anyone can provide I will accept with extreme gratitudeHi
Windows 2000 is not listed as one of the platforms in this KB'
http://support.microsoft.com/default.aspx?scid=kb;en-us;152513
in particular permissions on
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
John
"Brian" wrote:
> Not sure if i am posting this in the right area as although my symptoms
> affect SQL they are probably not specifically limited to this. This could
> probably be posted in Windows 2000 security area as well.
> Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
> and fully patched, SQL Server 2000 and fully patched.
> Database administration team wish to run system monitor / perfmon against
> the server to baseline and monitor performance but segregation of duties
> ensure that these can't be made local server administrators (I don't make the
> rules I only try to work within them)
> As an admin if I run perfmon locally on the server itself I can see all the
> SQL performance objects. If I select counters from the computer remotely all
> SQL counters are displayed - on this basis I know it is not a problem with
> the performance counters themselves.
> I have followed KB300702 to grant the non admin users access to perfmon
> remotely and this works a treat except when the user fires up perfom and
> lists the performance objects all of the SQL entries are missing. Even
> though I have applied the access to the SQL service performance counters as
> specified in the KB this still doesn't work.
> I need to get this working without granting these users full administrator
> rights or any of the other built in Windows groups OR without running the SQL
> services with a different user ID /password and providing this to the
> database team.
> Any help that anyone can provide I will accept with extreme gratitude|||John
Thanks for the response - you are correct in that the KB isn't listed as a
solution for Windows 2000 but a degree of commonality does exist - e.g. the
read permission required to the perflib area of the registry and the need for
full control on the performance key for each service.
The interesting bits (as I read it) seem to be that the remote counters are
running as a thread on the winlogon process and the idea that an issue with
an extensible DLL may be the problem - I will play around with this on my
test box and let you know how I get on.
Thanks again for your help
Brian
"John Bell" wrote:
> Hi
> Windows 2000 is not listed as one of the platforms in this KB'
> http://support.microsoft.com/default.aspx?scid=kb;en-us;152513
> in particular permissions on
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
> John
> "Brian" wrote:
> > Not sure if i am posting this in the right area as although my symptoms
> > affect SQL they are probably not specifically limited to this. This could
> > probably be posted in Windows 2000 security area as well.
> >
> > Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
> > and fully patched, SQL Server 2000 and fully patched.
> >
> > Database administration team wish to run system monitor / perfmon against
> > the server to baseline and monitor performance but segregation of duties
> > ensure that these can't be made local server administrators (I don't make the
> > rules I only try to work within them)
> >
> > As an admin if I run perfmon locally on the server itself I can see all the
> > SQL performance objects. If I select counters from the computer remotely all
> > SQL counters are displayed - on this basis I know it is not a problem with
> > the performance counters themselves.
> >
> > I have followed KB300702 to grant the non admin users access to perfmon
> > remotely and this works a treat except when the user fires up perfom and
> > lists the performance objects all of the SQL entries are missing. Even
> > though I have applied the access to the SQL service performance counters as
> > specified in the KB this still doesn't work.
> >
> > I need to get this working without granting these users full administrator
> > rights or any of the other built in Windows groups OR without running the SQL
> > services with a different user ID /password and providing this to the
> > database team.
> >
> > Any help that anyone can provide I will accept with extreme gratitude|||Hi
There is also http://support.microsoft.com/?id=812915 which may not be your
problem but implies it could be worth apply the hotfix/service pack if you
have not already done so.
John
"Brian" wrote:
> John
> Thanks for the response - you are correct in that the KB isn't listed as a
> solution for Windows 2000 but a degree of commonality does exist - e.g. the
> read permission required to the perflib area of the registry and the need for
> full control on the performance key for each service.
> The interesting bits (as I read it) seem to be that the remote counters are
> running as a thread on the winlogon process and the idea that an issue with
> an extensible DLL may be the problem - I will play around with this on my
> test box and let you know how I get on.
> Thanks again for your help
> Brian
>
> "John Bell" wrote:
> > Hi
> >
> > Windows 2000 is not listed as one of the platforms in this KB'
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;152513
> > in particular permissions on
> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
> >
> > John
> >
> > "Brian" wrote:
> >
> > > Not sure if i am posting this in the right area as although my symptoms
> > > affect SQL they are probably not specifically limited to this. This could
> > > probably be posted in Windows 2000 security area as well.
> > >
> > > Server spec - HP Proliant server running Windows 2000 SP4, latest hotfixes
> > > and fully patched, SQL Server 2000 and fully patched.
> > >
> > > Database administration team wish to run system monitor / perfmon against
> > > the server to baseline and monitor performance but segregation of duties
> > > ensure that these can't be made local server administrators (I don't make the
> > > rules I only try to work within them)
> > >
> > > As an admin if I run perfmon locally on the server itself I can see all the
> > > SQL performance objects. If I select counters from the computer remotely all
> > > SQL counters are displayed - on this basis I know it is not a problem with
> > > the performance counters themselves.
> > >
> > > I have followed KB300702 to grant the non admin users access to perfmon
> > > remotely and this works a treat except when the user fires up perfom and
> > > lists the performance objects all of the SQL entries are missing. Even
> > > though I have applied the access to the SQL service performance counters as
> > > specified in the KB this still doesn't work.
> > >
> > > I need to get this working without granting these users full administrator
> > > rights or any of the other built in Windows groups OR without running the SQL
> > > services with a different user ID /password and providing this to the
> > > database team.
> > >
> > > Any help that anyone can provide I will accept with extreme gratitude
Wednesday, March 7, 2012
Node Cluster - Fails on Network Resources
servers (passive then active), one of the nodes did not successfully join the
cluster. This node shows exclamation marks on the Network Interfaces in
Cluster Administrator. These nics are functioning correctly outside of the
cluster. The cluster log on the failed node indicates that these network
interfaces are functioning each time it tries to join the cluster. The
active node's cluster log indicates that these resources are not functioning
and removes the other node from being active.
If anyone has any ideas on how to solve this problem, your input would be
greatly appreciated.
Thanks,
Debbie
Is the NIC you have exclamation mark on Public or Private network?
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@.microsoft.com...
> I am running a 2-node cluster for SQL Server. After powering down both
> servers (passive then active), one of the nodes did not successfully join
the
> cluster. This node shows exclamation marks on the Network Interfaces in
> Cluster Administrator. These nics are functioning correctly outside of
the
> cluster. The cluster log on the failed node indicates that these network
> interfaces are functioning each time it tries to join the cluster. The
> active node's cluster log indicates that these resources are not
functioning
> and removes the other node from being active.
> If anyone has any ideas on how to solve this problem, your input would be
> greatly appreciated.
> Thanks,
> Debbie
>
|||There are three NICs, the heartbeat (crossover), private (for backups) and
our intranet. All three have the exclamation mark.
"Ayad" wrote:
> Is the NIC you have exclamation mark on Public or Private network?
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@.microsoft.com...
> the
> the
> functioning
>
>
|||Check your IP settings and make sure you are using the correct subnet mask
address and network segment for each port and match each port with the other
node's port.
Was it working before or this is a new install?
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:89B546EC-247D-464E-A149-6952D4AC5EC7@.microsoft.com...[vbcol=seagreen]
> There are three NICs, the heartbeat (crossover), private (for backups) and
> our intranet. All three have the exclamation mark.
> "Ayad" wrote:
join[vbcol=seagreen]
in[vbcol=seagreen]
of[vbcol=seagreen]
network[vbcol=seagreen]
The[vbcol=seagreen]
be[vbcol=seagreen]
|||Ayad,
This is not a new install. It was working before. We had to power down all
of the servers for a generator hook-up to be installed. When bringing the
cluster back up, this server failed and has failed ever since with these NIC
resource errors.
The subnets look good on the NICs.
Thanks,
Debbie
"Ayad" wrote:
> Check your IP settings and make sure you are using the correct subnet mask
> address and network segment for each port and match each port with the other
> node's port.
> Was it working before or this is a new install?
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:89B546EC-247D-464E-A149-6952D4AC5EC7@.microsoft.com...
> join
> in
> of
> network
> The
> be
>
>
|||Debbie,
Try Shutdown that node (server hard reboot) and power it ON again and see if
it clears your NIC issue.
Ayad
"Debbie" <Debbie@.discussions.microsoft.com> wrote in message
news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@.microsoft.com...
> Ayad,
> This is not a new install. It was working before. We had to power down
all
> of the servers for a generator hook-up to be installed. When bringing the
> cluster back up, this server failed and has failed ever since with these
NIC[vbcol=seagreen]
> resource errors.
> The subnets look good on the NICs.
> Thanks,
> Debbie
> "Ayad" wrote:
mask[vbcol=seagreen]
other[vbcol=seagreen]
and[vbcol=seagreen]
both[vbcol=seagreen]
successfully[vbcol=seagreen]
Interfaces[vbcol=seagreen]
outside[vbcol=seagreen]
would[vbcol=seagreen]
|||Ayad,
The hard reboot did not clear up the problem. I am thinking of removing
this node from the cluster and then readding it to the cluster to see if that
clears up the problem.
Thanks,
Debbie
"Ayad" wrote:
> Debbie,
> Try Shutdown that node (server hard reboot) and power it ON again and see if
> it clears your NIC issue.
> Ayad
> "Debbie" <Debbie@.discussions.microsoft.com> wrote in message
> news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@.microsoft.com...
> all
> NIC
> mask
> other
> and
> both
> successfully
> Interfaces
> outside
> would
>
>
Saturday, February 25, 2012
No witness, primary shutsdown, bring failover online
First of all, Great webcast today. My question is, I have everything up and running and would like to know what to do when the machine my primary is on quits or has a some type of disaster. Do I need to manually run recovery on each db that was mirrored? I'm not currently running a witness.
thanks
No, you don't need to recover anything but depending on which mode you are running you will need to iether manually initiate a failover from server A to B or force the service from server A to B because you are running without a witness.
do you know what mode you are running, high-performance or high-protection?
|||Everything runs in high Safty and just to be clear I'm looking at the scenario where the primary just dies.|||ok, so you're running high protection mode.
I will have to correct myself here first, running in either high performance or high protection requires that you force service from server A to B. In books Online, look up the topics:
Forced Service (with Possible Data Loss)
and
How to: Force Service in a Database Mirroring Session (Transact-SQL)
these will explain in more detail than I ever could!
Hope this helps
|||This is correct. If the principal cannot be contacted, then the way to make the databases available on the mirror is to turn off mirroring or to issue a "FORCE_SERVICE_ALLOW_DATA_LOSS"
Thanks,
Mark
no trust connection
i having i workstation with running in windows 98, now i want link it to the SQL server which are in windows 2000. when i try to link it the following error message " no associate trust SQL Server Connection". Can i know how to settle this problem
thanks in advanceare you trying to connect to the server using windows integrated
authentication? If so, make sure you're logged on to the domain in your
workstation before trying to connect to sql server. You might want to try to
connect using standard authentication (i.e using sa or another login) just
to verify you can connect to the server successfully. If this doesn't work,
make sure you can get to the server through tcp port 1433 (sql server port);
this can be tested using the following command:
telnet servername 1433
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
> thanks in advance
>|||Hi,
Windows 98 will only support SQL server Authentication.
So while linking from SQL 2000, use SQL server Login credentials.
Thanks
Hari
MCDBA
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
> thanks in advance
>|||when i using window intergrate authentication that can sucess link to the SQL server, but when i using the SQL authentication it fail at the end so what should i do now.
how to open the port 1433 '
thanks in advance|||is there a firewall between the client and the server? If they are in the
same network you don't have to open ports or anything.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:D6026E6E-7EE4-4739-A280-9EA3BAD30032@.microsoft.com...
> when i using window intergrate authentication that can sucess link to the
SQL server, but when i using the SQL authentication it fail at the end so
what should i do now.
> how to open the port 1433 '?
> thanks in advance|||what error are you getting?
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:1256EDE4-FAA1-4A10-BF29-AAD182FBC94A@.microsoft.com...
> that r not any firewall install in that server, i just format and
reinstall the window for that server. so waht action i can take
> thanks in advance|||are you saying you get this error when trying to connect to sql server using
STANDARD authentication? It's weird, that error shows up when you can't
connect to sql but using integrated authentication.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:85BAB5CE-BD59-4559-A7E1-1ED4A36596BE@.microsoft.com...
> it also show "no associate trust SQL Server Connection"
no trust connection
i having i workstation with running in windows 98, now i want link it to the
SQL server which are in windows 2000. when i try to link it the following e
rror message " no associate trust SQL Server Connection". Can i know how to
settle this problem
thanks in advanceare you trying to connect to the server using windows integrated
authentication? If so, make sure you're logged on to the domain in your
workstation before trying to connect to sql server. You might want to try to
connect using standard authentication (i.e using sa or another login) just
to verify you can connect to the server successfully. If this doesn't work,
make sure you can get to the server through tcp port 1433 (sql server port);
this can be tested using the following command:
telnet servername 1433
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
quote:
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
quote:|||Hi,
> thanks in advance
>
Windows 98 will only support SQL server Authentication.
So while linking from SQL 2000, use SQL server Login credentials.
Thanks
Hari
MCDBA
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
quote:
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
quote:|||when i using window intergrate authentication that can sucess link to the SQ
> thanks in advance
>
L server, but when i using the SQL authentication it fail at the end so what
should i do now.
how to open the port 1433 '?
thanks in advance|||is there a firewall between the client and the server? If they are in the
same network you don't have to open ports or anything.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:D6026E6E-7EE4-4739-A280-9EA3BAD30032@.microsoft.com...
quote:
> when i using window intergrate authentication that can sucess link to the
SQL server, but when i using the SQL authentication it fail at the end so
what should i do now.
quote:|||that r not any firewall install in that server, i just format and reinstall
> how to open the port 1433 '?
> thanks in advance
the window for that server. so waht action i can take
thanks in advance|||what error are you getting?
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:1256EDE4-FAA1-4A10-BF29-AAD182FBC94A@.microsoft.com...
quote:
> that r not any firewall install in that server, i just format and
reinstall the window for that server. so waht action i can take
quote:|||it also show "no associate trust SQL Server Connection"|||are you saying you get this error when trying to connect to sql server using
> thanks in advance
STANDARD authentication? It's weird, that error shows up when you can't
connect to sql but using integrated authentication.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:85BAB5CE-BD59-4559-A7E1-1ED4A36596BE@.microsoft.com...
quote:
> it also show "no associate trust SQL Server Connection"