Viewing 15 posts - 24,286 through 24,300 (of 59,099 total)
There are two answers that I've grown accustomed to when working with any flavor of SQL. The first, of course, is "It Depends". The second one, which seems...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2014 at 8:57 pm
David Webb-CDS (2/26/2014)
Insert the records in batches and take log backups between the batches.
Switch the DB to 'Simple' recovery mode, insert in batches,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2014 at 8:50 pm
sankepalli (2/26/2014)
Suppose, there are 1 million records, if we insert all these records in the log file, it will become full & DB will become read only. We cannot...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2014 at 8:39 pm
S-I-M-P-L-I-F-Y 😉
I don't guarantee this will work because I don't have your tables to test it on but it should be pretty close. The key here is (as it...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2014 at 8:22 pm
waheed71 (2/26/2014)
I will appreciate if you can help me to write hour calculation report based on number of In and Out from site. The Problem I am facing here...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2014 at 7:26 pm
sgmunson (2/26/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2014 at 7:10 pm
yocki (2/25/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 10:53 pm
I've had the Developers cache semi-static and static data several times rather than calling stored procedures or doing embedded T-SQL to get the data. For the things I've used...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 9:41 pm
yocki (2/25/2014)
What are the effects of adding SYSADMIN Server Roles ?
I have this user called "SDE". It has PUBLIC Server Roles. Then I add SYSADMIN. All of a sudden,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 9:30 pm
ringovski (2/25/2014)
Thanks a lot chris, i have never heard of cross join before works.
It's not a CROSS [font="Arial Black"]JOIN[/font]. That's something completely different than the CROSS [font="Arial Black"]APPLY [/font]that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 9:26 pm
This should handle pretty much anything you can throw at it.
-- DROP TABLE #FileName
--===== Create a test table with some normal and "odd" file/path names.
SELECT FileName = 'C:/Location/Folder/Subfolder/filename20130101.xxx'
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 9:18 pm
AK1516 (2/25/2014)
2....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 8:47 pm
sqlnaive (2/11/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 5:39 pm
Also remember that indexes are simply a sorted duplication of data that will affect nightly maintenance, backup times, backup sizes, restore times, insert times, delete times, and possibly update times....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 5:35 pm
DKG2014S (2/25/2014)
SQL Server 2008 R2
LEFT OUTER LOOP JOIN PART_LIST p1 ON e.COLUMN3 = p1.CODE
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2014 at 5:30 pm
Viewing 15 posts - 24,286 through 24,300 (of 59,099 total)