Viewing 15 posts - 6,241 through 6,255 (of 9,643 total)
By default SQL Server does not accept remote connections. On the SQL Server box you need to go to the SQL Server Configuration Manager and make sure TCP and/or...
January 16, 2009 at 7:24 am
Check out this thread, http://www.sqlservercentral.com/Forums/Topic305986-92-2.aspx
January 16, 2009 at 7:18 am
Have you tried using RESTORE? While the standard extension for a Native SQL Backup is .bak you can use any extension you want and it will restore using RESTORE.
January 16, 2009 at 7:09 am
Vikas and Abhijit have offered better solutions. Your original proposal is inflexible as you limit the # of phone numbers to the number of columns in the table. ...
January 16, 2009 at 7:01 am
Please read the articles linked in my signature. Your question is incomplete as posted.
Just a shot in the dark, but if the column is a character data...
January 16, 2009 at 6:56 am
Interesting topic. I can see both sides of the issue. I personally am against legislation of pay. I'm not a big union fan either, because the union...
January 16, 2009 at 6:45 am
If you are using SSIS, I think going directly to the source will be faster. Using a linked server basically means you have 2 clients the SQL Server and...
January 15, 2009 at 5:33 pm
Steve Jones - Editor (1/15/2009)
Glad to see the Patriots out of contention...
January 15, 2009 at 4:43 pm
Why are you using a linked server? Why don't you just use the actual source as the source in SSIS and skip the overhead of the linked server?
January 15, 2009 at 4:38 pm
GSquared (1/15/2009)
create table #T1 (
ID int identity primary key,
Col1 int);
insert into #T1 (Col1)
select number
from dbo.numbers;
select *
from dbo.Numbers
cross apply
(select col1
from #T1
where...
January 15, 2009 at 12:00 pm
The APPLY operator is designed for use against table valued functions while JOIN is for tables. They are not interchangeable.
January 15, 2009 at 11:21 am
What is the primary key definition? The error is pretty self-explanatory. You are getting dupes, so either you have bad data or a poorly chosen primary key.
January 15, 2009 at 11:17 am
You should work on tuning the stored procedure. Run it on the source server, check the execution plan, and add indexes or change query as needed.
January 15, 2009 at 11:09 am
cy (1/15/2009)
Jack Corbett (1/15/2009)
...I've sent her off to Montana and Ecuador since we've been married...How did you pull that off? 🙂
Wasn't hard. Montana was for the wedding of her...
January 15, 2009 at 10:04 am
Viewing 15 posts - 6,241 through 6,255 (of 9,643 total)