Hi
Is it wise to open port 1433/1434 so that a remote user can access sql server thats on my dmz
ThanksBetter to use non-standard ports, if possible.
Sincerely,
Invotion Engineering Team
Advanced Microsoft Hosting Solutions
http://www.Invotion.com
>--Original Message--
>Hi,
>Is it wise to open port 1433/1434 so that a remote user
can access sql server thats on my dmz?
>Thanks
>.
>|||Hi
Where can I find info on changing the ports
Thanks
Showing posts with label remote. Show all posts
Showing posts with label remote. Show all posts
Tuesday, March 20, 2012
Wednesday, March 7, 2012
osql or isql to run a batch remotely
Hello,
I have a collection of SQL Scripts that I would like to execute using a
batch file from a remote machine. Does anyone have any suggestions? I
think that I could use osql or isql, but I have never done that before. I
would appreciate any assistance.
Stewart
Stewart Saathoff wrote:
> Hello,
> I have a collection of SQL Scripts that I would like to execute using
> a batch file from a remote machine. Does anyone have any
> suggestions? I think that I could use osql or isql, but I have never
> done that before. I would appreciate any assistance.
> Stewart
I'm unclear about what is where...
Where is the file you want to execute located?
Do you want to run this file from a remote client or do you want to run
the file as though it were running directly on the server?
You can kick off OSQL from a stored procedure or a SQL Agent job on the
server. You could kick off OSQL from a client PC and execute a script
file that resides on the client PC. I would say that if the script file
is large, you'll get better performance running it from the server.
David Gugick
Imceda Software
www.imceda.com
|||ok, Let me be more clear.
I have a very large SQL Statement that needs to be run on the server.
Ideally the client will sit on their workstation and double-click on a file.
That file should execute the SQL statement on the server. I am pretty
positive that I can do all of this using osql, however I am unclear how I
can do this using a batch file. I don't want the users to have to type a
considerable amount and I definately do not want them to have to learn osql
or sql commands to do this...
Stewart
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%237j3Oby1EHA.524@.TK2MSFTNGP09.phx.gbl...
> Stewart Saathoff wrote:
> I'm unclear about what is where...
> Where is the file you want to execute located?
> Do you want to run this file from a remote client or do you want to run
> the file as though it were running directly on the server?
> You can kick off OSQL from a stored procedure or a SQL Agent job on the
> server. You could kick off OSQL from a client PC and execute a script file
> that resides on the client PC. I would say that if the script file is
> large, you'll get better performance running it from the server.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
|||Stewart Saathoff wrote:
> ok, Let me be more clear.
> I have a very large SQL Statement that needs to be run on the server.
> Ideally the client will sit on their workstation and double-click on
> a file. That file should execute the SQL statement on the server. I
> am pretty positive that I can do all of this using osql, however I am
> unclear how I can do this using a batch file. I don't want the users
> to have to type a considerable amount and I definately do not want
> them to have to learn osql or sql commands to do this...
> Stewart
>
If you have to run the SQL batch from a client PC, you can use OSQL.
There's an option for submitting a file to run. The command-line
interface is fairly straightforward and documented in BOL.
David Gugick
Imceda Software
www.imceda.com
|||<snip>
> I am pretty positive that I can do all of this using
> osql, however I am unclear how I can do this using a
> batch file.
<snip>
Stewart,
Assuming you get this to work at the command prompt...
osql -SBigBox -Uuser -Ppwd -ddbname -i somefile.sql -o somefile.log
You can just paste it into a BAT file: that's it. You can use @.ECHO OFF,
print out message, etc to pretty it up but that's pretty much all you need.
You would need a file with your SQL statement where the BAT file runs
(ideally the same folder). If that's not acceptable, then you could put the
statement in a stored proc and call the proc by name instead of using the
input file.
Craig
|||Thank you all for your help. Everything works great.
"Craig Kelly" <cnkelly.nospam@.nospam.net> wrote in message
news:yY9rd.1007069$Gx4.741632@.bgtnsc04-news.ops.worldnet.att.net...
> <snip>
>
> <snip>
> Stewart,
> Assuming you get this to work at the command prompt...
> osql -SBigBox -Uuser -Ppwd -ddbname -i somefile.sql -o somefile.log
> You can just paste it into a BAT file: that's it. You can use @.ECHO OFF,
> print out message, etc to pretty it up but that's pretty much all you
> need.
> You would need a file with your SQL statement where the BAT file runs
> (ideally the same folder). If that's not acceptable, then you could put
> the statement in a stored proc and call the proc by name instead of using
> the input file.
> Craig
>
I have a collection of SQL Scripts that I would like to execute using a
batch file from a remote machine. Does anyone have any suggestions? I
think that I could use osql or isql, but I have never done that before. I
would appreciate any assistance.
Stewart
Stewart Saathoff wrote:
> Hello,
> I have a collection of SQL Scripts that I would like to execute using
> a batch file from a remote machine. Does anyone have any
> suggestions? I think that I could use osql or isql, but I have never
> done that before. I would appreciate any assistance.
> Stewart
I'm unclear about what is where...
Where is the file you want to execute located?
Do you want to run this file from a remote client or do you want to run
the file as though it were running directly on the server?
You can kick off OSQL from a stored procedure or a SQL Agent job on the
server. You could kick off OSQL from a client PC and execute a script
file that resides on the client PC. I would say that if the script file
is large, you'll get better performance running it from the server.
David Gugick
Imceda Software
www.imceda.com
|||ok, Let me be more clear.
I have a very large SQL Statement that needs to be run on the server.
Ideally the client will sit on their workstation and double-click on a file.
That file should execute the SQL statement on the server. I am pretty
positive that I can do all of this using osql, however I am unclear how I
can do this using a batch file. I don't want the users to have to type a
considerable amount and I definately do not want them to have to learn osql
or sql commands to do this...
Stewart
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%237j3Oby1EHA.524@.TK2MSFTNGP09.phx.gbl...
> Stewart Saathoff wrote:
> I'm unclear about what is where...
> Where is the file you want to execute located?
> Do you want to run this file from a remote client or do you want to run
> the file as though it were running directly on the server?
> You can kick off OSQL from a stored procedure or a SQL Agent job on the
> server. You could kick off OSQL from a client PC and execute a script file
> that resides on the client PC. I would say that if the script file is
> large, you'll get better performance running it from the server.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
|||Stewart Saathoff wrote:
> ok, Let me be more clear.
> I have a very large SQL Statement that needs to be run on the server.
> Ideally the client will sit on their workstation and double-click on
> a file. That file should execute the SQL statement on the server. I
> am pretty positive that I can do all of this using osql, however I am
> unclear how I can do this using a batch file. I don't want the users
> to have to type a considerable amount and I definately do not want
> them to have to learn osql or sql commands to do this...
> Stewart
>
If you have to run the SQL batch from a client PC, you can use OSQL.
There's an option for submitting a file to run. The command-line
interface is fairly straightforward and documented in BOL.
David Gugick
Imceda Software
www.imceda.com
|||<snip>
> I am pretty positive that I can do all of this using
> osql, however I am unclear how I can do this using a
> batch file.
<snip>
Stewart,
Assuming you get this to work at the command prompt...
osql -SBigBox -Uuser -Ppwd -ddbname -i somefile.sql -o somefile.log
You can just paste it into a BAT file: that's it. You can use @.ECHO OFF,
print out message, etc to pretty it up but that's pretty much all you need.
You would need a file with your SQL statement where the BAT file runs
(ideally the same folder). If that's not acceptable, then you could put the
statement in a stored proc and call the proc by name instead of using the
input file.
Craig
|||Thank you all for your help. Everything works great.
"Craig Kelly" <cnkelly.nospam@.nospam.net> wrote in message
news:yY9rd.1007069$Gx4.741632@.bgtnsc04-news.ops.worldnet.att.net...
> <snip>
>
> <snip>
> Stewart,
> Assuming you get this to work at the command prompt...
> osql -SBigBox -Uuser -Ppwd -ddbname -i somefile.sql -o somefile.log
> You can just paste it into a BAT file: that's it. You can use @.ECHO OFF,
> print out message, etc to pretty it up but that's pretty much all you
> need.
> You would need a file with your SQL statement where the BAT file runs
> (ideally the same folder). If that's not acceptable, then you could put
> the statement in a stored proc and call the proc by name instead of using
> the input file.
> Craig
>
Monday, February 20, 2012
orphaned request in the RSLog
we are trying to track down an error we get in RS where the ssl connection
is forcibly closed by the remote server. Going through the RS Logs I noticed
these info statements. Can anyone explain in better detail what these mean?
w3wp!runningjobs!11b4!9/16/2005-16:06:35:: w WARN: Thread pool pressure:
turning off threads
w3wp!runningjobs!11b4!09/16/2005-16:06:37:: w WARN: Thread pool pressure:
turning off threads
w3wp!library!11b4!09/16/2005-16:06:37:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!runningjobs!11b4!9/16/2005-16:07:15:: i INFO: Adding: 5 running jobs to
the database
w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:FYI,,, We are running RS SP2 on clustered Windows Server 2003
"Mark" wrote:
> we are trying to track down an error we get in RS where the ssl connection
> is forcibly closed by the remote server. Going through the RS Logs I noticed
> these info statements. Can anyone explain in better detail what these mean?
>
> w3wp!runningjobs!11b4!9/16/2005-16:06:35:: w WARN: Thread pool pressure:
> turning off threads
> w3wp!runningjobs!11b4!09/16/2005-16:06:37:: w WARN: Thread pool pressure:
> turning off threads
> w3wp!library!11b4!09/16/2005-16:06:37:: i INFO: Initializing
> EnableExecutionLogging to 'True' as specified in Server system properties.
> w3wp!runningjobs!11b4!9/16/2005-16:07:15:: i INFO: Adding: 5 running jobs to
> the database
> w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:|||Hi Mark,
Thanks for your posting!
From your descriptions, I understood when disconnected forcibly from remote
server, your Report Server will report the error message "found orphaned
request". If I have misunderstood your concern, please feel free to point
it out.
I believe due to the none response from client (it was disconnected
forcibly), some existing request become orphaned. Does this error message
make any business impact on your server?
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.|||So are you saying then that its' the client that is actually disconnecting
from the server?
This issue actually goes back to an early post I had with long running
reports
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&query=long+running+reports&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=80219d15-436f-4b8e-ad0d-0c8c604c6b9f&mid=80219d15-436f-4b8e-ad0d-0c8c604c6b9f
It seems we constantly get this message when we have a batch job running
on a client machine doing a soap call to the RS server. Everything runs fine
until it hits 15 minutes and then we get the SSL connection closed error. We
have tried a variety of things from upgrading to sp2 applying serveral hot
fixes, and changing the defualt IIS timeout settings from 900 seconds to 600
seconds. All to no avail. At exaclty 15 minutes we get disconnected.
I was looking then through the RSlogs and saw the orphaned requests coming
up at about the same time we get the ssl connection error and decided to post
again to see if that might trigger a new approach.
Frustrated at 15!!!
"Michael Cheng [MSFT]" wrote:
> Hi Mark,
> Thanks for your posting!
> From your descriptions, I understood when disconnected forcibly from remote
> server, your Report Server will report the error message "found orphaned
> request". If I have misunderstood your concern, please feel free to point
> it out.
> I believe due to the none response from client (it was disconnected
> forcibly), some existing request become orphaned. Does this error message
> make any business impact on your server?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner 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 Mark,
From the error, I belive it seems to be caused by data connection to
datasource for the report. You may want to check if the following error is
also in RS log:
e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has
occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error
has occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Query
execution failed for data set 'MSFixlets'. -->
System.Data.SqlClient.SqlException:
Timeout expired. The timeout period elapsed prior to completion of the
operation
or the server is not responding.
You may try the following steps:
Open up the report project in VS.NET IDE, go to the Data tab and edit the
dataset which brings back those images. In the Query tab, set the timeout
property to more than 900 (15 mins).
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.
is forcibly closed by the remote server. Going through the RS Logs I noticed
these info statements. Can anyone explain in better detail what these mean?
w3wp!runningjobs!11b4!9/16/2005-16:06:35:: w WARN: Thread pool pressure:
turning off threads
w3wp!runningjobs!11b4!09/16/2005-16:06:37:: w WARN: Thread pool pressure:
turning off threads
w3wp!library!11b4!09/16/2005-16:06:37:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!runningjobs!11b4!9/16/2005-16:07:15:: i INFO: Adding: 5 running jobs to
the database
w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:FYI,,, We are running RS SP2 on clustered Windows Server 2003
"Mark" wrote:
> we are trying to track down an error we get in RS where the ssl connection
> is forcibly closed by the remote server. Going through the RS Logs I noticed
> these info statements. Can anyone explain in better detail what these mean?
>
> w3wp!runningjobs!11b4!9/16/2005-16:06:35:: w WARN: Thread pool pressure:
> turning off threads
> w3wp!runningjobs!11b4!09/16/2005-16:06:37:: w WARN: Thread pool pressure:
> turning off threads
> w3wp!library!11b4!09/16/2005-16:06:37:: i INFO: Initializing
> EnableExecutionLogging to 'True' as specified in Server system properties.
> w3wp!runningjobs!11b4!9/16/2005-16:07:15:: i INFO: Adding: 5 running jobs to
> the database
> w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1d5c!9/16/2005-16:07:15:: i INFO:|||Hi Mark,
Thanks for your posting!
From your descriptions, I understood when disconnected forcibly from remote
server, your Report Server will report the error message "found orphaned
request". If I have misunderstood your concern, please feel free to point
it out.
I believe due to the none response from client (it was disconnected
forcibly), some existing request become orphaned. Does this error message
make any business impact on your server?
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.|||So are you saying then that its' the client that is actually disconnecting
from the server?
This issue actually goes back to an early post I had with long running
reports
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&query=long+running+reports&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=80219d15-436f-4b8e-ad0d-0c8c604c6b9f&mid=80219d15-436f-4b8e-ad0d-0c8c604c6b9f
It seems we constantly get this message when we have a batch job running
on a client machine doing a soap call to the RS server. Everything runs fine
until it hits 15 minutes and then we get the SSL connection closed error. We
have tried a variety of things from upgrading to sp2 applying serveral hot
fixes, and changing the defualt IIS timeout settings from 900 seconds to 600
seconds. All to no avail. At exaclty 15 minutes we get disconnected.
I was looking then through the RSlogs and saw the orphaned requests coming
up at about the same time we get the ssl connection error and decided to post
again to see if that might trigger a new approach.
Frustrated at 15!!!
"Michael Cheng [MSFT]" wrote:
> Hi Mark,
> Thanks for your posting!
> From your descriptions, I understood when disconnected forcibly from remote
> server, your Report Server will report the error message "found orphaned
> request". If I have misunderstood your concern, please feel free to point
> it out.
> I believe due to the none response from client (it was disconnected
> forcibly), some existing request become orphaned. Does this error message
> make any business impact on your server?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner 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 Mark,
From the error, I belive it seems to be caused by data connection to
datasource for the report. You may want to check if the following error is
also in RS log:
e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has
occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error
has occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Query
execution failed for data set 'MSFixlets'. -->
System.Data.SqlClient.SqlException:
Timeout expired. The timeout period elapsed prior to completion of the
operation
or the server is not responding.
You may try the following steps:
Open up the report project in VS.NET IDE, go to the Data tab and edit the
dataset which brings back those images. In the Query tab, set the timeout
property to more than 900 (15 mins).
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.
Subscribe to:
Posts (Atom)