Forum Replies Created

Viewing 15 posts - 136 through 150 (of 297 total)

  • RE: AWE Enabled

    I'm currently on SP3 and I understand this is equivalent to SP2 + CU 10. So i don't believe this is what the issue is.

    Thanks anyways...

  • RE: AWE Enabled

    Did you see the bit in my post about Task Manager not showing memory use above the 4GB line? You need to look at what SQL Server says it...

  • RE: can not edit sql agent job

    I'm not sure I understand the question. The jobs are local on my sql server, if that's what you mean. It's not a job on another server somewhere...

  • RE: can not edit sql agent job

    If you connect to the cluser using the Virtual name or IP you should be ok in that case right? You should not have to disconnect and re-connect, which should...

  • RE: AWE Enabled

    EXECUTE sp_configure 'awe enabled'

    GO

    This has the values 0, 1, 1, 0

  • RE: AWE Enabled

    Just to re-iterate, the SQL Server box was bounced after PAE and AWE was enabled. Even though the OS now recognizes the 8GB memory, Total Server Memory for the SQL...

  • RE: AWE Enabled

    The server is DL380 with 8GB physical memory. It has Windows 2003 with SP2 EE and SQL 2005 SP3 EE installed on it.

    So does this mean that I need to...

  • RE: SQL Server 2000 Security

    You can also do this by reading / parsing the error log within SQL Server and keeping track of the number of failed attempts, and after you're threshold is crossed,...

  • RE: can not edit sql agent job

    That's right sysadmin is by default owner of all the jobs. These are local jobs right?

  • RE: Killing a restore process

    Krishna,

    Even after you have a fresh copy of the database, you want to restore one copy at a time since reading from the same file may end up causing contention...

  • RE: can not edit sql agent job

    Have you confirmed you are still the owner of the job?

  • RE: Killing a restore process

    In all probability you will end up with a database that is suspect or one that has its integrity compromised.

    Even if you are able to restore from the same file...

  • RE: Post Installation

    1433 is the default port SQL Server is listening on. You could change the port for it to listen to another static port or have it set to dynamically select...

  • RE: Post Installation

    Best practices analyzer is usually run when you're ready to go to Production. That will be your baseline.

    Once you, are in Production, you would need to run it to...

  • RE: Post Installation

    I would look at each of these recommendations closely and see which ones best fit your environment. Like with everything else, never a one solution fits all.

Viewing 15 posts - 136 through 150 (of 297 total)