Excellent!!!

bala2 (9/27/2013)

---

HI All,

We have requirement to migrate a database from oracle to sql server 2008 .

What is best method to do the migration?

We are Planing to use SSMA tool for...

Luis Cazares (9/27/2013)

---

Sean Lange (9/27/2013)

---

Luis Cazares (9/27/2013)

---

Today, I'm really pissed off with the database and network administrators. Because of the lack of good planning and best practices, instead of restrictions...

mrea-605474 (9/27/2013)

---

Maybe I am a bit dense today since it is a Friday and I am looking towards the weekend.. But this isn't making sense to me.

I have a web...

Luis Cazares (9/27/2013)

---

Today, I'm really pissed off with the database and network administrators. Because of the lack of good planning and best practices, instead of restrictions to our users permissions,...

IF the server name is using...

Jon Higgins (9/27/2013)

---

Hi,

I'm dealing with a situation where one of our developers is compiling a component with the connection string to a SQL Server instance included in the compile. ...

Then EXISTS is a good choice. Another option might be something like this.

DECLARE @order INT = '1'

DECLARE @col INT

SELECT @col = col FROM Orders WHERE NumOrder = @order

IF @col...

You would call those other procs just like any other (parenthesis are not used in a proc call).

EXEC sp_2_InsertOwnersFromOnboard @StartPoint, @EndPoint

I would use EXISTS. Using exists looks for the actual row in the table, the @@ROWCOUNT version is examining the results of query to see if the row exists. That...

You should look up ALTER LOGIN in BOL.

polkadot (9/26/2013)

---

I'm trying to apply what I've learned in the APPLY links you left me, Luis, to my solution. Thus, I want a TVF for the right half of the...

Dwain, I think this should produce the same result?

SELECT field1, field2, field3

FROM table

JOIN dbo.DelimitedSplit8K(@UsersEntry, ',') s ON field1 = s.item

ORDER BY s.ItemNumber;

Could do this with a case expression also so there is no need to use CAST.

select case when CHARINDEX('%', @Test) > 0 then 1 else 0 end

The pivot approach certainly works but you might want to read this article. http://www.sqlservercentral.com/articles/T-SQL/63681/%5B/url%5D

It demonstrates that PIVOT can have some performance issues...