Viewing 15 posts - 76 through 90 (of 285 total)
It turns out that OPENROWSET will not work for me:
SELECT *
FROM OPENROWSET('SQLOLEDB','Server=sql_server_network_name\instance_name;Trusted_Connection=Yes;Database=Master',
...
February 28, 2012 at 9:00 am
Since two of us asked the same question at the same time, this is the URL to the other thread:
http://www.sqlservercentral.com/Forums/Topic1258885-391-1.aspx
February 28, 2012 at 8:52 am
shew (2/28/2012)
ganeshnarim (2/28/2012)
Hi,in the SSMS Go to Local server groups/New server registration/just put in the servername and connection info and you should be good to go...
Hope this help full..
Hmmmm... I...
February 28, 2012 at 8:48 am
Sean Lange (2/28/2012)
Gianluca Sartori (2/28/2012)
As I asked in the other thread: why not using linked servers?
Because the homework question said to not use them??? Such a strange request and twice...
February 28, 2012 at 8:41 am
Gianluca Sartori (2/28/2012)
As I asked in the other thread: why not using linked servers?
We have audit restrictions. It's just waaaaaaaay too much hassle to get permission, document what we are...
February 28, 2012 at 8:38 am
Sean Lange (2/28/2012)
How completely random that this question was asked twice on the same day!?!?!?!?
That is wild. I googled a while prior to posting, but I didn't find anything useful....
February 28, 2012 at 8:34 am
ganeshnarim (2/28/2012)
Hi,in the SSMS Go to Local server groups/New server registration/just put in the servername and connection info and you should be good to go...
Hope this help full..
Hmmmm... I already...
February 28, 2012 at 8:32 am
Hmmm... It looks as if this truncation is a limitation of the print command. http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=95740
The data appears to be intact, and I can access it in 8000 byte chunks.
print '###...
January 12, 2012 at 11:00 am
Thanks for the feedback. SQLCMD.EXE and SSMS are truncating the data at the same place (~7700 bytes) in the output. Both tools report the data as being 9741 bytes long.
January 12, 2012 at 9:43 am
The data appears to be 9741 bytes long in the database, according to "select len(column_name)..."
January 12, 2012 at 9:00 am
I am running with SQLCMD.EXE under PowerShell because of the column truncation that normally happens in SQL Server Management Studio.
However, SSMS and SQLCMD.EXE appear to be truncating the data at...
January 12, 2012 at 8:57 am
GSquared,
One more question...
I started down the path of using XML because I read a Google hit that said XML would retrieve the entire column (presumably even for a varchar(max) column)....
January 12, 2012 at 8:40 am
Thanks, that works better. 🙂
January 12, 2012 at 7:42 am
GSquared,
XML is not my strong suit...
When I tidy up the output from your sample query, I am seeing multiple table tags, which can cause the data to misalign. Is there...
January 12, 2012 at 7:18 am
Thanks for the tip. That gets rid of some replace statements.
January 12, 2012 at 7:00 am
Viewing 15 posts - 76 through 90 (of 285 total)