Viewing 15 posts - 4,576 through 4,590 (of 7,168 total)
SQL Server 2008 does not use UTF-8 anywhere in terms of storing data internally, and neither does SQL 2012.
SQL 2008 stores unicode data using UCS-2, a subset of UTF-16LE...
April 6, 2012 at 9:47 pm
Alternative:
EXECUTE...AT
http://msdn.microsoft.com/en-us/library/ms188332(v=sql.105).aspx
See example G. This way we can force a select to execute on the remote server.
If you have a table ready that matches the shape of the SELECT you...
April 6, 2012 at 9:25 pm
If you can change what your input parameters mean you will have a much simpler time querying your data in my opinion. Let's say we changed it to mean this...
April 6, 2012 at 9:03 pm
chumphrey 12211 (4/6/2012)
April 6, 2012 at 4:48 pm
You've got several concepts going on here that you need to learn before you can get all the way through the task. Here are a couple videos that cover some...
April 6, 2012 at 4:35 pm
Not sure, but your registered SPNs may need to be updated after the rename if the FQDNs change with the rename.
April 6, 2012 at 4:21 pm
OK, I think I ruled out the block-level copy step as a possible problem. I just successfully restored the supposedly problematic-backup to a different 2008 R2 server in the remote...
April 6, 2012 at 4:17 pm
Here's the equivalent T-SQL solution:
WITH cte
AS (
...
April 6, 2012 at 3:53 pm
You're sample data is still causing trouble...but I polished it a little to the point where it will at least run. here is a sample using the SQLCLR Aggregate:
IF EXISTS...
April 6, 2012 at 3:47 pm
Lynn Pettis (4/6/2012)
Try copying the file using Robocopy and see if it verifies okay on the destination server.
I wish I could...the 2005 and 2008 R2 data centers are geo-separated and...
April 6, 2012 at 3:33 pm
No worries on the name, happens all the time.
Did you see Gail's post? I think she is onto something 😉
April 6, 2012 at 3:27 pm
The RESTORE VERIFYONLY returned clean:
The backup set on file 1 is valid.
April 6, 2012 at 3:20 pm
Can you post the DDL for DateL2?
This part of your update statement will not tolerate NULLs:
WHERE CollectionPrefix = @CollectionPrefix
...
April 6, 2012 at 2:46 pm
GilaMonster (4/6/2012)
April 6, 2012 at 2:37 pm
We must have been typing at the same time...ditto to everything Lynn said. In order to help further we need to see DDL (i.e. CREATE TABLE statements), DML to create...
April 6, 2012 at 2:31 pm
Viewing 15 posts - 4,576 through 4,590 (of 7,168 total)