Where does one find this tool? MSDN ? Microsoft site? Somewhere on the SQL Server install CD ?

Steve

(aka smunson)

:):):)

Scott MacCready (4/24/2008)

---

IF someone has difficulties...

In your query for your dataset, you could probably find a way to use a CTE to create a "groups only" result set (using a HAVING COUNT(*) >1 clause) that...

There's a much easier way, although it might make the report design appear a bit odd. You can use an expression to change the visibility of any...

I'm pretty sure there is a specific sequence. See my EDIT in my previous post and see if you can find it from there. Also, I...

I don't know what the solution is, but a self-referencing table within a cascade delete just doesn't sound to me like "the only efficient way". The details...

Also, you may want to look at Data Driven Subscriptions. This provides a means of using a query to determine the e-mail addresses to be used as recipients....

I had to rewrite my query to improve it's performance, and once I did that, my problem was solved. However, I think there's a clear consensus that...

It could be a data type problem. Whenever you insert data from Excel, SQL Server looks at some number of rows at the beginning of the data to...

Having never done this myself, and assuming that it must be possible, I would check the BOL to ensure I was meeting it's exact requirements, and see if there was...

Sounds like it may not be configured by default, or it's been intentionally turned off. Check first with your admin/DBA, or if you're it, then you probably need...

How about OPENROWSET ? (look it up in BOL)

Steve

(aka smunson)

:):):)

I'm not sure exactly what you mean by "blowing up". However, I think the larger problem is knowing exactly how you expect things to work. If...

Yes. You can use a "tally table", aka "Auxiliary Table of Numbers". Look up posts from Jeff Moden on creating a tally table. Joining...

Eliminating your WITH statements should be possible by just changing to temp tables from cte's, by replacing each WITH statement with it's INSERT INTO equivalent (INSERT INTO #ctedisks, for example)....

I think you'll quickly discover that using any manner of recordset navigation using Access's built-in methodology will annoy the royal you know what out of you, so I would get...