Showing posts with label changing. Show all posts
Showing posts with label changing. Show all posts

Friday, March 30, 2012

Restrict Port Security

I'm going to be installing a sql server behind a firewall. I'd appreciate
any best practice advice on changing the default port number and also wanted
to know if there was a way to secure a sql server by granting access only to
specific IP addresses?
Hi Scott,
Really best practice is changing the default port number of the SQL Server.
But granting access to specific IP addresses only machine 1 to machine 2 or
ip address.
Hugs,
Rodrigo Fernandes
MCSE/MCDBA
"scott" wrote:

> I'm going to be installing a sql server behind a firewall. I'd appreciate
> any best practice advice on changing the default port number and also wanted
> to know if there was a way to secure a sql server by granting access only to
> specific IP addresses?
>
>
|||What do you mean by saying 'but granting access ...'?
"Rodrigo Fernandes" <RodrigoFernandes@.discussions.microsoft.com> wrote in
message news:94A130F7-B240-44DF-9054-9E2BC08D9DE3@.microsoft.com...[vbcol=seagreen]
> Hi Scott,
> Really best practice is changing the default port number of the SQL
> Server.
> But granting access to specific IP addresses only machine 1 to machine 2
> or
> ip address.
> Hugs,
> Rodrigo Fernandes
> MCSE/MCDBA
> "scott" wrote:

Restrict Port Security

I'm going to be installing a sql server behind a firewall. I'd appreciate
any best practice advice on changing the default port number and also wanted
to know if there was a way to secure a sql server by granting access only to
specific IP addresses?Hi Scott,
Really best practice is changing the default port number of the SQL Server.
But granting access to specific IP addresses only machine 1 to machine 2 or
ip address.
Hugs,
Rodrigo Fernandes
MCSE/MCDBA
"scott" wrote:

> I'm going to be installing a sql server behind a firewall. I'd appreciate
> any best practice advice on changing the default port number and also want
ed
> to know if there was a way to secure a sql server by granting access only
to
> specific IP addresses?
>
>|||What do you mean by saying 'but granting access ...'?
"Rodrigo Fernandes" <RodrigoFernandes@.discussions.microsoft.com> wrote in
message news:94A130F7-B240-44DF-9054-9E2BC08D9DE3@.microsoft.com...[vbcol=seagreen]
> Hi Scott,
> Really best practice is changing the default port number of the SQL
> Server.
> But granting access to specific IP addresses only machine 1 to machine 2
> or
> ip address.
> Hugs,
> Rodrigo Fernandes
> MCSE/MCDBA
> "scott" wrote:
>

Restrict Port Security

I'm going to be installing a sql server behind a firewall. I'd appreciate
any best practice advice on changing the default port number and also wanted
to know if there was a way to secure a sql server by granting access only to
specific IP addresses?Hi Scott,
Really best practice is changing the default port number of the SQL Server.
But granting access to specific IP addresses only machine 1 to machine 2 or
ip address.
Hugs,
Rodrigo Fernandes
MCSE/MCDBA
"scott" wrote:
> I'm going to be installing a sql server behind a firewall. I'd appreciate
> any best practice advice on changing the default port number and also wanted
> to know if there was a way to secure a sql server by granting access only to
> specific IP addresses?
>
>|||What do you mean by saying 'but granting access ...'?
"Rodrigo Fernandes" <RodrigoFernandes@.discussions.microsoft.com> wrote in
message news:94A130F7-B240-44DF-9054-9E2BC08D9DE3@.microsoft.com...
> Hi Scott,
> Really best practice is changing the default port number of the SQL
> Server.
> But granting access to specific IP addresses only machine 1 to machine 2
> or
> ip address.
> Hugs,
> Rodrigo Fernandes
> MCSE/MCDBA
> "scott" wrote:
>> I'm going to be installing a sql server behind a firewall. I'd appreciate
>> any best practice advice on changing the default port number and also
>> wanted
>> to know if there was a way to secure a sql server by granting access only
>> to
>> specific IP addresses?
>>sql

Tuesday, March 20, 2012

restoring msdb**

Hi
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.RM,
Do you get an error number?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.|||Also check SQL server error log and SQLAgent log for complete information on this behaviour.
--
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
> > Hi
> >
> > I restored msdb database successfully,
> > because of changing
> > the server and needed to restore all jobs
> > have been schaduled for periodical backup all
> > user batabases.
> > but when I want to change the text of step1
> > of every job to new drive in a new server
> > following error happened:
> > ""
> >
> > why? what's wrong?
> > any help would be greatly appreciated.
>|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> yeah,
>> error 14274
>> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
>> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> -- Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>>