Viewing 15 posts - 31,156 through 31,170 (of 59,101 total)
Sankar,
In the future, help us help you. Please post your data as I've done below. See the first link in my signature line below for more details.
CREATE...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 10:15 pm
SQL Kiwi (2/13/2012)
Jeff Moden (2/13/2012)
Nicely done, Paul. Will that preserve keys, constraints, and indexes? And, yes, I realize the TRUNCATE won't work if FK's are present.
One of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 10:05 pm
The error is pretty much self explanatory. You have a "field" in the data (probably the 76th field) that's too big for the table. Temporarily change the 76th...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 9:52 pm
SQLKnowItAll (2/13/2012)
USE databaseNameGRANT EXEC ON SCHEMA::dbo TO userName
That should do the trick, assuming the schema for these objects is dbo! Else, replace dbo with the schema you need.
That could be...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 9:44 pm
Maramor (2/13/2012)
I was curious what approach would be used to fix this particular situation.
If you have the Enterprise edition, partition the large tables by "row date" and "align the indexes"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 9:42 pm
If your backup files are much larger than the MDF/LDF files, then you may have multiple backups in the same file. I look at that as putting a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 9:25 pm
Since you don't have the Enterprise Edition, you can't do table partitioning. However, you can still build Partitioned Views where you can separate the older, mostly static data from...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 9:07 pm
ahthomas (2/13/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 9:00 pm
That won't actually switch the database from SQL Server 2000 to 2008. Your server may be 2008 but your databases will still be SQL Server 2000. Don't just...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 8:55 pm
Nicely done, Paul. Will that preserve keys, constraints, and indexes? And, yes, I realize the TRUNCATE won't work if FK's are present.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 8:35 pm
P.S. I won't explain it now because you won't believe me but when you eventually get burned by using BETWEEN with datetime datatypes, remember this post and that I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 8:29 pm
In the future, please post your data using the methods found in the article at the first link in my signature line below. 😉
Also, your example data has two "col6"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 8:22 pm
Now that the deletion of duplicates has been resolved, you might want to take a look at the structure of your table and figure out what would make a good...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 7:32 pm
Vincy-856784 (2/13/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 7:27 pm
Stevie T (2/13/2012)
wow. thank you very much, that's exactly what i want. implemented and wrapped. nice job -thank you.
Will the customer have any logins with "SA" privs....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2012 at 7:19 pm
Viewing 15 posts - 31,156 through 31,170 (of 59,101 total)