Search Results

If you're doing it through a T-SQL statement such as below, then no table drop will occur and you can safely do it in a production environment: alter table <table> alter column <column> nvarchar(bigg …

I currently have some SQL Servers that sit on a sub-domain. We are eliminating that sub-domain and moving everything to the regular domain. As far as SQL Server configuration goes, is there anything …

That seems fine to me. But the only way to be sure is to implement and test.

I'd suspect that your table would have to be incredibly large and improperly indexed or have hundreds-to-thousands of concurrent users running this proc (the merge uses 1 less lock) to really see any …

It's a warning, not an error. As long as the row is within the 2GB (I believe) limit, it should have inserted. Can you verify that it was indeed inserted?

You should do an isnull on both policynumbers so that you can group properly. Since it's an outer-join, there's the possibility of one side of the join being NULL while still having data. select sum …

Thanks to everyone for your help. After pouring through some execution plans, it turns out there is a JOIN that is being processed differently based on the amount of RAM available. With less RAM it e …

Setup: Windows Server 2008 R2 SQL Server 2008 R2 SP1 240GB RAM TempDB is 8x16GB data files w/out auto-grow (128GB total) Physical/Stand-alone Server This server is used for ETL processing. We jus …

Lets assume we have a table as follows: PK -- nonclustered primary key Col1 -- unique clustered Col2 Col3 Is this index: nonclustered index on (Col2, Col3) any different from this index: nonclu …

In addition to the answers addressing standards and compatibility, one should also keep in mind performance. While disk space is readily accepted as cheap, DBAs/Developers often ignore the fact that q …

Assume you have 2 SSAS databases, DB1 and DB2, that are identical. Now they branch off. Changes A and B are made to DB1 and changes C and D are made to DB2. Is there an easy method to migrate change …

No, if you want to alter the column type you're going to have to use an ALTER COLUMN statement. Well, that's not true - you can drop the table and recreate it - but ALTER COLUMN is clearly superior :) …

Re-worked it slightly... DECLARE @FoundIndex INT DECLARE @ReturnValue VARCHAR(MAX) SET @FoundIndex = CHARINDEX(@delimiter, @String) WHILE (@FoundIndex <> 0) BEGIN SET @ReturnValue = SUBSTRING …

Working in SQL Server 2008 R2, I am trying to rollback a set of DDL statements as a group (think of an upgrade script for a database), but am running into trouble. Take the following code: begin try …

select * from ( SELECT Subject, Name, RANK() OVER (PARTITION BY Subject ORDER BY Score DESC) as RN FROM Table ) a where a.RN <= 2