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

Friday, March 30, 2012

Manage SQL Server 2000 database from new workstation?

I'm currently using a new workstation and need to manage some databases on
my ISPs SQL 2000 server.
I've tried installing SSMSEE, but it won't install since I don't have
SQL2005 (or any SQL server) installed on this machine.
My host does not have a control panel that I can use to maintain SQL
databases.
What can I use to modify our online databases?
Hi,
you can use any third party tool:
http://www.aspfaq.com/2442
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1144223204.270214.319200@.e56g2000cwe.googlegr oups.com...
> Hi,
> you can use any third party tool:
> http://www.aspfaq.com/2442
Thanks!
Looks like I'm going to need a web based app due to firewall constraints.
Several to check out on that page.

Monday, March 19, 2012

Make SQL use more memory

I've got a Windows 2003 Enterprise server with 8GB of memory running
SQL 2005 Standard (32 bit). According to the documentation SQL can
take up to the OS maximum amount of memory (64 GB with PAE). Well,
SQL isn't taking more than about 1.5GB of memory, and the Buffer Cache
Hit Ratio is up close to 100. How can I make SQL use more physical
memory?
Thanks
Dylan
If the Buffer Cache Hit Ratio is 100, that means that SQL Server doesn't
need to take any more memory. Your queries are all using data that's
already cached. SQL Server will not take memory it doesn't need.

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"dylan" <dylan.roehrig@.gmail.com> wrote in message
news:1182433233.008715.247450@.o61g2000hsh.googlegr oups.com...
> I've got a Windows 2003 Enterprise server with 8GB of memory running
> SQL 2005 Standard (32 bit). According to the documentation SQL can
> take up to the OS maximum amount of memory (64 GB with PAE). Well,
> SQL isn't taking more than about 1.5GB of memory, and the Buffer Cache
> Hit Ratio is up close to 100. How can I make SQL use more physical
> memory?
> Thanks
> Dylan
>
|||On Jun 21, 9:47 am, "Adam Machanic" <amacha...@.IHATESPAMgmail.com>
wrote:[vbcol=seagreen]
> If the Buffer Cache Hit Ratio is 100, that means that SQL Server doesn't
> need to take any more memory. Your queries are all using data that's
> already cached. SQL Server will not take memory it doesn't need.
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
> "dylan" <dylan.roeh...@.gmail.com> wrote in message
> news:1182433233.008715.247450@.o61g2000hsh.googlegr oups.com...
>
Ah, so you're right - I was reading my thresholds sheet wrong. I guess
I should have thought about what a ratio is before posting.
In any event, this SQL server's not very highly utilized right now.
If it becomes more highly utilized and does in fact need to take more
memory, will it, or do I need to change anything? I was reading about
enabling AWE - is that something that I should have enabled?
Thanks!
Dylan
|||"dylan" <dylan.roehrig@.gmail.com> wrote in message
news:1182434972.723295.308160@.o61g2000hsh.googlegr oups.com...
> In any event, this SQL server's not very highly utilized right now.
> If it becomes more highly utilized and does in fact need to take more
> memory, will it, or do I need to change anything? I was reading about
> enabling AWE - is that something that I should have enabled?
Yes, you'll have to enable AWE if you want SQL Server to use any RAM
over the 2GB user-mode VAS limit.

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
|||On Jun 21, 10:16 am, "Adam Machanic" <amacha...@.IHATESPAMgmail.com>
wrote:
> "dylan" <dylan.roeh...@.gmail.com> wrote in message
> news:1182434972.723295.308160@.o61g2000hsh.googlegr oups.com...
>
>
> Yes, you'll have to enable AWE if you want SQL Server to use any RAM
> over the 2GB user-mode VAS limit.
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
Great, thanks - one last question. I see that you need to enable Lock
Pages in Memory access through group Policy. It says to:
In the Select Users or Groups dialog box, add an account with
privileges to run sqlservr.exe.
Is that referring to the user that the MSSQLSERVER service logs in as
when it starts, or is that just any user with login access to the
database? It seems like no matter what account (or accounts) I give
that access to, SQL still spits out an error saying that they don't
have access.
|||"dylan" <dylan.roehrig@.gmail.com> wrote in message
news:1182436089.647770.79590@.p77g2000hsh.googlegro ups.com...
> Great, thanks - one last question. I see that you need to enable Lock
> Pages in Memory access through group Policy. It says to:
As far as I know, that's only applicable to 64-bit, Enterprise Edition
SQL Server.

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
|||On Jun 21, 10:34 am, "Adam Machanic" <amacha...@.IHATESPAMgmail.com>
wrote:
> "dylan" <dylan.roeh...@.gmail.com> wrote in message
> news:1182436089.647770.79590@.p77g2000hsh.googlegro ups.com...
>
>
> As far as I know, that's only applicable to 64-bit, Enterprise Edition
> SQL Server.
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
Hmm, well according to this article http://msdn2.microsoft.com/en-us/library/ms190673(SQL.90).aspx
AWE is not needed and cannot be configured on 64-bit operating systems.
|||"dylan" <dylan.roehrig@.gmail.com> wrote in message
news:1182437032.054788.207030@.n60g2000hse.googlegr oups.com...
> Hmm, well according to this article
> http://msdn2.microsoft.com/en-us/library/ms190673(SQL.90).aspx
> AWE is not needed and cannot be configured on 64-bit operating systems.
AWE is needed for 32-bit SQL Server, whether running on a 32-bit or
64-bit operating system. Lock Pages in Memory is only needed for 64-bit SQL
Server. You're running 32-bit SQL Server, according to your first post?

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
|||On Jun 21, 11:09 am, "Adam Machanic" <amacha...@.IHATESPAMgmail.com>
wrote:
> "dylan" <dylan.roeh...@.gmail.com> wrote in message
> news:1182437032.054788.207030@.n60g2000hse.googlegr oups.com...
>
>
> AWE is needed for 32-bit SQL Server, whether running on a 32-bit or
> 64-bit operating system. Lock Pages in Memory is only needed for 64-bit SQL
> Server. You're running 32-bit SQL Server, according to your first post?
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
I really need to read these things better, I didn't see in your
previous post that you were talking about Enterprise Edition SQL
Server, I thought you meant 64 Bit Windows 2003 Enterprise Edition.
Yes, I am running 32 bit SQL Server Standard on 32 Bit Windows 2003
Enterprise. Given that, I can't get AWE to enable. When I try to
enable it, I get the following error:
Alter Failed (Microsoft.SQLServer.SMO)
Additional information
+ An exception occured while executing a Transact-SQL statement or
batch.
(Microsoft.SQLServer.ConnectionInfo)
+ Address Windowing Extensions (AWE) requires the "lock pages in
memory" privilege which is not currently present in the access token
of the process.
When I looked that up, I found that I needed to enable the Enable the
Lock Pages in Memory Option. Using this article
http://msdn2.microsoft.com/en-us/library/ms190730(SQL.90).aspx I tried
to do that, but it is still not working. Any insight?
Thanks very much for your help.
|||Do you have the /PAE switch enabled in boot.ini ?

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"dylan" <dylan.roehrig@.gmail.com> wrote in message
news:1182440393.064379.241090@.p77g2000hsh.googlegr oups.com...
> On Jun 21, 11:09 am, "Adam Machanic" <amacha...@.IHATESPAMgmail.com>
> wrote:
> I really need to read these things better, I didn't see in your
> previous post that you were talking about Enterprise Edition SQL
> Server, I thought you meant 64 Bit Windows 2003 Enterprise Edition.
> Yes, I am running 32 bit SQL Server Standard on 32 Bit Windows 2003
> Enterprise. Given that, I can't get AWE to enable. When I try to
> enable it, I get the following error:
> Alter Failed (Microsoft.SQLServer.SMO)
> Additional information
> + An exception occured while executing a Transact-SQL statement or
> batch.
> (Microsoft.SQLServer.ConnectionInfo)
> + Address Windowing Extensions (AWE) requires the "lock pages in
> memory" privilege which is not currently present in the access token
> of the process.
> When I looked that up, I found that I needed to enable the Enable the
> Lock Pages in Memory Option. Using this article
> http://msdn2.microsoft.com/en-us/library/ms190730(SQL.90).aspx I tried
> to do that, but it is still not working. Any insight?
> Thanks very much for your help.
>

Monday, March 12, 2012

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, Reeleezee
Solved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes?)
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee
|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, Reeleezee
Solved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes?)
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee
|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:

Wednesday, March 7, 2012

Mainteneance plans BAK TRN

Hi All,
Ive created a maintenance plan which does the following (all in one plan)
* All Databases
* Reorganise data,
Change free space per page percentage to 10%
Remove unused space from database files
Shrink database when it grows beyond 50 Mb
Amound of free space to remain after shrink 10%
*Check database integrity
include indexes
*Back up the database as part of the maintenance plan
Verify the integrity of the database upon completion
Backup to Disk
Use this Directory
Remove files older than 5 days
Backup file extension BAK
*Back up the Transaction log as part of the maintenance plan
Verify the integrity of the database upon completion
Backup to Disk
Use this Directory
Remove files older than 5 days
Backup file extension TRN
*Write a report file in the directory
delete report files after 14 days
We also have one other plan which simply checks the integrity on all DBs
once a week. Does this solution / plan seem ok? Its the first one I have
created so Im not 100% on it.
Also what rights/user does the plan run under?
I find that sometimes it deletes the files over 5 days and then sometimes it
just doesnt, or it will delete the TRN files but not the BAK files or vice
versa. I cant really make sense of it. Any ideas?
Also would I be better off having seperate plans for removing the BAK and
the TRN files?
Any help would be appreciated.
Thank youAdrin,
If you are using Sql Server 2000, then check your script and please
specify any pattern that you see in not removing old files.
You should be able to remove old files without any issues.
In Sql 2005 removing old files from sub-directory was not possible.
Even that is fixed after applying SP1.
Hope this helps,
Sameer Raval
[DBA-Developer]
Augusta,GA,USA
"Adrian" wrote:
> Hi All,
> Ive created a maintenance plan which does the following (all in one plan)
> * All Databases
> * Reorganise data,
> Change free space per page percentage to 10%
> Remove unused space from database files
> Shrink database when it grows beyond 50 Mb
> Amound of free space to remain after shrink 10%
> *Check database integrity
> include indexes
> *Back up the database as part of the maintenance plan
> Verify the integrity of the database upon completion
> Backup to Disk
> Use this Directory
> Remove files older than 5 days
> Backup file extension BAK
> *Back up the Transaction log as part of the maintenance plan
> Verify the integrity of the database upon completion
> Backup to Disk
> Use this Directory
> Remove files older than 5 days
> Backup file extension TRN
> *Write a report file in the directory
> delete report files after 14 days
> We also have one other plan which simply checks the integrity on all DBs
> once a week. Does this solution / plan seem ok? Its the first one I have
> created so Im not 100% on it.
> Also what rights/user does the plan run under?
> I find that sometimes it deletes the files over 5 days and then sometimes it
> just doesnt, or it will delete the TRN files but not the BAK files or vice
> versa. I cant really make sense of it. Any ideas?
> Also would I be better off having seperate plans for removing the BAK and
> the TRN files?
> Any help would be appreciated.
> Thank you|||In addition, I've seen a plan stopping execution if something goes wrong. This can lead to old
backup files not being removed. Read the report file carefully. Also, don't have databases in simple
recovery mode in a plan where you do log backups.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Sameer Raval" <SameerRaval@.discussions.microsoft.com> wrote in message
news:ED2CC0C2-6E36-4AA7-A6B4-8BD0AFD05934@.microsoft.com...
> Adrin,
> If you are using Sql Server 2000, then check your script and please
> specify any pattern that you see in not removing old files.
> You should be able to remove old files without any issues.
> In Sql 2005 removing old files from sub-directory was not possible.
> Even that is fixed after applying SP1.
> Hope this helps,
>
> Sameer Raval
> [DBA-Developer]
> Augusta,GA,USA
>
> "Adrian" wrote:
>> Hi All,
>> Ive created a maintenance plan which does the following (all in one plan)
>> * All Databases
>> * Reorganise data,
>> Change free space per page percentage to 10%
>> Remove unused space from database files
>> Shrink database when it grows beyond 50 Mb
>> Amound of free space to remain after shrink 10%
>> *Check database integrity
>> include indexes
>> *Back up the database as part of the maintenance plan
>> Verify the integrity of the database upon completion
>> Backup to Disk
>> Use this Directory
>> Remove files older than 5 days
>> Backup file extension BAK
>> *Back up the Transaction log as part of the maintenance plan
>> Verify the integrity of the database upon completion
>> Backup to Disk
>> Use this Directory
>> Remove files older than 5 days
>> Backup file extension TRN
>> *Write a report file in the directory
>> delete report files after 14 days
>> We also have one other plan which simply checks the integrity on all DBs
>> once a week. Does this solution / plan seem ok? Its the first one I have
>> created so Im not 100% on it.
>> Also what rights/user does the plan run under?
>> I find that sometimes it deletes the files over 5 days and then sometimes it
>> just doesnt, or it will delete the TRN files but not the BAK files or vice
>> versa. I cant really make sense of it. Any ideas?
>> Also would I be better off having seperate plans for removing the BAK and
>> the TRN files?
>> Any help would be appreciated.
>> Thank you|||Hey guys,
sorry for the late response I made some changes and wanted to wait a gew
days to see the results.
I changed all dbs to full recovery mode this seemed to fix the problem with
the BAK files and now they are getting backed up and removed successfully
after 5 days.
however the TRN files are still not being removed, I get the following
errors in my log file.
Backup can not be performed on database 'master'. This sub task is ignored.
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'Backup All DBs' on 01/08/2006 00:00:44
SQLMAINT.EXE Process Exit Code: 1 (Failed)
On different days I seem to get different dbs showing the same type of error
Backup can not be performed on database 'msdb'. This sub task is ignored.
Backup can not be performed on database 'pubs'. This sub task is ignored.
Any suggestions?|||You really need two separate plans. One for the databases for which you intend to do log backups,
and one for the databases that you don't intent to do log backups.
You cannot do log backups on master regardless of recovery model.
Agent will set msdb to simple recovery on startup.
Why do you backup pubs?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Adrian" <Adrian@.discussions.microsoft.com> wrote in message
news:97F75DCF-B984-4644-BD93-DE4798C81B4B@.microsoft.com...
> Hey guys,
> sorry for the late response I made some changes and wanted to wait a gew
> days to see the results.
> I changed all dbs to full recovery mode this seemed to fix the problem with
> the BAK files and now they are getting backed up and removed successfully
> after 5 days.
> however the TRN files are still not being removed, I get the following
> errors in my log file.
> Backup can not be performed on database 'master'. This sub task is ignored.
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'Backup All DBs' on 01/08/2006 00:00:44
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> On different days I seem to get different dbs showing the same type of error
> Backup can not be performed on database 'msdb'. This sub task is ignored.
> Backup can not be performed on database 'pubs'. This sub task is ignored.
> Any suggestions?
>|||Hi Tibor,
Im not quite sure I understand, I thought it was good practice to backup and
log all database's?
Am I right now in thinking that I should not backup or log the system
databases
Master, model, msdb, pubs, tempdb ?
Does my initial plan look ok, if I remove the system databases and just have
it for our business database's?
Thanks|||You should always do a FULL backup on Master, Model & MSDB but there is no
need for Log backups since they are either in Simple mode to begin with or
in the case of Model there are no changes made. Tempdb is rebuilt from
scratch each time you start up SQL Server so there is no need to back it up.
--
Andrew J. Kelly SQL MVP
"Adrian" <Adrian@.discussions.microsoft.com> wrote in message
news:12366730-7681-43DB-80BE-A838D1188209@.microsoft.com...
> Hi Tibor,
> Im not quite sure I understand, I thought it was good practice to backup
> and
> log all database's?
> Am I right now in thinking that I should not backup or log the system
> databases
> Master, model, msdb, pubs, tempdb ?
> Does my initial plan look ok, if I remove the system databases and just
> have
> it for our business database's?
> Thanks
>|||Thanks Andrew,
I have created a third Maintenance plan to back up the system dbs, Master,
Msdb and model.
I have also changed the Initial Plan to backup all user databases, I will
check this tomorrow and see the results.
"Andrew J. Kelly" wrote:
> You should always do a FULL backup on Master, Model & MSDB but there is no
> need for Log backups since they are either in Simple mode to begin with or
> in the case of Model there are no changes made. Tempdb is rebuilt from
> scratch each time you start up SQL Server so there is no need to back it up.
> --
> Andrew J. Kelly SQL MVP
> "Adrian" <Adrian@.discussions.microsoft.com> wrote in message
> news:12366730-7681-43DB-80BE-A838D1188209@.microsoft.com...
> > Hi Tibor,
> >
> > Im not quite sure I understand, I thought it was good practice to backup
> > and
> > log all database's?
> >
> > Am I right now in thinking that I should not backup or log the system
> > databases
> > Master, model, msdb, pubs, tempdb ?
> >
> > Does my initial plan look ok, if I remove the system databases and just
> > have
> > it for our business database's?
> >
> > Thanks
> >
>
>|||Adrian wrote:
> Thanks Andrew,
> I have created a third Maintenance plan to back up the system dbs, Master,
> Msdb and model.
> I have also changed the Initial Plan to backup all user databases, I will
> check this tomorrow and see the results.
>
Sounds like you have a solution, but if you decide that managing three
seperate maintenance plans is too much work, have a look at this script
of mine:
http://realsqlguy.com/twiki/bin/view/RealSQLGuy/AutomaticBackupOfAllDatabases
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Mainteneance plans BAK TRN

Hi All,
Ive created a maintenance plan which does the following (all in one plan)
* All Databases
* Reorganise data,
Change free space per page percentage to 10%
Remove unused space from database files
Shrink database when it grows beyond 50 Mb
Amound of free space to remain after shrink 10%
*Check database integrity
include indexes
*Back up the database as part of the maintenance plan
Verify the integrity of the database upon completion
Backup to Disk
Use this Directory
Remove files older than 5 days
Backup file extension BAK
*Back up the Transaction log as part of the maintenance plan
Verify the integrity of the database upon completion
Backup to Disk
Use this Directory
Remove files older than 5 days
Backup file extension TRN
*Write a report file in the directory
delete report files after 14 days
We also have one other plan which simply checks the integrity on all DBs
once a week. Does this solution / plan seem ok? Its the first one I have
created so Im not 100% on it.
Also what rights/user does the plan run under?
I find that sometimes it deletes the files over 5 days and then sometimes it
just doesnt, or it will delete the TRN files but not the BAK files or vice
versa. I cant really make sense of it. Any ideas?
Also would I be better off having seperate plans for removing the BAK and
the TRN files?
Any help would be appreciated.
Thank youAdrin,
If you are using Sql Server 2000, then check your script and please
specify any pattern that you see in not removing old files.
You should be able to remove old files without any issues.
In Sql 2005 removing old files from sub-directory was not possible.
Even that is fixed after applying SP1.
Hope this helps,
Sameer Raval
[DBA-Developer]
Augusta,GA,USA
"Adrian" wrote:

> Hi All,
> Ive created a maintenance plan which does the following (all in one plan)
> * All Databases
> * Reorganise data,
> Change free space per page percentage to 10%
> Remove unused space from database files
> Shrink database when it grows beyond 50 Mb
> Amound of free space to remain after shrink 10%
> *Check database integrity
> include indexes
> *Back up the database as part of the maintenance plan
> Verify the integrity of the database upon completion
> Backup to Disk
> Use this Directory
> Remove files older than 5 days
> Backup file extension BAK
> *Back up the Transaction log as part of the maintenance plan
> Verify the integrity of the database upon completion
> Backup to Disk
> Use this Directory
> Remove files older than 5 days
> Backup file extension TRN
> *Write a report file in the directory
> delete report files after 14 days
> We also have one other plan which simply checks the integrity on all DBs
> once a week. Does this solution / plan seem ok? Its the first one I have
> created so Im not 100% on it.
> Also what rights/user does the plan run under?
> I find that sometimes it deletes the files over 5 days and then sometimes
it
> just doesnt, or it will delete the TRN files but not the BAK files or vice
> versa. I cant really make sense of it. Any ideas?
> Also would I be better off having seperate plans for removing the BAK and
> the TRN files?
> Any help would be appreciated.
> Thank you|||In addition, I've seen a plan stopping execution if something goes wrong. Th
is can lead to old
backup files not being removed. Read the report file carefully. Also, don't
have databases in simple
recovery mode in a plan where you do log backups.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Sameer Raval" <SameerRaval@.discussions.microsoft.com> wrote in message
news:ED2CC0C2-6E36-4AA7-A6B4-8BD0AFD05934@.microsoft.com...[vbcol=seagreen]
> Adrin,
> If you are using Sql Server 2000, then check your script and please
> specify any pattern that you see in not removing old files.
> You should be able to remove old files without any issues.
> In Sql 2005 removing old files from sub-directory was not possible.
> Even that is fixed after applying SP1.
> Hope this helps,
>
> Sameer Raval
> [DBA-Developer]
> Augusta,GA,USA
>
> "Adrian" wrote:
>|||Hey guys,
sorry for the late response I made some changes and wanted to wait a gew
days to see the results.
I changed all dbs to full recovery mode this seemed to fix the problem with
the BAK files and now they are getting backed up and removed successfully
after 5 days.
however the TRN files are still not being removed, I get the following
errors in my log file.
Backup can not be performed on database 'master'. This sub task is ignored.
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'Backup All DBs' on 01/08/2006 00:00:44
SQLMAINT.EXE Process Exit Code: 1 (Failed)
On different days I seem to get different dbs showing the same type of error
Backup can not be performed on database 'msdb'. This sub task is ignored.
Backup can not be performed on database 'pubs'. This sub task is ignored.
Any suggestions?|||You really need two separate plans. One for the databases for which you inte
nd to do log backups,
and one for the databases that you don't intent to do log backups.
You cannot do log backups on master regardless of recovery model.
Agent will set msdb to simple recovery on startup.
Why do you backup pubs?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Adrian" <Adrian@.discussions.microsoft.com> wrote in message
news:97F75DCF-B984-4644-BD93-DE4798C81B4B@.microsoft.com...
> Hey guys,
> sorry for the late response I made some changes and wanted to wait a gew
> days to see the results.
> I changed all dbs to full recovery mode this seemed to fix the problem wit
h
> the BAK files and now they are getting backed up and removed successfully
> after 5 days.
> however the TRN files are still not being removed, I get the following
> errors in my log file.
> Backup can not be performed on database 'master'. This sub task is ignored
.
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'Backup All DBs' on 01/08/2006 00:00:44
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> On different days I seem to get different dbs showing the same type of err
or
> Backup can not be performed on database 'msdb'. This sub task is ignored.
> Backup can not be performed on database 'pubs'. This sub task is ignored.
> Any suggestions?
>|||Hi Tibor,
Im not quite sure I understand, I thought it was good practice to backup and
log all database's?
Am I right now in thinking that I should not backup or log the system
databases
Master, model, msdb, pubs, tempdb ?
Does my initial plan look ok, if I remove the system databases and just have
it for our business database's?
Thanks|||You should always do a FULL backup on Master, Model & MSDB but there is no
need for Log backups since they are either in Simple mode to begin with or
in the case of Model there are no changes made. Tempdb is rebuilt from
scratch each time you start up SQL Server so there is no need to back it up.
Andrew J. Kelly SQL MVP
"Adrian" <Adrian@.discussions.microsoft.com> wrote in message
news:12366730-7681-43DB-80BE-A838D1188209@.microsoft.com...
> Hi Tibor,
> Im not quite sure I understand, I thought it was good practice to backup
> and
> log all database's?
> Am I right now in thinking that I should not backup or log the system
> databases
> Master, model, msdb, pubs, tempdb ?
> Does my initial plan look ok, if I remove the system databases and just
> have
> it for our business database's?
> Thanks
>|||Thanks Andrew,
I have created a third Maintenance plan to back up the system dbs, Master,
Msdb and model.
I have also changed the Initial Plan to backup all user databases, I will
check this tomorrow and see the results.
"Andrew J. Kelly" wrote:

> You should always do a FULL backup on Master, Model & MSDB but there is no
> need for Log backups since they are either in Simple mode to begin with or
> in the case of Model there are no changes made. Tempdb is rebuilt from
> scratch each time you start up SQL Server so there is no need to back it u
p.
> --
> Andrew J. Kelly SQL MVP
> "Adrian" <Adrian@.discussions.microsoft.com> wrote in message
> news:12366730-7681-43DB-80BE-A838D1188209@.microsoft.com...
>
>|||Adrian wrote:
> Thanks Andrew,
> I have created a third Maintenance plan to back up the system dbs, Master,
> Msdb and model.
> I have also changed the Initial Plan to backup all user databases, I will
> check this tomorrow and see the results.
>
Sounds like you have a solution, but if you decide that managing three
seperate maintenance plans is too much work, have a look at this script
of mine:
http://realsqlguy.com/twiki/bin/vie...realsqlguy.com

Maintenance required after deploying merge pull replication?

Hi,
Before I ask for input, I just want to thank everyone in this
newsgroup for being so helpful... I've really gotten through some
complicated issues thanks to the information here. People like Hilary
are always coming through.
I am deploying a solution that depends on Continuous Merge Pull
replication... I can configure the systems of my customers, but once I
deploy them, I won't have direct administrative access to their copy
of MSDE which contains a pull subscription to our central database.
If needed, I could write an application to interface with MSDE through
the ActiveX controls...
What sort of control am I going to need so that I can always be sure
they are in sync? How can I make sure that if the connection is
dropped, or a new article is added, that they automatically keep
retrying until the process works?
In general, what are the problems do you think I might have after
deploying this sort of solution? Is it even workable without being
able to remote administer?
Thanks again
josh
Josh,
the agent failure/retry/success alerts should take care of some of these
concerns, provided you can configure email integration in your MSDEs.
To ensure the data is correctly transferred, occasional validation could be
used.
To ensure that the merge agent keeps retrying in the event of a network
failure, you can force it to work in an infinite loop (step 3 of the merge
agent's job step can have 'on success' and 'on failure' going back to step
2).
HTH,
Paul Ibison
|||So with an infinite loop trying to sync, will I also be covered for
any of the issues that normally cause the agent to stop?
For instance, replicating schema changes and new articles typically
requires a new snapshot, so the merge agent just stops itself (even in
continuous mode) until an up-to-date snapshot is posted. Will the
loop allow it to keep checking this?
Basically, I have no administrative access over the MSDE once it is
deployed (since it is on dynamic IP), and need to be sure there is
nothing that can cause sync to fail.
I suppose if the MSDE is on dynamic IP, there is no good way to
configure after deployment. Perhaps using replication is not the best
choice in this scenario. ..
Any input appreciated.
Thanks again,
josh
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:<eTsOlvAYEHA.3476@.tk2msftngp13.phx.gbl>...
> Josh,
> the agent failure/retry/success alerts should take care of some of these
> concerns, provided you can configure email integration in your MSDEs.
> To ensure the data is correctly transferred, occasional validation could be
> used.
> To ensure that the merge agent keeps retrying in the event of a network
> failure, you can force it to work in an infinite loop (step 3 of the merge
> agent's job step can have 'on success' and 'on failure' going back to step
> 2).
> HTH,
> Paul Ibison
|||Josh,
the loop will protect against network issues but not adding new articles.
When the article is added, you'll need to run the snapshot agent
immediately, to ensure the merge agent doesn't stop. You could have a step
in the snapshot agent (sp_start_job) which restarts the merge agent if
necessary.
Not to sure about the dynamic IP bit. The Netbios name is normally used
rather than the IP address to connect using Enterprise Manager. If you are
replicating to a subscriber on a non-trusted domain or over the internet
then I could see your problem.
The thought that you could no longer monitor the subscriber makes me
concerned, and in my opinion this will be a problem as time goes by. Perhaps
you could have the subscriber run a job on a schedule which posts its IP
address to the publisher, so you have the option of troubleshoting if
necessary.
Regards,
Paul Ibison

Maintenance Plans on MSDE

Hi NG,
I've defined a job and a maintenance plan on my SQL-Server. The target
system is using MSDE. I could see that the job was created, but with the
Enterprise Manager I cannot see that there is a folder 'Database Maintenance
Plans' under folder 'Management'.
Does anybody know if Maintenance plans are generally possible under MSDE, or
is there something missing on my target system where MSDE is installed.
Thanks for support, rene
hi Rene,
Re Fo wrote:
> Hi NG,
> I've defined a job and a maintenance plan on my SQL-Server. The target
> system is using MSDE. I could see that the job was created, but with
> the Enterprise Manager I cannot see that there is a folder 'Database
> Maintenance Plans' under folder 'Management'.
> Does anybody know if Maintenance plans are generally possible under
> MSDE, or is there something missing on my target system where MSDE is
> installed.
> Thanks for support, rene
Maintenance Plans are supported, but you do not have a graphical tool to
manage them, and have to rely on xp_sqlmaint system extended stored
procedure
(http://msdn.microsoft.com/library/de...-us/tsqlref/ts
_xp_aa-sz_0mb8.asp)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply