Installing SQL Server
Because installing SQL Server is so easy it is tempting to cut corners, fail to plan properly and blindly accept default options without considering the alternatives.
2009-10-06
4,162 reads
Because installing SQL Server is so easy it is tempting to cut corners, fail to plan properly and blindly accept default options without considering the alternatives.
2009-10-06
4,162 reads
Create a linked server on the fly in this tip.
2009-10-06
3,401 reads
With SQL Server 2005 DMVs, we can easily find query performance statistics. Every DBA has a favorite script to find query performance stats. I also have one. But, are all the queries captured by the DMVs? In this tip I will walk through capturing some of this data and show what is capture and what is not captured by the DMVs.
2009-10-05
4,784 reads
DBA's can use the Transfer Error Messages and Transfer Master Stored Procedures tasks to transfer error messages and stored procedures between difference SQL Server instances.
2009-10-05
2,328 reads
The final part of the series will examine full text catalogs and indexing, database collation, service broker considerations, encryption and high availability.
2009-10-02
3,303 reads
This white paper complements the existing documentation on planning, implementation, and administration of a SQL Server 2008 failover cluster, which can be found in Microsoft SQL Server 2008 Books Online. There are links to relevant existing content throughout the paper, which is intended primarily for a technical audience. This white paper covers failover cluster architecture and concepts for Windows Server (2003 and 2008) and SQL Server 2008; installation of a SQL Server 2008 failover cluster; upgrades and updates to SQL Server 2008 failover clustering; and maintenance and administration of SQL Server 2008.
2009-10-02
3,698 reads
SQL Server 2005 and 2008 provide native XML data type and provides extensive support for XML data processing. The easy conversion from XML to a relational table provides a way for set-based updates based on user input.
2009-10-01
3,838 reads
In a previous tip on SQL Script Generation Programmatically with SMO, you've seen how you can use SMO to generate SQL scripts programmatically. In this tip I will cover how to generate scripts using Windows PowerShell.
2009-10-01
3,940 reads
Given that companies spend on average between 7 and 12 percent of their annual budgets on energy – a focus on reducing energy consumption can have significant bottom-line impact
2009-09-30
3,575 reads
Change Data Capture (CDC) is a new native feature in SQL Server 2008 Enterprise Edition. This article shows how to use CDC to easily set up data auditing on your SQL Server system
2009-09-30
3,222 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