To SP or not to SP in SQL Server: an argument for stored procedures
A seemingly never-ending battle in online database forums involves the question of whether or not database application development should involve the use of stored procedures.
A seemingly never-ending battle in online database forums involves the question of whether or not database application development should involve the use of stored procedures.
For those of you using Analysis Services, Yaniv Mor takes a look at some of the manageablity tools with SQL Server 2005. The way you work with Analysis Services and your cubes has changed dramatically and this is a good overview to get you started.
Better late than never, here's a look at the May issue of the SQL Server Standard, now available as a PDF.
As everyone moves to SQL Server 2005 from SQL Server 2000, there are quite a few pieces of information that have moved and may give you trouble finding. Boris Balinger brings us a followup to his first look at some of those changes with a quick article on how you can get the free space in your database files.
There is a lot of talk these days about “business intelligence” (BI for short). Pick up any magazine aimed at business or technology professionals, and you’re sure to read about things like data warehouses, dashboards, cubes, ETL, SCD, and a seemingly endless list of other specialized terms and acronyms. One might be left wondering, is this something to which I should be paying attention?
XML is becoming more and more the mainstream for data transfers between systems. Web services and SOAP communications are built into SQL Server 2005, requiring the more and more DBAs understand how to work with XML. Raj Vasant has written a number of articles on XML and brings us a look at how XML should and should not be used.
If you're in Jacksonville next week, whether you’re a developer, DBA or manager, you’ll get something out of this all day SQL Server free event. This event is being run with Microsoft and Idea Integration (Brian from SQLServerCentral.com) and will be at a detailed tech level (no marketing). This all-day session is designed to Get You Started with Microsoft SQL Server 2005 High Availability and gotchas when upgrading to 2005. High availability is a hot topic for most enterprise customers. Any application downtime can impact your business, resulting in revenue loss, customer dissatisfaction, and damaging creditability of their business. These 300 Level sessions will be mostly demos! When you leave this, you should know how to mirror a database and cluster. RSVP required.
This (new) design bothered me. It violated one of the fundamentals that I'd learned and read about for years; namely keeping the primary key small and narrow. It also looked like it would be difficult to maintain. Finally, after arguing back and forth about the merits and drawbacks of each of the designs, we decided that testing them was the only way to be sure
Reporting Services is a great subsystem for SQL Server that fulfills quite a few needs. However just like SQL Server, there are some features that are limited to the Enterprise Editions, something that not every user can afford to implement. New author Jason Selburg brings us a way to implement subscriptions to reports using Standard edition.
The latest article in our series discusses improvements in the transactional support implemented in SQL Server 2005 Integration Services. The more granular scope of transactions, which now can be assigned to arbitrarily designated Control Flow tasks and containers, makes it is possible to limit their impact or execute several of them in parallel. However, even with this improved functionality, you need to keep the blocking issues they might potentially introduce in mind.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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