I have SQL Server 2005 Express on a Windows XP SP2 machine. Everything works fine and I have several dbs running. How ever I was wanting to optimize some programs and needed to watch the server and see what it is processing. I log into SQL Management Studio Express and when I go to Management->Server Logs I see the logs and the Activity Monitor. If I right click on the log all I see is Refresh. If I doule click nothing happens. I can view the Activity Monitor and the processes going.
I am sure it is a permission thing or something along those lines. I can not for the life of me figure it and have spent a couple days on google and these forums. I have tried with the SA, my defined users, and the local windows administrator. Is log viewing not allowed in SQL Server Express?
How do I view the .LOG file output by the SQL Performance Monitor? When I try to "Load" the log file, it looks for a *.PML extension, but I believe this is a settings file from which desired counters to track are stored. I have created an output file which has the extension *.LOG (the only choice I could pick) and I want to view this.
The file is not a text file and would not load/translate into Word on-the-fly as I had hoped.
We'd like to load our log files periodically so as to parse for particular events. We want to analyse our server performance over time.
I am trying to create a set of "Reporting" views and grant Select permission on those views instead of the tables. I created the view in the same database but under a different schema from the tables. When the user tries to select from the views they get an error saying they do not have select privilege on the tables. Do I need to grant them select on the underlying tables?
What is the best way to grant a user permission to create a view?I first created a role using enterprise manager but for the role Icreated it doesn't seem to offer that permission. It offers the basicstuff such as insert, select, and update.I could go in and use a grant create view sql statement I suppose butI'd rather do it through enterprise manager where it would be visibleif I need to change it in the future.-David
Hi, This is regarding the SQL 2005 Report Manager (http://localhost/Reports) page. I have posted the reports, the reports run fine, buttons like new folder, new data source, etc... are visible (lets call this machine as A). The problem is when my machine is accessed from a nearby computer on the same network as http://machineA/Reports, the Report manager Home page appears with limited or no buttons. The reports are also not visible in the browser of machine B. How do I make the reports visible to users (grant permission) for them to run and view those reports?
In a nutshell, how the posted reports be accessed by users?
My company has upgraded some of the database systems to SQL 2005 while other have a fresh install.
The problem we're seeing is that the view button located in the Advanced section of the steps in the Job properties windows is greyed out. The path is valid as we can copy the path and paste it at the run command and view the log.
Does anyone know how this problem can be resolved? If we select to log the results to a table; we have access to the corresponding view button but not the one for the file system logging.
We rely heavily on this feature since we used it often under SQL 2K. Can anyone provide any helpful details to resolve this or has anyone seen this problem before???
Hi guys, just wanna ask about the backup and restore database method. What's the best way for database and restore which able to view all the transaction logs after the database being restored. Currently I backup my database daily for recovery purposes. However, if I restore the backup file at another server and use SQL log application for viewing the prefer database's transaction log, it shows all the previous log had been truncated.
Therefore, I want to know is there any way that able to get the transaction logs after restore from a database backup file? Hope able to get any assistance here as soon as possible. Thank you.
On our production SQL 2005 servers I want to give developers readonly access to each user database and also give them the ability to see stored procedures. Readonly is handled through db_datareader, but how do I give them the ability to see stored procedures without granting permission to execute them?
We have a third party application and wish to create a report based upon a view.
The strange thing is logged in to the server as a SQL SYSAdmin account, we cannot view the data via the view. SQL Admin accounts are setup correctly and there is nothing different on this particular server. No errors are returned just a blank view with no records.
Could this be a permissions problem or orphaned schemas in that particular database? I thought SYSAdmin could view and do just about anything and the people who use this particular database would not have the know how on denying permission to the SYSAdmin role.
I want to grant access on the below view for an end user so that he connect to our SQL server and retrieve data. The view looks like the below
CREATE VIEW DB1.[dbo].[View1] AS -- For brevity, I made it as simple statement. SELECT * From DB2.dbo.table2 GO
For the above view, it looks like I have to grant select and connect permission for the DB1. [dbo].[View1] as well as DB2.dbo.table2.
1. Is my understanding correct?
2. I want the user to access only DB1. [dbo].[View1] and not the underlying tables. Is there a way to grant access only on the view and execute the statement on a different security context so that the user can€™t access DB2.dbo.table2 directly?
3. When the user uses SQL Server Management Studio to connect to SQL server, he is able to connect and select DB2.dbo.table2 directly. Is there any way to restrict user from viewing and executing select statement on DB2 database from SQL Server Management Studio
I am currently trying to export from SQL to notes via NotesSQL.I have set up the necessary ODBC data sources & DTS job. I am encountering errors when I attempt to execute the DTS package . I.e "job failed" - How do I drill down to aquire more detailed error logging on the package to find out exactly what's wrong with DTS?
When I'm in EM, there is one log that when I click on it to view it hangs my EM. All other logs (current and others) I can click and view just fine. I'm on my way out to the server to see the log in the file directory but what could cause this?
I created a package in SSIS, and used the SQL Server Agent to run the package. I get an error 'Package Execution Failed' everytime I run it throught the SQL Server Agent.I don't get an error if I run the package from SSIS.
I right-clicked in 'Control Flow' and clicked Logging to add a new log. After I re-run this again in the SQL Server Agent, where do I go to find the error log?
The project I am currently working on has a requirement to do certain amount of logging within SSIS. Client has asked me to log only to event viewer if the package has failed. Everything else they want to log it to a text file.
I enabled the package container and added "SSIS log provider for Windows Event Log" on Providers and Logs tab and selected "OnError" on details tab. It works fine when I tested that.
Secondly I added another package level logging "SSIS log provider for Text files" and given a new text file connection. In the details tab I selected "OnInformation" and "OnProgress".
Now if I go back and look at "SSIS log provider for Windows Event Log", it has OnError, OnInformation and OnProgress selected. All three are selected against both logging methods.
It looks like that Providers and Log tab is not linked to Details Tab. Has anyone else had the same problem, if so how did you get around it?
I have recently uncovered a problem we are experiencing with SQL Server 6.5 Service Pack 4 (Don't ask) and wonder if anyone has seen this before, and maybe has a solution.
When viewing an errorlog either current or historic, via either enterprise manager of xp_readerrlog, occassionaly the network connection is dropped and the process runs out of control. The process is unkillable, as it is in a 'Critical Section' and does not respond to kill. The real problem is that the process is logging millions of errors of the form "...cannot send results to the front end..." at a rate of around 1GB / hour.
I was under the impression or i always got following entries in SQL Agent error log when server restart and there are some entries in sql error log as well which confirms that server restarted. but today when i was checking error log i saw same entreis in SQL agent error log but there were no entries in server error log. now i got really confused whether my server is restarted or not........... because if it is restarted then there must be some messages in server error log..... can some one please let me know when and why following messages appear in SQL Agent Error Log
Information, There are 9 alert(s) in the alert cache Warning, delay_between_response attribute (10 sec) of alert (9) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (8) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (7) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (6) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (5) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (4) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (3) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (1) is less than poll interval for this alert (20 sec) Warning, delay_between_response attribute (10 sec) of alert (2) is less than poll interval for this alert (20 sec) Information, Populating alert cache... Information, There are 3 job(s) [0 disabled] in the job cache Information, SQLServer Message: 0<c/> SQLServerAgent Monitor started successfully. [SQLSTATE 01000] Information, Support engine started Information, Populating job cache... Information, Starting SQLServerAgent Monitor using '' as the notification recipient... Information, Alert engine started (using Eventlog Events) Information, Request servicer engine started Warning, An idle CPU condition has not been defined - OnIdle job schedules will have no effect Information, Job scheduler engine started (maximum worker threads: 800) Information, SQLAgent$XYZ starting under Windows NT service control Error, The Messenger service has not been started - NetSend notifications will not be sent Information, Subsystem 'ANALYSISCOMMAND' successfully loaded (maximum concurrency: 800) Information, Subsystem 'ANALYSISQUERY' successfully loaded (maximum concurrency: 800) Information, Subsystem 'QueueReader' successfully loaded (maximum concurrency: 800) Information, Subsystem 'Merge' successfully loaded (maximum concurrency: 800) Information, Subsystem 'Distribution' successfully loaded (maximum concurrency: 800) Information, Subsystem 'LogReader' successfully loaded (maximum concurrency: 200) Information, Subsystem 'Snapshot' successfully loaded (maximum concurrency: 800) Information, Subsystem 'CmdExec' successfully loaded (maximum concurrency: 80) Information, Subsystem 'ActiveScripting' successfully loaded (maximum concurrency: 80) Information, Subsystem 'TSQL' successfully loaded (maximum concurrency: 160) Information, There are 10 subsystems in the subsystems cache Information, Populating subsystems cache... Information, Local computer is ABC running Windows NT 5.2 (3790) Service Pack 1 Information, ** processor(s) and **** MB RAM detected Information, NetLib being used by driver is DBNETLIB.DLL; Local host server is ServerName Information, SQL Server ODBC driver version 9.00.2047 Information, SQL Server ABC version 9.00.2047 (0 connection limit) Information, Microsoft SQLServerAgent version 9.00.2047.00 (x86 unicode retail build) : Process ID 8100 Error, SQLServer Error: 2812<c/> Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)