There is only one Web Project Type in Visual Studio unlike the previous versions of Visual Studio.
From Standard Web Forms to MVC all the project templates related to building websites and web applications are available in the same place.
Sharing knowledge does not lessen your store, often it gets you more.
Success doesn't happen overnight and patience is key to living your dream life.
Success is a journey not a destination
There is only one Web Project Type in Visual Studio unlike the previous versions of Visual Studio.
From Standard Web Forms to MVC all the project templates related to building websites and web applications are available in the same place.
Windows Azure SQL Reporting is a cloud-based reporting service for the Windows Azure Platform built on SQL Server Reporting Services technologies.
SQL Reporting service is available to current subscribers, but should not be used for new software development projects. The service will be discontinued on October 31, 2014.
An alternative to SQL Reporting is to use one or more instances of SQL Server Reporting Services (SSRS) running on Windows Azure Virtual Machines (VM).
A known issue of SQL Reporting is that report execution is slower than SSRS running on premises. In contrast, performance of SSRS on a VM is similar to the performance you might expect from an on-premises SSRS instance.
Transition from SQL Reporting to SQL VM provides the following advantages:
SQLCLR allows integration of .NET Framework CLR components in SQL SERVER. .NET CLR Assemblies reside and run from database rather than file system. SQL SERVER need to check only once during deployment. This boosts performance and reliability.
SQLCLR allows to write stored procedures, functions, triggers, user defined types and aggregates using variety of .NET Framework languages like C#, VB.NET etc.
When to use SQLCLR?
Don't use SQLCLR for querying data from SQL SERVER. It is better to use T-SQL for that. Instead use SQLCLR when you can't perform some tasks using native SQL functions like GZip Compression/Decompression, PGP Encryption/Decryption, complex string manipulations etc.
How to enable SQLCLR?
exec sp_configure 'clr enabled', 1; GO RECONFIGURE GO
Consider a scenario where you have a view object in a database named "Database A" tries to access a table from "Database A" as well as a table from "Database B". In this scenario to run the view the user must also be a user in Database B along with Database A. If these databases are tightly linked, cross database ownership chaining can be used where user can access the table from Database B only through the view from Database A but doesn't have explicit permissions to query the table in Database B.
Steps to enable Cross Database Ownership Chaining
Set both Database A and Database B in the chaining as trustworthy.
ALTER DATABASE Database1 SET TRUSTWORTHY ON;
ALTER DATABASE Database2 SET TRUSTWORTHY ON;
Make sure that both Tables inside the Database A and Database B belong to the same owner.
Enable Cross Database Ownership Chaining. This can be done on whole instance level or specific databases.
For instance level
Exec sp_configure 'cross db ownership chaining', 1;
RECONFIGURE;
For database level
ALTER DATABASE Database1 SET DB_CHAINING ON;
ALTER DATABASE Database2 SET DB_CHAINING ON;
Yes, it is completely supported in SQL Server 2008 irrespective of the instance running on Windows Authentication or Mixed mode Authentication.
Make sure the AD Groups are created as Security Groups rather than Distribution Lists. If not created as Security Groups, then Nested AD Groups will not be working.
Attempt to start SSMS with a different windows user account if you are using credentials on the same domain
runas /netonly /user:domain\username ssms.exe
Use the "/netonly" switch, you can log in using remote credentials on a domain that you're not currently a member of, even if there's no trust set up
runas /netonly /user:domain\username ssms.exe
Want to do delta loads for your Data Warehouse and having problems in storing Last Load time in an SSIS DateTime Variable?
SSIS DateTime data type truncates the milliseconds from the DateTime. To avoid this set the data type for the variable to store the Last Load time as String. e.g.
SELECT CONVERT(VARCHAR(23), LastModified, 121) LastModified FROM ........
Then you can change it to DateTime before passing it back to the database.
.......WHERE LastModified > CONVERT(DATETIME, @LastModified, 121)