Ya está disponible el soporte de las arquitecturas de fileover cluster de SQL Server en un entorno de virtualización. Esto significa que ahora existe soporte cuando se crea los nodos del clúster de SQL Server corriendo como máquinas virtuales.

De esta manera se puede lograr alta disponibilidad del SQL Server cuando se ejecuta en un entorno virtualizado con los beneficios de ambos, la virtualización y la alta disponibilidad del fileover cluster.

El cluster esta soportado para SQL Server 2005 y SQL Server 2008 en una máquina virtual Windows Server 2008 con Hyper-V, Microsoft Hyper-V Server 2008 y configuraciones certificadas por el Server Virtualization Validation Program (SVVP) siempre se cumplen los siguientes requisitos:

El sistema operativo corriendo en la máquina virtual es Windows Server 2008 o superior

El entorno de virtualización cumple con los requisitos tal como se documenta en “La Política de soporte técnico de Microsoft para Windows Server 2008 Failover Clusters”.

Mas detalles en:

Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment

This is something that I am frequently being asked about, so I decided to post the simple solution.

For SQL Server table columns that have the IDENTITY property enabled, their respected values are being auto-incremented according to the IDENTITY’s incremental value.

The seed value is the value that is used for the very first row inserted into the table.
Therefore, if at some point all table records are cleared, there might be the need to reset the seed value back to zero or some other value.

Here is how we can reset the IDENTITY value with a simple SQL statement:

DBCC CHECKIDENT ('table-name', RESEED, new-value)

It has to be mentioned that the next value that will be inserted on the table would be the value of ‘new-value’ + 1. So for example if the new-value is 0, the next row value will be 1.

5) Enable SQL Server Browser Service

If SQL Server is not installed as default instance but instead installed as named instance and also if there is no specific TCP/IP port configured, it will give rise to the error that is being discussed in this article. If SQL Server Browser service is enabled, it will allow the server to be connected through dynamic TCP/IP port. Enabling this service is a one-time process, as on enabling it once it will apply to all the instances installed on the same server.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Browser.

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

Quite often I get request if I send blog post in newsletter or through email. Here are few important links.

You can for sure get email of my post, however, I strongly suggest to visit blog as if there are any updates in my post they are reflected on blog.

Subscribe to blog post through email

Subscribe SQLAuthority Feed

Search SQLAuthority – This is very powerful search. Give it a try.

Follow me on Twitter

Reference: Pinal Dave (http://blog.SQLAuthority.com)

Les comparto este webcast que impartí sobre la administración en SQL Server Azure.

http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032426192&Culture=es-AR

Webcast MSDN: Roles y responsabilidades de la administración de una base de datos de Microsoft SQL Data Services

Id. de evento: 1032426193

Registrarse

Idiomas:
Español.

Productos:
Windows Azure.

Audiencia(s):
Programador/desarrollador de programas.

Moderador(es):

Eduardo Castro

Duración:
60 Minutos

Fecha de Inicio:

miércoles, 18 de noviembre de 2009 06:00 p.m. Bogotá

Información general del Evento

Venga para conocer acerca de la administración de bases de datos en el nuevo mundo de SQL Data Services (SDS). Comenzando desde la creación de una cuenta SDS, conozca acerca de las herramientas y técnicas para suministrar cuentas, servidores y bases de datos. Vea cómo se administra la facturación. Aprenda cómo colaborar con sus colegas para construir un proyecto Azure que utiliza SDS. Mostramos los mecanismos para la administración de bases de datos tales como los inicios de sesión y permisos de administración. Vea cómo SDS automatiza las tediosas y complejas tareas administrativas (por ejemplo, los errores de la máquina) y cómo le permite invertir más tiempo en las importantes funciones de diseño de un DBA.

Opciones de registro

Id. de evento:
1032426193

Registrarse

Saludos,

Eduardo Castro Martinez – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

En la siguiente presentación analizamos los roles y responsabilidades en la administración de una infraestructura con SQL Azure.

Saludos,

Eduardo Castro Martinez – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

When you create stored procedures, MS SQL Server does not really compile them and check them against the system catalog, as for example Oracle does.

This makes it nearly impossible for TSQL developers to make sure their code executes without faults in production environments.

My approach to check stored procedures is to execute them with all parameters set to NULL inside a transaction that will be rolled back after stored procedure execution.

BEGIN TRANSACTION
EXEC (@storedproc)
ROLLBACK TRANSACTION

The simplest strategy is to iterate through all procedures, and execute them using this code inside a TRY … CATCH block. If an error is raised, the CATCH block logs the error.

However, when I ran the code in an actual development environment with lots of SPs (around 120), two problems occurred that needed to be dealt with:

• If any SQL statement run in Management Studio creates more than 100 result sets, you get the error message

The query has exceeded the maximum number of result sets that can be displayed in the results grid. Only the first 100 result sets are displayed in the grid.

• Therefore, we stored the results of analysed procedures in a temporary table, which needs to be created only once if it does not yet exist
• If you execute several stored procedures in a row, and each one probably has some imperfect transaction handling code, you need to make sure to rollback all open transactions.

/*
DROP TABLE #p
DELETE FROM #p
*/

SET ANSI_WARNINGS OFF

IF OBJECT_ID('tempdb..#p') IS NULL
  CREATE TABLE #p (
    ProcedureName sysname COLLATE Latin1_General_CI_AS,
    ErrorNumber int,
    ErrorSeverity int,
    ErrorState int,
    ErrorProcedure sysname COLLATE Latin1_General_CI_AS NULL,
    ErrorLine int,
    ErrorMessage NVARCHAR(2048) COLLATE Latin1_General_CI_AS
  )

DECLARE @proc sysname, @params VARCHAR(1000), @exec VARCHAR(1000)

DECLARE c CURSOR for
SELECT	p.name, SUBSTRING(REPLICATE(', null', COUNT(pa.name)), 3, 1000)
FROM sys.procedures p
LEFT OUTER JOIN sys.parameters pa  ON  p.object_id = pa.object_id
LEFT OUTER JOIN #p ON p.name = #p.ProcedureName
WHERE	p.name LIKE '%stored-procedure-name-filter%'
AND	#p.ProcedureName IS null
GROUP BY p.name
ORDER BY p.name

OPEN c
FETCH c INTO @proc, @params

WHILE @@FETCH_STATUS = 0 BEGIN

  PRINT @proc

  WHILE @@TRANCOUNT > 0
    ROLLBACK

  INSERT INTO #p (ProcedureName) VALUES (@proc)

  BEGIN TRANSACTION

  BEGIN TRY
    SET @exec = 'EXEC ' + @proc + ' ' + ISNULL(@params, '')
    EXEC (@exec)
    ROLLBACK TRANSACTION
  END TRY
  BEGIN CATCH
    WHILE @@TRANCOUNT > 0
      ROLLBACK

    UPDATE #p
    SET ErrorNumber = ERROR_NUMBER(),
      ErrorSeverity = ERROR_SEVERITY(),
      ErrorState = ERROR_STATE(),
      ErrorProcedure = ERROR_PROCEDURE(),
      ErrorLine = ERROR_LINE(),
      ErrorMessage = ERROR_MESSAGE()
    WHERE ProcedureName = @proc
  END CATCH

  FETCH c INTO @proc, @params
END

CLOSE c
DEALLOCATE c

SELECT * FROM #p
WHERE ErrorNumber IS NOT NULL
AND ErrorNumber <> 515

Some final comments:

• I left the DROP and DELETE statements in TSQL comments to make it easier to clear or delete the temp table.
• The collation declarations are necessary for the JOIN condition if your working db and your temp db have different collations.
• If the script exits with the 100-result-sets error, rerun it until it only shows the check result for all stored procedures.
• ErrorNumber 515 is the error indicating a NULL value has been inserted into a not-nullable column. Since the script creates this error condition, we need not list it.

Aparte de las cláusulas especificas de cada base de datos, la clave esta en utilizar ORDER BY ASC (ordenación de menor a mayor) para los primeros resultados y ORDER BY DESC (ordenación de mayor a menor) para los últimos resultados de la consulta.

Sea la consulta:

select primera_columna,
       segunda_columna
  from mitabla

En los ejemplos estamos recuperando los últimos 10 resultados de la consulta.

Para MS SQL Server ó MS Access, utiliza la cláusula TOP:

select TOP 10
       primera_columna,
       segunda_columna
  from mitabla
 order
    by primera_columna desc

Para MySQL ó PostgreSQL, utiliza la cláusula LIMIT:

select primera_columna,
       segunda_columna
  from mitabla
 order
    by primera_columna desc
 limit 10

Para Oracle, utiliza la cláusula ROWNUM:

select *
  from ( select primera_columna,
                segunda_columna
           from mitabla
          order
             by primera_columna desc )
 where rownum <= 10

Para DB2, utiliza la cláusula FETCH FIRST:

select primera_columna,
       segunda_columna
  from mitabla
 order
    by primera_columna descending
fetch first 10 rows only

There are some cases when you need to do cleanse on your duplicate data.
Below I provide some way to clean your data.

here’s the duplicate data

--Customer's Telephone
declare @t table (ID int identity (1,1), FName varchar(20), LName Varchar(20), Phone varchar(10), CreatedAt smallDatetime)

insert into @t (FName, LName, Phone, CreatedAt)
select 'Mary', 'Jane', '09876543' , dateadd( day, -33, GETDATE()) UNION ALL
select 'Nan', 'Nes', '123456' , dateadd( day, -30, GETDATE()) UNION ALL
select 'Jazz', 'Soy', '5748759' , dateadd( day, -29, GETDATE()) UNION ALL
select 'Rocky', 'Sion', '875643' , dateadd( day, -27, GETDATE())UNION ALL
select 'Mary', 'Jane', '1234567' , dateadd( day, -21, GETDATE()) UNION ALL
select 'Rocky', 'Sion', '785465' , dateadd( day, -14, GETDATE()) UNION ALL
select 'Jazz', 'Soy', '4536382' , dateadd( day, -8, GETDATE())UNION ALL
select 'Mary', 'Jane', '6598690' , GETDATE()

SELECT * FROM @t

here’s the data

ID	FName	       LName       Phone	 CreatedAt
1	Mary	        Jane	   09876543	 2009-10-24 14:24:00
2	Nan	        Nes	   123456	 2009-10-27 14:24:00
3	Jazz	        Soy	   5748759	 2009-10-28 14:24:00
4	Rocky	        Sion	   875643	 2009-10-30 14:24:00
5	Mary	        Jane	   1234567	 2009-11-05 14:24:00
6	Rocky           Sion	   785465	 2009-11-12 14:24:00
7	Jazz	        Soy	   4536382	 2009-11-18 14:24:00
8	Mary	        Jane	   6598690	 2009-11-26 14:24:00

in data above we would like to take the latest phone number from the same Customer
expected result

ID	FName	       LName       Phone	 CreatedAt
2	Nan	        Nes	   123456	 2009-10-27 14:24:00
6	Rocky           Sion	   785465	 2009-11-12 14:24:00
7	Jazz	        Soy	   4536382	 2009-11-18 14:24:00
8	Mary	        Jane	   6598690	 2009-11-26 14:24:00

first method : this method works for SQL 2005 and UP

--find the latest by id..
;WITH DeleteDuplicate AS
(
 SELECT Fname, LName, Phone, ROW_NUMBER() OVER (PARTITION BY Fname, LName ORDER BY ID DESC) AS RowNumber
 FROM @t
)
 DELETE DeleteDuplicate
 WHERE RowNumber > 1;

--find the latest by createdAt
;WITH DeleteDuplicate AS
(
 SELECT Fname, LName, Phone, ROW_NUMBER() OVER (PARTITION BY Fname, LName ORDER BY CreatedAt DESC) AS RowNumber
 FROM @t
)
 DELETE DeleteDuplicate
 WHERE RowNumber > 1;

2nd way : applicable in sql 2000

 -- using max, aggregate function
delete @t
from @t A
where id not in (select MAX(id) as ID
                from @t    
                group by FName, lname) 

Because Microsoft SQL Server Analysis Services query and processing performance tuning is a fairly broad subject, this white paper organizes performance tuning techniques into the following three segments.

Enhancing Query Performance – Query performance directly impacts the quality of the end user experience. As such, it is the primary benchmark used to evaluate the success of an online analytical processing (OLAP) implementation. Analysis Services provides a variety of mechanisms to accelerate query performance, including aggregations, caching, and indexed data retrieval. In addition, you can improve query performance by optimizing the design of your dimension attributes, cubes, and Multidimensional Expressions (MDX) queries.

Enhancing Processing Performance – Processing is the operation that refreshes data in an Analysis Services database. The faster the processing performance, the sooner users can access refreshed data. Analysis Services provides a variety of mechanisms that you can use to influence processing performance, including efficient dimension design, effective aggregations, partitions, and an economical processing strategy (for example, incremental vs. full refresh vs. proactive caching).

Tuning Server Resources – There are several engine settings that can be tuned that affect both querying and processing performance.

Download SQL Server 2008 Analysis Services Performance Guide

Reference: Pinal Dave (http://blog.sqlauthority.com)

Chances are, you are here because you have googled for the above mentioned error from SQL Server.

In case you did not understand what it means, I’ve found a simple yet effective explanation in this link

I quote

CREATE TABLE foo (
fooid int IDENTITY,
foovalue varchar(47)
)

CREATE TABLE bar (
barid int IDENTITY,
barvalue varchar(47),
fooid int
CONSTRAINT fk_bar_foo FOREIGN KEY(fooid)
REFERENCES foo(fooid)
ON UPDATE
CASCADE
ON DELETE
CASCADE
)

CREATE TABLE baz (
bazid int IDENTITY,
bazvalue varchar(47),
barid int
CONSTRAINT fk_baz_bar FOREIGN KEY(barid)
REFERENCES bar(barid)
ON UPDATE
CASCADE
ON DELETE
CASCADE
)

SQL Server will say, hey, if we delete a row from foo, well, we could delete
multiple rows from bar, and then we’ll have to delete multiple rows from
baz, and that could go on forever! So let’s issue a warning about “cycles or
multiple cascade paths” and disallow it.

I’ve been thinking through and experimenting a bit more with some of the concepts in SQL Azure – specifically I was considering the impact of fragmentation on both the storage (in terms of the storage limit) as well as the maintenance. This is not a new issue, DBA’s face fragmentation regularly and can deal with it in a variety of ways, but with SQL Azure the problem looks magnified by a lack of tools and working space. Whilst looking into this, I then realised that there is an unfortunate consequence of not knowing how much data space your index is actually using.

Each table in SQL Azure has to have a clustered index if data is going to be inserted into it and clustered indexes can suffer from fragmentation if chosen poorly. The combination of SQL Azure and the time-honoured fragmentation provides three consequences about in, fragmentation:

• will occur and you have no way in which to measure it due to the lack of DMV support.
• will create wasted space within your space allocation limit.
• will reduce your performance.

You could work it out if you knew how much space you had actually used vs. what the size of the data held is, but we are unable to measure either of those values. If you have chosen the data compression option on the index then even those values would not give you a fragmentation ratio.

This leaves us with a situation in which you can not know how much you are fragmented, meaning:

• You schedule a regular index rebuild.
• Hope SQL Azure performs index rebuilds for you.

I’m not aware of SQL Azure doing this for you – and you do not have SQL Agent facilities either.

So this seems very wrong, the concept of SQL Azure is to take away a lot of the implementation details and hassle from the subscriber – DR and failover is handled etc. But there looks to be as gap in which certain items such as fragmentation is falling – I have not seen any documentation saying SQL Azure handles it (but there could be some hidden somewhere and I hope there is!) and neither are you given the right tools in which to program and handle it yourself.

What happens when you hit that size limit?

Msg 40544, Level 20, State 5, Line 1 The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions. Code: 524289 

That took a lot of time to get to, (SQL Azure is not fast), but was generated using a simple example that would also demonstrate fragmentation.

Create Table fragtest ( id uniqueidentifier primary key clustered,
padding char(3000)
) 

Very simple stuff, deliberately using a clustered key on a GUID to cause a decent level of fragmentation, and also using the padding fixed with character field to ensure 2 rows per page only, maximising the page splits.

insert into fragtest values (newid(), replicate('a',1000))
go 200000

Because of the randomness of the newid() function, the level of fragmentation is not predictable but will certainly occur – in my test I hit the wall on 196,403 records and failed with an out of space message.

Given the 2 rows per page and the number of rows, with ~0% fragmentation the data should be able ~767Mb – that is considerably short of 1 Gb – so there is a significant level of fragmentation in there wasting space, about 23% of it. If you include the 2k per page being wasted by the awkward row size then the actual raw data stored is roughly ~60% of the overall size allowing for row overheads etc.

So there are two important points from this contrived example:

• You can lose significant space from bad design.
• Doing this backs you into a corner that you will not be able to get out of – this is the worst part.

How are you cornered? well, try work out how to get out of the situation and defrag the clustered index / free up the space, you could:

• Attempt an index rebuild.
• Try to rebuild it with SORT_IN_TEMP.
• Drop the index.
• Delete data.

The first three fail, the SORT_IN_TEMP is not supported and would not of rescued the situation either since you have no working space in which to write the newly sorted rows prior to removing the old ones.  So do you really want to delete data? I don’t think we can consider that an option for now.

This all seems like a ‘rock’ and a ‘hard place’; whilst SQL Azure can support these data quantities,  it seems prudent that you never consider actually going close to them at all – and that you equally are going to find it difficult to understand if you are close to them, since there is no way of measuring the fragmentation. The alternative is that you manually rebuild indexes on a regular basis to control fragmentation, but then enough free space is going to have to be left to allow you to rebuild your largest index without running out of space – reducing your data capacity significantly.

The corner is not entirely closed off, the way out of the corner would be to create another SQL Azure database within my account and select the data from database1.fragtest to database2.fragtest and then drop the original table and transfer it back – not ideal but it would work in an emergency.

I think the key is to design to make sure you do not have to face this issue; keep your data quantities very much under the SQL Azure size limits, and watch for the potential of tables being larger than the remaining space and preventing an re-indexing from occurring.

Interested to know your thoughts on this one, and what other consequences of being close to the limit will come out.

Microsoft has launched a compelling new worldwide Microsoft® .NET Framework campaign at www.dotnetstories.com. Through online videos and written case studies featuring real developers who built amazing and diverse solutions on the .NET Framework.

The developers’ varied stories integrate the .NET Framework —Windows® 7, Windows Server® 2008 R2, Windows Azure™, Microsoft SharePoint® 2010, and Microsoft SQL Server® 2008 R2, reinforcing the business potential with Microsoft technologies.

Get involved!

Summary: The goal of this white paper is to provide a framework for choosing among virtualization, multi-database, and multi-instance consolidation strategies for SQL Server Database Engine OLTP applications by highlighting some of the key decision points based on technical analysis. Some foundational topics and terminology will be included to provide the basis for the discussion, because some terms or strategies might be worded differently in other papers.

Consolidation Guidance for SQL Server.

Pengalaman saya saat memakai SQL Server 2005 adalah sulit koneksi ke server, pesannya adalah “Warning: mssql_connect() [function.mssql-connect]: Unable to connect to server: SERVER\SQLEXPRESS“. Wah sampai kebingungan gak ketemu-ketemu solusinya, di sebagian komputer gak ada masalah tapi kenapa cuma komputer saya yang gak bisa connect (BT deh…..). Saya coba install dulu SQL Server 2000 baru bisa connect. Aneh banget…., masa tiap mau pake SQL Server 2005 mesti install dulu SQL Server 2000. Dan ternyata cara tersebut malah beda ketika di implementasikan ke komputer yg lain. Tapi hari ini baru saja saya menemukan dan baca di http://forum.ragezone.com/f528/share-new-way-to-register-an-account-without-rancp-php-script-564652/. Ternyata berhasil….., aplikasi web yg saya buat bisa connect SQL Server 2005 Express.

Caranya copy ntwdblib.dll [version] 2000.80.194.0 ke:

For XAMPP user:
C:\xampp\php
C:\xampp\apache\bin
C:\WINDOWS\system32

For WAMP user:
C:\wamp\bin\php\php5.2.6
C:\wamp\bin\apache\apache2.2.8\bin
C:\WINDOWS\system32

Untuk yang memili problem yang sama seperti saya, mudah-mudahan ini bisa menjadi salah satu solusi bagi anda. Silahkan download ntwdblib.dll disini (ket. Jangan lupa setelah selesai download ubah ekstensi *.jpg nya ke *.zip) maklum di wordpress gak bisa upload file berekstensi *.zip ^_^.

I use following script very often and I realized that I have never shared this script on this blog before. Creating Comma Separated Values (CSV) from Table Column is a very common task, and we all do this many times a day. Let us see the example that I use frequently and its output.

USE AdventureWorks
GO
-- Check Table Column
SELECT Name
FROM HumanResources.Shift
GO
-- Get CSV values
SELECT SUBSTRING(
(SELECT ',' + s.Name
FROM HumanResources.Shift s
ORDER BY s.Name
FOR XML PATH('')),2,200000) AS CSV
GO

I consider XML as the best solution in terms of code and performance. Further, as I totally prefer this option, I am not even including the linka to my other articles, where I have described other options.

Do you use any other method to resolve this issue? Can you find any significant difference in performance between these options? Please leave your comment here.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

]]> http://beenhazed.wordpress.com/2009/11/24/update-with-table-join/ Tue, 24 Nov 2009 19:56:22 +0000 beenhazed http://beenhazed.wordpress.com/2009/11/24/update-with-table-join/ http://decipherinfosys.wordpress.com/2009/11/24/ssms-tracing-a-session-in-profiler/ Tue, 24 Nov 2009 18:31:53 +0000 decipherinfosys http://decipherinfosys.wordpress.com/2009/11/24/ssms-tracing-a-session-in-profiler/

SQL Server management studio in SQL Server 2008 has a neat little feature called “Trace Query in SQL Server Profiler”.   Using this option, one can start a profiler trace right from SSMS and the trace that gets started is already filtered on the spid of that particular session.  This option is present under the Query Option of the Menu:

As you can see, it also has a short cut key: Ctrl + Alt + P.  When you select this, a profiler window will open and if you look at it’s properties and then the filter, you will see that it has put a filter on your specific SPID for you:

The very next question then that comes to mind is what events is it tracking and what columns is it using?  The default template that it uses for the events and columns is “TSQL_SPs” – you can see this by clicking on properties of the trace that it started for you.  This is one of the templates that comes with the install.  You can modify this template and customize it to your needs.  All you need to do is open it up from Profiler and go to File\Templates\Edit Templates, make the changes and save it.

This is a pretty handy feature and can help a great deal when tuning SQL code in SSMS.  One can get all the detailed information at the click of the button now.

Resources:

• SQL Server MSDN profiler reference – here.

Pembuatan aplikasi pada toko sering menggunakan database untuk penyimpanan data, apalagi jika aplikasi tersebut digunakan untuk warehouse atau pabrik atau rumah sakit. Database yang digunakan bermacam-macam, tergantung kebutuhan dari penggunaan aplikasi diperuntukkan, misal Microsoft Access, MySQL, SQL Server, IBM Database, dll. Untuk penggunaan database dengan kapasitas besar lebih disarankan menggunakan SQL Server atau IBM Database karena penggunaannya lebih stabil dan aman.

SQL Server (versi berapapun) bisa digunakan untuk menghandle data dengan kapasitas besar tapi untuk penggunaan yang lebih safety SQL Server untuk diupdate sesuai kemampuan komputer atau isi kantong anda .

Untuk Tutorial membuat database tunggu edisi selanjutnya .

Best Regards