SQL Server Report Server 2008 R2 Execution Log Reports
As you design and deploy more and more reports to your Report Server, how do you review which reports are being run, how often, and how long the reports take to render?
2012-07-11
4,110 reads
As you design and deploy more and more reports to your Report Server, how do you review which reports are being run, how often, and how long the reports take to render?
2012-07-11
4,110 reads
The database developer can, of course, throw all errors back to the application developer to deal with, but this is neither kind nor necessary. How errors are dealt with is dependent on the application, but the process itself isn't entirely obvious.
2012-07-10
3,666 reads
We'd like to grow our understanding of the software you create and how you get it to your users. This survey should only take a few minutes and we really appreciate your input!
2012-07-09
2,000 reads
SQL Server 2012 Integration Services offers several different options for deploying and storing SSIS packages along with their associated projects, two of which are directly related to two deployment models available in SQL Server Data Tools console. Marcin Policht presents one of these methods, which deals with packages deployed using Project Deployment Model and leverages newly introduced Environments.
2012-07-09
2,715 reads
The Trash Destination and this article came from early experiences of using SSIS and community feedback at the time. When developing a package it is very useful to have a destination adapter that does nothing but consume rows with no setup requirement. You often want run a package part way through development, or just add a path so you can set a Data Viewer. There are stock tasks that can be used, but with the Trash Destination all columns are treated as selected automatically (usage type of read-only), so the pipeline knows they are required.
2012-07-06
2,532 reads
Learn how to clean up your orphaned replication settings.
2012-07-05
3,518 reads
MySQL introduced its own brand of job scheduling, called Events, in version 5.1. However, some Database Administrators (DBAs) feel that it isn't quite ready for prime time. This article presents a hybrid solution that uses MySQL Event Scheduling to manage the batch jobs and Windows PowerShell for the error handling.
2012-07-03
2,971 reads
Many clients are using custom stored procedures or third party tools to backup databases in production environments instead of using database maintenance plans. One of the things that you need to do is to maintain the number of backup files that exist on disk, so you don't run out of disk space. There are several techniques for deleting old files, but in this tip I show how this can be done using PowerShell.
2012-07-02
3,232 reads
PowerShell is becoming a great tool for managing SQL Server tasks, but like most tasks that are coded there is always the need for error handling to deal with the unknown. PowerShell has several options for handling and capturing error details and in this tip we will explain these options using PowerShell for SQL Server examples.
2012-06-28
3,684 reads
A deceptively simple solution to a business re-engineering problem can beguile companies into selecting a compromise that doesn't actually meet all their needs. Simple is great, but not at the expense of functionality. Some IT solutions are complex because the problem is complex, but they can be made conceptually clearer.
2012-06-27
3,279 reads
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers