Administration

Technical Article

Microsoft SQL Reporting Services – Running a Report from the Command L

  • Article

I recently ran into a need to run a report in SQL reporting services from the command line. The Report took four (4) input parameters and I had to export it to Microsoft® Excel and save it to disk. I had to rummage through the product documentation and the Microsoft® SQL Reporting newsgroup to get this right. For running reports from the command line, SQL Reporting services provide a utility called “rs utility”.

2005-01-26

2,602 reads

Technical Article

SQL Server 2005 - Managed execution

  • Article

The next version of SQL Server named SQL Server 2005 is completely hyped with the integration of CLR into SQL Server. The introduction of CLR into SQL Server allows developers to write stored procedures, triggers, user defined functions, user defined aggregates and user defined types using .NET languages like VB.NET and C#. This introduction has opened up multiple avenues for developers and we need to be careful in maximizing the feature provided.

2005-01-14

3,007 reads

SQLServerCentral Article

Recovery Planning For SQL Reporting Services

  • Article

SQL Server 2000 Reporting Services is becoming a more and more popular reporting option everyday. However, the disaster recovery plan for this add on is not a simple backup and restore since there are multiple pieces and servers usually involved. However the DBA may be responsible for the entire system. Mike Pearson brings us a look at some of the scenarios that you need to consider and what you might need to prepare for disaster recovery of SQL Server 2000 Reporting Services.

5 (4)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

29,286 reads

SQLServerCentral Article

SQL Server 2005 DBCC Command Quick Reference

  • Article

The next version of SQL Server due in 2005 will bring about many changes in how it works, with .NET, the CLR integration, Integration Services, and much more. Many of us are looking to get a jump on the product and see where these changes might affect our scripts and environments. Jon Reade has started the work in decoding the new DBCC commands, which ones work and which don't. Since there's a limited amount of documentation for the Beta product, read about his detective work and send him off an

3.64 (11)

You rated this post out of 5. Change rating

2004-12-16

34,279 reads

SQLServerCentral Article

Finding Objects Owned by non-DBO Users

  • Article

SQL Server has this concept of an owner of an object. Similar to the concept of schema, but not quite the same. Best practice dictates that all objects in SQL Server be owned by dbo, but that does not always happen. Tracking those objects down might be a pain, but Santveer Singh brings us an easy way of doing this.

You rated this post out of 5. Change rating

2004-12-15

6,059 reads

Blogs

SQL Saturday Boston Slides and Code

By

Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...

Scaling SQL Server 2025 Vector Search with Load-Balanced Ollama Embeddings

By

SQL Server 2025 introduces native support for vector data types and external AI models....

Advice I Like: Fear and Imagination

By

Fear is fueled by a lack of imagination. The antidote to fear is not...

Read the latest Blogs

Forums

How to use data pre-computed in previous ETL SSIS Nodes?

By rafa040500

I'm building ETL packages in SSIS. My data comes from an OLE DB Source...

Building AI Governance and Policies- First Steps

By dbakevlar

Comments posted to this topic are about the item Building AI Governance and Policies-...

Simple delete causes table scan on other tables with foreign key

By askcoffman

Why is sql doing a full scan VS seeking on the index? I've included...

Visit the forum

Question of the Day

Checking Identities

The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:

TravelLogID CityID  StartDate   EndDate
1           1       2025-01-11  2025-01-16
2           2       2025-01-11  2025-01-16
3           3       2025-01-11  2025-01-16
4           4       2025-01-11  2025-01-16
5           5       2025-01-11  2025-01-16
6           6       2025-01-11  2025-01-16
7           7       2025-01-11  2025-01-16
8           8       2025-01-11  2025-01-16
9           9       2025-01-11  2025-01-16
10          10      2025-01-11  2025-01-16
The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
    CityID,
    StartDate,
    EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above?

See possible answers